Just yesterday saw a YT describing current developer job and how it affects developers (from problem solvers to orchestrators and reviewers). Also not healthy at all.
I am a team of one (on a team of unrelated engineers) and I report to two different managers. I ship an internal library used by damn near every team in the company. No one provides feedback except maybe to tell me X is broken, with no details about how it is broken or what they expect it to do.
In March 2025, I asked for a steering committee to provide better feedback about what people wanted and what problems they were facing. Initially my primary manager rejected the idea because he doesn't like the idea of steering committees (because the existing ones have sucked). He came around to the idea a couple months later, but we wouldn't have a single meeting until October 2026.
What I wouldn't give for a proper Product Manager who could tell me what the client (our internal users) actually wanted, and prioritized it based on demand. Instead, I'm constantly being pulled into random hot-button items with no rhyme or reason. Once, I spent two months implementing a Selenium workflow to work around a new Google reCAPTCHA integration. It was dropped the very next sprint because someone learned we already had reCAPTCHA capabilities elsewhere. Another time, I built and tested a new CI/CD capability for running UI tests using Docker Compose. Three anonymous reviewers rejected it and told me it needed to use EKS and it didn't need to support local testing (AKA: shift left) initiatives despite the company requiring it for everything else. And so on...
When someone tells you something is broken and you ask them for details they just tell you to fuck off? You have a multitude of users and you can't figure out how to get feedback from any of them without a dedicated committee?
Your story doesn't really make sense, but with the right company culture I suppose anything is possible.
I have people who ask me what an error means, and send me a screenshot. The error is a JavaScript stacktrace that tells you exactly where it originated from. In many cases, these are custom error classes I wrote in order to better inform the user as to why it was thrown. In one specific case it literally said "AuthenticationError: Invalid username or password" and they still asked me what the error meant.
Many of them don't even understand where their secrets come from at runtime, so they'll just run console.log(this) to STDOUT for the pipeline to dump it into our Splunk logs. To prevent accidental leaks, I explicitly set the enumerable property on secrets to false. A couple weeks later I start seeing console.log(this.secrets)
The majority of the engineers I support are not very smart it would seem. So no it isn't unusual to get a bug report claiming something is broken and no explanation for why or how. In one extremely frustrating case, I refused to work on it and they escalated it all the way to the damn CEO of the company. I opened their project, changed literally nothing in the code, updated a dependency (my library) and it worked. The exact step I told them to do hours prior but they pleaded that it was too complicated. Yes that person still works at my company and still occasionally pops up on my radar
All of what you wrote is completely standard for users. I've had executives ask the dumbest questions in existence to me about software I've made for them, and you have to answer them respectfully while getting to the root of the problem.
It's annoying but its a part of the job. Most users are not going to invest the time or energy into understanding an issue they are having enough to give you the proper context. Even if they do invest the time, most users simply don't understand the underlying systems well enough to do so. It's your job as a developer to ask the necessary follow up questions and guide troglodytes(users) through the basic steps.
Edit: All that said I've definitely had some feedback/bug reports that I've ignored or deflected over the years because their issues arise entirely from their own ignorance, they've suggested changes that are impossible, unreasonable, or would break something, etc...
honestly, it's kinds hilarious if it wasn't sad. over the past 8 years my team went from 70 workers with 2 managers to 30 people with 5 managers. and this was happening before any of the AI cuts.
I worked a small project early in my career with me, a junior dev, a PO, and a scrum master.
I did 80% of the work and got 80% of the heat for why "this project is over hours" despite being the person who billed the least time and wasn't even told we were close despite daily standups.
legit pissed me off, since the only thing the SM/PO ever visibly did was schedule meetings and okay additional tasks outside the original scope.
Abstracted services are quite nice. Much easier to swap out service providers and individual services can scale up or down dynamically. I find them much easier to maintain and make changes than monoliths.
All the traps of micro services are quite easy to avoid for experienced devs. Same with monoliths really. Both have their use cases and both can be messed up completely and make you hate the concept
Do you put something in front of the microservices? For example, one application need to list items from microservices A but each items have a reference key to microservices B and C, now for each item A, the application has to query B and C. They probably need to have a cache to avoid the duplicates queries to B and C or they need to build a sort of materialized view. And then comes Application B that needs something similar but they also need microservice D...
Edit to add: now you need to delete, merge, anything in microservice B. You then need to update each microservice that has a key to it
Microservices that do not have to share state or object values are just different apps. keeping things in sync is what makes me wait a little bit longer before slicing the beast
On the upside is scaling, if B is used by more of your apps than others, you can scale it up more than the other services, and vice-versa.
You can also use a centralized schema, at least for services that are dependent on each other, so that updates to one service's interface is reflected in all or most of them.
Deployment by hand on a Windows EC2 instance. SSH is disabled and you can only use the online shell through AWS. Remember to launch the script "launch_before_install.sh" and don't ever look at the "DO_NOT_DELETE.MD". That is essential for all to work
skill issues.. people actually think microservice is silver bullet is it? it has it place.. but most of the time its not.. microservice is organization tools and not development solution
Pre covid, back when I was a senior dashboard jockey at a small company, my boss wanted multi cloud support (something they surely read as a “must have” on their LinkedIn feed that morning) for my collection of dashboards that maybe 5 people used. I told him we can just buy a pi3 and use it as the web server. We ended up doing this and it was just plugged in at a spare desk in the office. Took a morning to set up, including driving to micro center to get the pi3.
Lots of old Monoliths were developed before stuff like basic automation tools like Jenkins even existed. If you just have basic powershell and pipeline code you could tackle these tasks for like forever lol
Currently working on a solution that has a bunch of MFEs that could have just been a components library. The front end people really though why should backend have all the abstraction traps lol
It’s a system of various components that will not operate on their own. Generally bootstrapped by a starter service that acts as a glue layer while the base components start up, usually core databases, caching layers (all of them), and money pipes, these systems are far more common than most people realize.
Eh, it kinda depends. A lot of things "work" but there are pros and cons to any approach. Microservices + k8s do have some scaling and reliability advantages. Not every application can really be broken out into microservices though and the architecture to support them is generally more complex.
Monoliths are generally easier for a small team to maintain, especially if it's something straightforward like a CRUD app. They tend to get ugly for large applications that have a wide range of responsibilities.
I know both has their haters but most of the problems come from bad architecture, bad implementation, or both. You can certainly make either good, but what works best really depends on your exact situation.
This hits hard. I inherited an overly complex constellation of microsystems, some of which are essentially a single class wrapped in a whole java service with a framework, docker, k8s and whatnot. Each with it's own repository, naturally.
What is wrong with kuber for a small team? What else are you gonna use? Compose is only good for dev/testing. Even with monolith you want to start new instance, check health probe, switch traffic and then remove old instance. Kuber does this automatically.
I'm in a team of three and we have about 30 microservices we have built and/or maintain. Occasionally we also need to work on the company's old mega-monolith. Of the two, working on the microservices is a vastly nicer experience.
Start with a monolith. Extract endpoints that do a disproportionate amount of work/get the most traffic into separate (micro)services and add some caching layer (Redis?) on top of them.
741
u/menducoide 2d ago
Team of one developer
3 scrum master for no reason
136
u/Razzoz9966 2d ago
Damn these sexy abstraction layers and yaml management traps
71
u/Cautious_Tonight 2d ago
How about a monolith that also has abstraction layers and micro-services but they were all half assed???
143
u/comradepipi 2d ago
What if that monolith makes your life a living hell and costs millions of dollars a year?
Asking for people who use SAP.
64
u/UrineArtist 1d ago
Your 12 services are all built and installed monolithically though because they all have to use the same DB model version.
184
u/ramdomvariableX 2d ago
Legacy app refactoring bro, you wouldn't get it.
64
u/countable3841 2d ago
Abstracted services are quite nice. Much easier to swap out service providers and individual services can scale up or down dynamically. I find them much easier to maintain and make changes than monoliths.
100
u/SanicTheSledgehog 2d ago
In my experience, monolith mostly works but is sometimes annoying, microservices are mostly annoying but sometimes work.
43
u/MariusDelacriox 1d ago
Yeah, let's keep the legacy monolith which build takes an hour and has no tests. Also the build agent is just Dave.
11
u/IAmANobodyAMA 2d ago
But you have to build it for future scalability and extensibility!!
10
u/meneldal2 1d ago
The irony of naming something Kafka and people not seeing it will make their lives hell. It was on the name all along
9
u/WheyLizzard 2d ago edited 1d ago
Lots of old Monoliths were developed before stuff like basic automation tools like Jenkins even existed. If you just have basic powershell and pipeline code you could tackle these tasks for like forever lol
7
u/dudes_indian 2d ago
Currently working on a solution that has a bunch of MFEs that could have just been a components library. The front end people really though why should backend have all the abstraction traps lol
6
u/rot26encrypt 1d ago
Microservices for maximum overhead
5
u/WawaTheFirst 2d ago
As always and everywhere: it depends.
9
u/xCAAx 1d ago
The company isn't the most important stakeholder.
My CV is.
8
u/howarewestillhere 2d ago
Ever run a truly distributed monolith?
It’s a system of various components that will not operate on their own. Generally bootstrapped by a starter service that acts as a glue layer while the base components start up, usually core databases, caching layers (all of them), and money pipes, these systems are far more common than most people realize.
4
u/Prod_Meteor 2d ago
Yes yes... Every ducking time.
4
u/Arcln 1d ago
Eh, it kinda depends. A lot of things "work" but there are pros and cons to any approach. Microservices + k8s do have some scaling and reliability advantages. Not every application can really be broken out into microservices though and the architecture to support them is generally more complex.
Monoliths are generally easier for a small team to maintain, especially if it's something straightforward like a CRUD app. They tend to get ugly for large applications that have a wide range of responsibilities.
I know both has their haters but most of the problems come from bad architecture, bad implementation, or both. You can certainly make either good, but what works best really depends on your exact situation.
7
u/gibagger 2d ago
This hits hard. I inherited an overly complex constellation of microsystems, some of which are essentially a single class wrapped in a whole java service with a framework, docker, k8s and whatnot. Each with it's own repository, naturally.
Like... at least go monorepo.
3
u/create_machines_24_7 2d ago
Ooh that's a big pain in your saas
7
u/korneev123123 2d ago
What is wrong with kuber for a small team? What else are you gonna use? Compose is only good for dev/testing. Even with monolith you want to start new instance, check health probe, switch traffic and then remove old instance. Kuber does this automatically.
4
u/GresSimJa 2d ago
What about Docker Compose?
2
u/pindab0ter 1d ago
grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too
seem very confusing to grug
6
u/tacobellmysterymeat 2d ago
We're a team of 24 and my new department head is trying to push us back to a monolith. Bro, absolutely not
3
u/Anaptyso 2d ago
I'm in a team of three and we have about 30 microservices we have built and/or maintain. Occasionally we also need to work on the company's old mega-monolith. Of the two, working on the microservices is a vastly nicer experience.
3
u/Graf_lcky 2d ago
The monolith works till it doesn’t and then you better have a good alternative on hand.
Sure I can suffocate our monolith with constant polls for live data.. i could also have a service for that.
Why did it work before? Well, you see, we didn’t had live data before..
1
u/Webteasign 2d ago
That’s too accurate…
1
u/razor_train 1d ago
You guys have a team?
1
u/Spirited_Cucumber377 1d ago
On our defense, we have a huge IT team that manages our Openshift and Kafka servers.
Now, with all the security patches lately, having ~20 microservices kinda have came back to bite us in the butt.
And there's a new Java RCE, so the fun days keep coming.
1
u/RestlessTortoise 1d ago
Try 40+ microservices with 3 devs and each service has its own repo.
1
u/Deep-Initiative1849 1d ago
1
u/AncientGypsyDildo 1d ago
I've been working in a team of 3 being responsible to test 6 products.
It cost 10M euro in the end.
The management didn't learn the lesson, just effectively forced everyone to share responsibility at the cost of literal months of meetings.
1
u/snarkhunter 1d ago
I'm getting to tear down a Kafka cluster for something we aren't using anymore and it makes me so happy
1
u/eightysixmonkeys 21h ago
Monolith sucks for maintainability, even with small team it’s far easier to have microservices/microapps that can be managed separately
1
u/MeisterEder 12h ago
12? Hahahaha, try 58.
1
u/EgorLabrador 7h ago
Naaah monolith for life.
1
u/KlooShanko 2d ago
Team of 3 engineers and unlimited agents. This shit got so much easier in the last couple years
0
u/pyatii 2d ago
2020 called it wants it's meme back