Skip to main content
6 events
when toggle format what by license comment
Jan 14, 2021 at 13:24 history edited Karl Bielefeldt CC BY-SA 4.0
typo
Jan 13, 2021 at 20:53 comment added user1169420 This answer a million times. I'm in OP's senior's position. I am the last stop for really hard, almost intractable problems that take lots of complex troubleshooting and design wisdom. So my junior dev is getting the bulk of the quantitative workload while I am quietly, endlessly banging my head on harder problems that move slowly and are less visible, as well as spending considerable unrecognized time curating tasks for him (they don't grow on trees). Also putting out production fires, keeping our pipelines flowing and planning.
Jan 13, 2021 at 12:34 comment added Graham It's not too far from the truth to say that the less your team can see what you're doing for them, the better you're doing your job to insulate them from all this. :)
Jan 13, 2021 at 12:30 comment added Jared Smith This. Sooo much of my time is spent doing linux server administration, dev ops, planning meetings, design meetings, vendor meetings, documenting procedure, context switching when the emergency alarm goes off, etc. I'm sure experiences vary a great deal, but for me it is definitely true that every year of my career I spend less time coding than the year before.
Jan 13, 2021 at 12:30 comment added Graham I've definitely filled this role. A senior engineer is often the pipeline for work between customers/sales/management/QA and the rest of the team. The rest of the team (mostly) shouldn't have to talk to all those people - they just get given (hopefully) well-defined and well-bounded changes, and they can get on with it. Your team don't have to deal with the knife-fight between four different customer reps over what the workflow should look like, or turn vague requests from sales into a well-defined change that can be implemented and tested.
Jan 13, 2021 at 2:45 history answered Karl Bielefeldt CC BY-SA 4.0