I don't want to progress my career. I want to get better at building things.
Maybe one of these if more worthy of your time? - The C Book - GOF Book - The Dragon Book - TAOCP Book - The Rust Book
The Software Engineer's Guidebook
31–36 of 36 posts
Re: The Software Engineer's Guidebook
#32I 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.
Re: The Software Engineer's Guidebook
#33I 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.
Is that even possible? I'm currently the lowest of the low code monkey with no extra responsibilities but I code for maybe 10% of my time if that. Mostly I coordinate with other people to get info about what's broken this week and when it will be fixed and how soon we can deploy the code that I wrote in 5 minutes last week and who I need to get on board for it. I kind of get it to some extent, code is a liability tha…
Maybe that's why I ended up here. Maybe getting 5 folks like you from 10% to 12% coding time makes a bigger difference than adding my own 10% to the pile :(
Re: The Software Engineer's Guidebook
#34I 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 naturally take the lead and often end up in a similar situation where I spent a lot of time on leading, instead of tech. Early this year I joined a new team and expected the same to happen, but there were also a few other people who wanted the lead. I've taken that opportunity to let them. I'm now mainly coaching them and bothering with the team dynamics, without getting too distracted by stakeholder management. I…
Re: The Software Engineer's Guidebook
#35Earlier quoted context omitted.
"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…
Re: The Software Engineer's Guidebook
#36Earlier quoted context omitted.
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.
That's a bummer. Are you done with programming, or just all the apparatus of arroundig it in a business environment.
Something I have had trouble with is finding purpose - I work at a government agency, and I feel my work means next to nothing (for various reasons I can't get into).
I did manual labor for a while during university, and the sedentary nature of my current job may be contributing to my decreased interest to carry on with it.
Firefighting looks like something I'd love to do.