3 ms·
Unfortunately, you may need to let go of your tech work, or shunt it over to "nights and weekends." I was a manager for 25 years, and one thing that I learned,
by ChrisMarshallNY 5y ago
Unfortunately, you may need to let go of your tech work, or shunt it over to "nights and weekends."
I was a manager for 25 years, and one thing that I learned, was to never put myself into the critical path. I could do tech projects, but they needed to be "nice to have on the side" projects.
Management requires that we work on interrupt. We can't have that sweet "fugue," that makes us productive developers.
What I did, was work on a lot of open-source stuff, on the side. I didn't have deadlines, and it allowed me to keep my "tech chops" up.
Since leaving that job, I tossed the management stuff into the skip, and have concentrated 100% on tech work. I love it.
I'm a damn good engineer. I get a hell of a lot done, at awesome quality levels, in very little time, but I also don't particularly care whether or not anyone co-signs my work.
Also, I'm not a jargonaut. Lots of folks like to sneer at people like me, because we suck at Buzzword Bingo.
- alasdair_ 5y agoIt's possible still to do some real coding as CTO. One thing I like about Stripe is that the leadership will make sure to take a week or so each year to ship a real feature and then write up all the little pain points that they experienced and ensure they are addressed - it helps quite a lot with developer productivity.
- Mezzie 5y ago> Management requires that we work on interrupt. We can't have that sweet "fugue," that makes us productive developers. Thank you for this. My boss left in October and I have not been dealing well with the influx of things on my plate even though I have the time in terms of hours, and that explains why: The items I took over from her are directly opposing what I need to do my job. Well. It doesn't fix it, but it's validating, I guess.