4 ms·
I think that at least partly has to do with life circumstances changing, people get married, have kids, etc and have less time to spend practicing, reading. I'
by jmkni 5y ago
I think that at least partly has to do with life circumstances changing, people get married, have kids, etc and have less time to spend practicing, reading.
I'm 32 now, have been doing this since 20, and (I think/hope) mostly kept up to date, but I'm also single/childless lol.
Also, as you move up, you inevitably end up managing/mentoring younger devs (unless you have terrible people skills or something), meaning you spend less time actually coding, this also makes it more difficult to keep up to date (in detail, you still know what's going on, but have less experience implementing).
To be fair, terrible people skills could also apply to still being single/childless at 32, I hope not...
- cultofmetatron 5y agosingle and childless at 36. just frees me up to constantly travel fro place to place without a care in the world.
- WolfOliver 5y agoyou are in professional software engineering since you are 12? Learning to program is not the draining part it is the fun part. Dealing with people is the hard part.
- yourapostasy 5y ago> ...as you move up, you inevitably end up managing/mentoring younger devs (unless you have terrible people skills or something), meaning you spend less time actually coding... You can somewhat mitigate this if you want to still keep your hands in the code by finding the intersections of two or more tech stacks that take two or more others to even approach. The inevitable impedance mismatch between say two stacks means that one person familiar with both is usually far more effective than two people who have to feel their way through the mismatch. As a senior in this position, you often get to do the "fun" parts of throwing together a proof of concept, validate your mental model of the impedance mismatch, outline the details to iron out (usually known-complexity work like documenting, hooking up to various plumbing for unit testing, tracing, logging, monitoring, internationalization, etc.), and go on to the next fire to help put out.