Love the concept, but after reading the sample ( <a href="https://pragmaticurl.com/book-sample" rel="nofollow noreferrer">https://pragmaticurl.com/book-sample</a> ) I suspect the target audience is extremely junior people. The sample content starts by explaining things like the difference between backend, frontend, and mobile.<p>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 from absolute zero knowledge about anything about the topic. Probably a great book for someone starting from absolute zero industry knowledge who wants each thing explained in the simplest terms possible.
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<p>I wonder if it’s difficult for companies to find VPs of engineering, staff engineers and engineering managers
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.<p>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.
> Navigating senior, tech lead, staff and principal positions at tech companies and startups.<p>So why is the preview talking about how to pick first and second programming languages?
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.
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.