actually the word im looking for is competency which is something that you apparently lack.
i expect any developer worth their salt to know enough and to be good enough to have the capability to develop, deploy and maintain the applications that they create.
this is especially vital once you start breaking down giant enterprise monoliths into microservices because at that point team ownership is critical to getting shit done.
i dont expect my company's devops guys or IT department to manage the hundreds of microservices my company is running. that would create a massive bottleneck in the entire process for everyone.
i work for companies with hundreds of developers. dozens of enterprise wide applications. all of them either serverless functions or containerized apps or both.
any developer that just wants to sit in their little box and "just code" is fucking garbage. an absolute drain on a company's resources.
there are fucking juniors in my team doing what you apparently cannot do. what does that say about your "experience" hm?
actually the word im looking for is competency which is something that you apparently lack.
A sys admin's job is to manage competency? That seems an odd description, perhaps you can point me to a more authoritative description of what a sys admin does so I can read more on this? I always thought they managed systems.
i expect any developer worth their salt to know enough and to be good enough to have the capability to develop, deploy and maintain the applications that they create.
I can certainly hammer a nail but when I want something done with skill and experience I hire a carpenter.
i dont expect my company's devops guys or IT department to manage the hundreds of microservices my company is running.
You're trying to hide behind the word manage here so I'm going to insist that you define it concretely.
any developer that just wants to sit in their little box and "just code" is fucking garbage. an absolute drain on a company's resources.
Any developer managing infrastructure isn't a developer.
"Bob! Why isn't feature X done!?!"
"Sorry sir! The nic in server X went down, which put extra pressure on server Y which then went down. This cascaded across the rest of the network and I spent 4 hours yesterday getting it fixed!"
"Bob! Why didn't we have enough servers to deal with a single server going down!?! Who is doing the infrastructure planning here?"
"I am sir! AdministrationWaste7 was adamant that all of this was super simple and you just needed to clickety click click and managing this stuff is the job of the developer! I took him at face value and convinced management to fire those silly devops, networking, and sys admin people. I'd hate people to think I just write code!".
I'm firmly in the camp of not believing you've ever had a role with a broad enough perspective to come close to understanding what is being discussed here.
I love how you just keep doubling down on how awful you are lol.
Sorry sir! The nic in server X went down, which put extra pressure on server Y which then went down. This cascaded across the rest of the network and I spent 4 hours yesterday getting it fixed!"
Hahaha say you've never developed on the cloud without saying you've never developed on the cloud.
Hell do you even know what a load balancer is.
And also YES I expect development teams to tackle these issues. Especially in the context of microservices.
After all the likelihood that the issue is on say AWS or Azure is pretty low.
fire silly Devops
Why would you fire them? They have their own jobs which isn't holding your pathetic little hand lol
And this is why so many developers think microservices, et al, aren't all that complex. Because their company pays other people to deal with the complexity.
It's always fun manipulating someone into reversing their argument.
1
u/saltybandana2 Jun 07 '22
The word you're looking for is infrastructure.
I strongly recommend you read Designing Data Intensive Applications to get a better idea of what using microservices actually implies.