Technical debt is the number one cause of developer frustration. Working with imperfect systems demoralizes programmers, making it difficult to do quality work.
I’d wager not being given time to tackle technical debt is indeed frustating…
It’s hilarious when the identified problems come back around to bite the organization, when the priorities have been to work on poorly specc’d features instead.
Seen a lot of that too. Execs who thinks all the devs are idiots and would be lost without their genius guidance, phoned in from a luxury remote location while all of us have to return to the office full time. Then stuff fails and we “pivot” to the next badly thought out fiasco. I guess it pays the bills.
I keep seeing a pattern of sre/devops/sysadmin tasks being given back to developers and canning the SREs. Hard to understand why. Then some of the SWE get stuck basically focussing on infra SRE stuff and become unwilling SRE more or less. Circle of life? Do the old devops folks get made into glue or something?
Do the old devops folks get made into glue or something?
If i interpreted the “trend” correctly, “devops” was bastardized away from its original meaning to now mean “sysadmin”, at least in most cases.
Yeah. A “DevOps” is just a “sysadmin” who can pretend they don’t hate all developers for stretches of 20 minutes at a time. (I’m kidding. I know our SysAdmins love us… In their own secret ways.)
i interpreted the “trend” correctly, “devops” was bastardized away from its original meaning to now mean “sysadmin”, at least in most cases.
I don’t think I agree. The role of a sysadmin involved a lot of hand-holding and wrangling low-level details required to keep servers running. DevOps are something completely different. They handle specific infrastructure such as pipelines and deployment scripts, and are in the business of not getting in the way of developers.
“Devops” original intent meant you don’t have a separate “operations” department separate from teams “developing” your product / software due to competing incentives. “Dev” wants to push new stuff out faster; “ops” wants to keep things stable. Or “dev” needs more resources; but “ops” blocks or doesn’t scale the same. The idea was to combine both “dev” and “ops” people onto projects to balance these incentives.
Then managers and cloud clowns repurposed it to apply to every person in a project so now every member is expected to perform both roles (badly). Or even more overloaded to somehow refer to “developer infrastructure” teams.
The secret is just to do it anyway. I have yet to work in a job where anyone actively stopped me fixing technical debt, even if they never asked me to do it.
My boss legit says that he will give me some time to work on it every 2-3 months and then drops a “customer requires X feature and I promised that we will deliver in one week”. And mind you we have to patch up to 3 major versions in the past to back port the new feature because client haven’t upgraded and won’t in near future… which means sometimes our major releases are 60-70% same as our minor patches for old versions. Semvering much?
