I have not talked to anyone before – including many enthusiastic proponents of microservices and some developers of things like k8s that I've met over the years – who claimed that the operational story of microservices was "basic" or "trivial". It's widely recognized this can be complex and takes time to manage well. Is this worth the trade-off? Opinions clearly differ on that. But the trade-off is very real.
> It's bad form to go down the "everyone else sucks and I'm flawless" path
Except I never said anything like that.
> It's also bullshit to pretend that nowadays there is no way to launch and shutdown dozen of services in one go
I never claimed "there is no way" to do this.
> These are all lame excuses, and one that illustrates problems caused by the developer's inability to go through the very basics.
I'm not going to join an organisation and tell them "you're all doing it wrong!" in my first week. I might make suggestions, and if they're received with "meh, I don't see the issue" then I'm not going to press the issue to an unreasonable degree, or work on things I find important regardless, especially if they don't directly contribute to the product that's being built.
> I have not talked to anyone before (...) who claimed that the operational story of microservices was "basic" or "trivial".
You somehow failed to read what I actually said, and proceeded to go off on a non-sequitur.
I repeat what I said: it is trivial to launch and shutdown multiple services in a local software dev environment. It's trivial with Docker, it's trivial with minikube, it's trivial with microk8s, etc. It is a solved problem. Why is anyone trying to pretend that this is impossible?
Enough excuses and scapegoats.
> Except I never said anything like that.
Except you did. You tried to claim that the small teams you were involved failed to setup working software environment because reasons, and that was the reason why you also failed. Bad form. You own your work.
> I'm not going to join an organisation and tell them "you're all doing it wrong!" in my first week.
Bullshit. It makes zero sense to forego setting up a working dev environment as the very first onboarding task, and excuses like "being able to debug would make team members pissed" is absurd. Either you can do your job or you can't, and throwing your team members under the bus like this is bad form.
> It's bad form to go down the "everyone else sucks and I'm flawless" path
Except I never said anything like that.
> It's also bullshit to pretend that nowadays there is no way to launch and shutdown dozen of services in one go
I never claimed "there is no way" to do this.
> These are all lame excuses, and one that illustrates problems caused by the developer's inability to go through the very basics.
I'm not going to join an organisation and tell them "you're all doing it wrong!" in my first week. I might make suggestions, and if they're received with "meh, I don't see the issue" then I'm not going to press the issue to an unreasonable degree, or work on things I find important regardless, especially if they don't directly contribute to the product that's being built.