As a senior developer I have no idea how I’d get an AI to autonomously keep a small subsystem maintained. If I was replacing junior developers, that’s what it has to do.
Everybody in my team gets to own something. What you own depends on your capability. You learn by doing. No dogsbodies doing busy work.
Everybody in my team gets to own something. What you own depends on your capability.
This is a point I try to constantly make when people don’t understand why 2 people have the same title but don’t really have the same job, especially in technical fields.
No two people have the same set of skills, so we all end up taking on the tasks we’re more capable of than the next person.
It works great if nobody ever leaves or dies or takes vacation. We try to discourage siloization of projects and emphasize cross-training - it makes the job more interesting, gives people more/better tools to solve problems with, etc. And anytime the business objects we mention the project where X left and how painful it is to get new anything added/enhanced because none of those tenets were involved.
However, all bets are off with offshore contractors. Some want to learn, some simply don’t care and will do the bare minimum.
We try to discourage siloization of projects and emphasize cross-training
This is how my work has been and it allowed me to touch every part of the repo while still a junior dev and gain lots of experience. So I also like that. But lately I’m trying to specialize more and go deep into things, and I like the idea of being an expert on something. So I appreciate the trade-offs.
all bets are off with offshore contractors. Some want to learn, some simply don’t care and will do the bare minimum.
As a guy who was replaced by offshore contractors, and who hasn’t had a single interview in 7 months while offshore contractors are (probably) still getting lots of work… I find this observation both heartening and disheartening.
As a senior developer I have no idea how I’d get an AI to autonomously keep a small subsystem maintained. If I was replacing junior developers, that’s what it has to do.
Everybody in my team gets to own something. What you own depends on your capability. You learn by doing. No dogsbodies doing busy work.
I don’t think developers are doing it. It’s managers making this kind of decision I’d say.
This is a point I try to constantly make when people don’t understand why 2 people have the same title but don’t really have the same job, especially in technical fields.
No two people have the same set of skills, so we all end up taking on the tasks we’re more capable of than the next person.
Oh I like this.
It works great if nobody ever leaves or dies or takes vacation. We try to discourage siloization of projects and emphasize cross-training - it makes the job more interesting, gives people more/better tools to solve problems with, etc. And anytime the business objects we mention the project where X left and how painful it is to get new anything added/enhanced because none of those tenets were involved.
However, all bets are off with offshore contractors. Some want to learn, some simply don’t care and will do the bare minimum.
This is how my work has been and it allowed me to touch every part of the repo while still a junior dev and gain lots of experience. So I also like that. But lately I’m trying to specialize more and go deep into things, and I like the idea of being an expert on something. So I appreciate the trade-offs.
As a guy who was replaced by offshore contractors, and who hasn’t had a single interview in 7 months while offshore contractors are (probably) still getting lots of work… I find this observation both heartening and disheartening.
One of my bosses has a concept of “T-shaped developers”, which means you know everything a little, and have depth on one thing.
7months: ouch, sorry to hear. I wish I had some words of wisdom to share.