It’s my impression, as an engineer, and as expressed in other comments here, that a lot of (most?) engineers rather be doing/making things rather than managing people/processes/politics I wonder if it’s difficult for companies to find VPs of engineering, staff engineers and engineering managers
I've been a developer for 15 or so years and while I love to build, it's difficult to do anything meaningful in a vacuum. I've also been slowly chipping away at pre-engineering curriculum for the past 10 or so. Once I realized I have a knack for managing developers and I finished an AS, I went back to school for industrial /management systems engineering and haven't looked back. Now I get to architect big projects at a high-level and guide a team of very specialized people who are better coders than I could ever be... but I still get to dirty my hands quite often.
I definitely dread having to do PR reviews sometimes but it's really fulfilling and if that's rare, then that's great for my income potential right?
I've only read the link and the sample pages slightly, but this feels hyperfocused on advancing your career. Somehow the existence of books like these makes me depressed... is that rational? I just picture the future of tech being all about competitive people trying to race through their careers while the rest of the world puts up with their unpolished software.
"The best way to get what you want is to deserve it"
Looks interesting, ordered one for myself. As other commenters pointed out, I also enjoy building things by myself and there are already plenty of resources out there to keep improving on that front. However, at some point you realize that some if not most projects are bigger than yourself and you’ll need to work in a team. Not to mention it’s also more fun to work with other people where everyone can find their place to shine. With that come politics, processes, and management. And if your project is extremely interesting and attracts lots of folks, you’ll have to learn “the ways” to make sure you still get to keep working on the project. Thanks for a new addition to my shelf!
I've only read the link and the sample pages slightly, but this feels hyperfocused on advancing your career. Somehow the existence of books like these makes me depressed... is that rational? I just picture the future of tech being all about competitive people trying to race through their careers while the rest of the world puts up with their unpolished software.
I don't want to progress my career. I want to get better at building things.
>> I want to get better at building things.
Well that was my thought as well. I assumed that the latter would take care of the former. But I'm finding that if you aren't working in FAANG or similar this is not really the case.
I now realize I have to take concrete steps to progress my career in terms of positioning and salary.
I want to give the book a try. It seems interesting. I'm not sure though. I'm so burnt out seeing anything about a tech career or career advancement is unpleasant. I'm trying to accept that I just have a job, not a career, and that I won't get beyond midlevel.
I've only read the link and the sample pages slightly, but this feels hyperfocused on advancing your career. Somehow the existence of books like these makes me depressed... is that rational? I just picture the future of tech being all about competitive people trying to race through their careers while the rest of the world puts up with their unpolished software.
"The best way to get what you want is to deserve it"
Who exactly deserves a middle-management position where they sit between the actual business-handshakers who suck the blood from the company and the actual ("individual") contributors who do all the useful work? A nebulous self-busywork position that exists solely because it's convenient for the game of Feudalism that the upper management plays, the possibility of joining their ranks dangled in front of you like some cruel game of keep-away, with them knowing you'll never actually be able to become like them? Nor ever being able to return to the realm of Actual Work, as your skills slowly decay away and you lose your own sense of self-meaning, spending your entire days in meetings playing petty politics and cooking corporate metrics? Waking up every day to a miserable, tired existence as an utterly worthless being, your presence only resented by those underneath you, and mocked by those above you? Who deserves that waking nightmare!?
I could use a book on how the heck to finally move into a 'normal' software engineering role after having it elude me in every way you can imagine for for the past 3 years after college.
Seriously, how did I become a software lead without first being a SWE? I'm handling it well, but I really just want a 9-5 where 80% of my day spent with the code.
I want to give the book a try. It seems interesting. I'm not sure though. I'm so burnt out seeing anything about a tech career or career advancement is unpleasant. I'm trying to accept that I just have a job, not a career, and that I won't get beyond midlevel.
I came to the realization that software engineering was not what I wanted to do - about 4 years ago. 6 years into my career now. I still do it because I have bills to pay. I sometimes wonder how many others are in my shoes.
I don't want to progress my career. I want to get better at building things.
>> I want to get better at building things. Well that was my thought as well. I assumed that the latter would take care of the former. But I'm finding that if you aren't working in FAANG or similar this is not really the case. I now realize I have to take concrete steps to progress my career in terms of positioning and salary.