DevOps.
I didn't become a software engineer to write yaml or negotiate K8s resource allocation.
I didn't become a software engineer to write yaml or negotiate K8s resource allocation.
I also argue that we're probably fucking it up a lot, causing it to be more painful than it needs to be, but that's because we consistently get our developers to do infrastructure work.
A corollary to this, locally running the code AND integrations is essential. If you don't have the ability to replicate the full system locally, your devs are hamstrung and will take much longer to solve what could be very easy problems if only they could have debugged it locally and quickly. This is related because if your infrastructure is shooting for the moon in complexity, your devs have little hope of replicating it locally.
The perversion of it is that it comes across that I’m against DevOps. I’m absolutely the opposite. I’m against attaching bullshit marketing labels to good practices and making them a cancer on the project (cough devops, agile cough).
I’ve dealt with this recently. The “DevOps guy” was a toxic, condescending gatekeeper who wouldn’t co-operate with the engineers at all, but had the ear of the management.
He had a bunch of servers and builds he was really pleased with that were not at all documented and completely useless to everyone, because no-one understood it and couldn’t ask questions.
Good ops should be utterly transparent and utterly out of the way. Not hidden magic, just so easy to understand that it ticks over doing what it does without interrupting your workflow. And always reproducible locally.
Give a prick even the slightest chance to poison your company and they will is about the only 100% reliable piece of advice I could give anyone in this industry.
There is absolutely no bullshit in replacing waterfall's big upfront design and risk-prone one-shot dev project with an iterative process where at each cycle you reevaluate your course and your planning, always based on developer feedback.
There is also absolutely no bullshit in avoiding the mistake of artificially separating the devprocess into sysadmin stuff and dev stuff, and actually get developers directly involved and more importantly become mindful of the reality of everyday operations.
Portraying agile and DevOps as bullshit is clear telltale sign you are completely oblivious to the issues software developers face on a daily basis, and how agile and DevOps help solve or mitigate them.
2) agreed.
3) I never did that. I’m fully aware of the issues software developers face on a daily basis. I am one. Same as almost everyone here. Agile and DevOps (capital A, capital D, capital O) are corrupted buzzwords used to saddle engineering teams with snake oil salesmen and deeply suspect printable credentials.
But by all means you keep on throwing around baseless aspersions about who has the right or wrong kind of experience if they say something you don’t like.