>developers are not incentivized or even encouraged to gain broader knowledge of how their systems work
This is the crux of the problem. Coding in isolation. Replies of 'It's java, it should work anywhere' etc.
The other gear grinding commom theme is not even doing basic troubleshooting. To the point of not even googling the error message or the symptoms, and being 'blocked' because they are waiting on a ticket they opened with the 'other' team.
We’re a small company so we sometimes do many things, but it’s taught me a lot of networking fault finding.
There’s some very clever ppl that know all about how networks/vm stuff work, and I’ve learnt enough from them that I can fix most of my own infra related things - or at least give them a run down of what I’ve done first to save them some time.
It got me back into hardware and networky stuff, so now I’ve got a MikroTik at home, some proxmox machines, Tailscale network etc - more fun than just spin up a box on DO and be done with it.
A lot of ppl just aren’t interested though, they just want to code (and maybe learn a new language) but because a lot of stuff is now PaaS and it’s super easy, there is no need to learn it (in their eyes)
I think incentive for developer is to be relevant. If you don't do it, someone else will. And that becomes the new norm. Like how DevOps has become the new norm.
This is the crux of the problem. Coding in isolation. Replies of 'It's java, it should work anywhere' etc.
The other gear grinding commom theme is not even doing basic troubleshooting. To the point of not even googling the error message or the symptoms, and being 'blocked' because they are waiting on a ticket they opened with the 'other' team.