21–30 of 36 posts
Earlier quoted context omitted.
>> 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.
FWIW, it’s the same at FAANG
Love the concept, but after reading the sample ( https://pragmaticurl.com/book-sample ) I suspect the target audience is extremely junior people. The sample content starts by explaining things like the difference between backend, frontend, and mobile. Also the writing style feels reminiscent of what happens when you ask ChatGPT too broad of a question: You get an overly generic response that assumes you’re starting f…
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.
So why is the preview talking about how to pick first and second programming languages?
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'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'm not sure what's frustrating your career, but most of us are actually working outside of FAANG and doing really great engineering with skills and experience that compound year over year and more than enough income to live very comfortably.
Find the domain that you want to work in and stay focused on it. Build relationships; earn trust; and contribute good, thoughtful work.
You will probably not make as much money as the FAANG people, but you also won't be caught in vicious political fighting for interesting roles and will enjoy much more personal agency when not wearing their golden handcuffs. But you'll get to get better at building things, and if you focus on a domain you actually care about, the things you build will feel cool to you.
I don't want to progress my career. I want to get better at building things.
- The C Book
- GOF Book
- The Dragon Book
- TAOCP Book
- The Rust Book
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.
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 now regularly have days where I'm pretty much fulltime coding! (And headspace to develop new initiatives outside the team; an unexpected benefit/distraction.)