Look at the packages. Try to break it down into architectural layers. Understand in a broad sense what each layer adds to the one before. Rage that it wasn’t so much architected as cobbled together from pieces never designed to fit together. Decry it as total garbage and recommend total rewrite.
I would create a Jenkins task that runs during deployment that does whatever magical thing that updates your central index. That’s going to be implementation-dependent. I once worked on a custom workflow and documentation repository that did basically this, but I don’t have more info because I was only there a few weeks before getting moved to the contract I had actually been hired for. It would’ve been more complicated because they had api preview docs for things still under development.
Point is it was a custom solution and I’m not aware of an existing product.
OpenAPI will let you generate both controller and swagger documentation from a single yaml configuration. That’s probably not the whole answer, but it’s the hard part. Then you just need something to index all the swagger docs.
This presumes Java. I don’t know about other ecosystems.
Why do these stupid bots respond to explain why you are right? It’s not like they are (or are even capable of) learning anything. It comes across as condescending more than anything.
“Let me explain the situation to you, the person who just explained it to me.”
Classic AI-splaining.
I know where you’re coming from here. All I can say is there is something else wrong in this case and this is how it’s being expressed. I’ve seen it several times myself and sometimes no amount of good coding can fix bad architecture.
But I will say that if the twenty use cases all grow to the point of needing their own abstraction, I think you’d be damn glad there was at least a point of separation instead of having to maintain all possible permutations in a single method signature.
Let’s say you currently have an overloaded “god method” that is used for twenty different things. The proper thing to do would be to create twenty different interfaces that each do one specific thing and then call the syscall behind the scenes. That allows you to update and modernize your apps, allows for better testing of specific use cases, etc.
The original exposed syscall is deprecated and then eventually you force all the reliant code to adopt the proper new interface. The original overloaded code is still there, but locked up in a black box where no one has to worry about it.
Yep. I mostly document why the obvious or best practice solution is wrong. And the answer is usually because of reliance on other poorly written code - third party or internal.
I agree. Particularly because it’s less about the truth and more about what can be proven in court. But even more, they don’t want to pay a lawyer a bunch of money to defend this even if you could prove it beyond a shadow of a doubt. You can tell by the way they didn’t want to pay a lawyer to answer this question.
It’s hard to say what algorithm would serve you better. Seems like this does what you are seeing it to do. It’s not how I’d do it, but I don’t prioritize unblocked users. To fix this, I’d assign a multiplier for zero blocked users. It might be one so that no blocked users is the same as one mathematically. But maybe free speech is so important to you that you give it a multiplier of 2 or wherever.
active_users / [MAX(1,blocked_users)]
This would be a multiple of 1. Change the 1 to a 0.5 for a multiple of 2.
I didn’t look at the script but it probably has a Max function which just returns the higher of two numbers, effectively putting a lower bound on the possible values.
I’m self taught and have pretty bad imposter syndrome. Don’t think that’s the magic bullet.
You’ve got a lot of good reasons here, it’s just about how you phrase it.
Looking for new opportunities is extremely bland. It makes it sound like you’re bored or fishing for more pay. By being clear about what is wrong with your current environment, you demonstrate an understanding of what makes an effective team, and you feel you are ready for more responsibility. All good things.
Just don’t say anything about personality conflicts or you can’t stand your boss or call them all idiots or anything that sounds angry or overly emotional. Frame anything you have to say in positive or neutral terms. Like frequent leadership turnover makes it difficult to have consistent goals and direction vs. I hate constantly getting new bosses and each one is dumber than the last.
Management isn’t the only career path forward, but leadership is certainly part of any role of senior developer or higher unless you have very solid specific domain knowledge. Perhaps an architect role might work?
Having a broad base of experience can work for you in interviews, but you need to present it the right way. You know 20 different ways /tools for doing things and are able to choose the best tool for the job rather than having only a hammer and hitting everything like a nail.
I once worked with someone with the title Vice President of Awesome. We worked for a consultancy where you could just pick your own title.
I’m fifty, so I started my career in a different world. I hired in to a small consulting company. Our business was selling IBM systems and development was just a required value-add to that end. There were three of us when I hired in, knowing nothing. I was computer savvy but only a hobbyist programmer.
In the course of the next year, both of the other developers left the company, leaving me to grow and learn for myself. After 5 years I was promoted to senior. I had nothing but time in and there was no one to evaluate my skills or mentor me. I stayed another 4 years until the changing business model to IT as a service forced me out.
I was now a ten year senior with an unrelated two year degree and no knowledge except what I’d uncovered myself in a dying niche. I tried owning my own business but I’m not cut or for that. I lucked into a large project that was half the old stuff and half Java. I was there for a year or two when that business failed and I was spun off into a new consultancy.
One project had me commute back and forth to DC every other week. I liked it so when a government contract reached out to me with an opportunity, I took it and moved my family. This was my first time being part of a long term team and this is where I learned everything about that side of things.
Fast forward a few years, a move back home, and a few jobs, and with 24 years of experience I just accepted a position as a tech lead which I think is as far as I ever want to go in my career. I’ll put in a few years and look for a better contract or non contact position because this current company is shitty.
Title has never mattered in my career until I moved out of the SMB market into big business where title is tied to promotion path and salary. Most of them were totally arbitrary like when every one of twenty developers were just software architects. But now it’s important at least in the positions I’ve been seeing and taking.
If your library is a core dependency and it is constantly having breaking updates then something is deeply unwell in the environment. That is not sustainable, and it sounds like your library was created without a clear idea of what it should do.
I’ve been around long enough to know these things happen, but you’re not going to find a good way forward because there isn’t one. This is going to be a pain point until either the library is stable or the project fails.
This doesn’t feel like a disaster to me at all. This is an opportunity to grow and learn new things and new ways of doing things. It looks like your environment is very supportive and understanding that it will take some time and effort to get up to speed and are offering mentoring. And businesses often have valid technical or non-technical reasons for using a particular software stack - for example C# developers are likely easier to find than C++ developers which makes hiring easier in the future.
My suggestion is to take some deep breaths reset your perspective. Yes, sometimes it’s not fun to push outside of your comfort zone, and it sounds like that is creating a lot of anxiety for you, but you’ll do fine. This is very similar to how I got started professionally programming 25 years ago.
I’ve seen live updates for things like Go, NodeJS, Vue, Flutter, Angular, and you can recompile a Java class during debugging in Java (with limitations as certain things like static variables and methods need a full restart). More support and integration is certainly better but it doesn’t feel like it’s in a bad place to me.
Mainly financial sites, in my experience. I also have problems logging into Mastodon, because if I manually type my user and password I get logged in but if I use Bitwarden or even copy/paste it fails.
But also every site where you type in the user name and then submit and it takes you to enter the password - I use a lot of custom emails to avoid spam so I may not remember my username for a given site, but Bitwarden won’t recognize it as a login page (much bigger problem on mobile, which is where I do most of my stuff).
It feels like a lot of sites are taking active measures to block the use is password managers, too. I hate those sites. Why I’m the hell would you do that???
This helps with writing unit tests as well.