The Software Engineer's Guidebook (Software developer: A career guide for future seniors, techlids and staffers) (Category Engineering)

I recently finished reading the book by Gergeli Orosh, the author of the newsletter “The Pragmatic Engineer”, a former engineering manager at Uber and a developer at Skype/Microsoft and Skyscanner. I already am. told I read this book before I started reading it. Now, after reading this, I can share a brief sammari.

The book is well suited for engineers who want to go all the steps from June to Staff+ Engineer - some of the materials are addressed to all levels, and then the blocks for middle → senior → tech lead → staff go on increasing. The book is also useful for managers, especially those who try to remain “hands-on”. The book is broken into separate topics + there are bonus online chapters - Basic principles of career development paths, “owning” your career, performance review, promotion, how to work in different environments (start-up), change of job.

• Competent developer How to bring tasks to a result, writing code, development process, tools of a productive engineer. - Senior engineer. - interaction and teamwork, engineering practices, testing, architecture. - Techlid. (It doesn’t matter what position or role it is.) - project management, production, management of stakeholders, team structure and dynamics. - Staff/Principal Understand business, influence without authority, reliability and architecture. Conclusion + online bonus chapters to previous parts The book can be used as a desktop guide and read point by point, in the right place.

I found interesting career tips that increase awareness and success on the career ladder. - Own your career. Keep a log of completed tasks, regularly ask for feedback and make the manager an ally - this is a direct investment in promo. Prepare for performance review in advance Start collecting context and artifacts months before the review, helping the manager and calibration. - Promo is simple. "make upThe effect is important, but it is also necessary to demonstrate the next level of competence and coordinate complex initiatives. - Wednesday matters. BigTech and startups require different strategies; choose what is best for your goals and stage.

In principle, there are other similar books for IC and engineering managers, which I have already talked about. Will Larson's "Staff Engineer: Leadership Beyond the Management Track" is about how to grow and work in the staff branch without going to management. (see. review) Tanya Reilly, “The Staff Engineer’s Path” – a detailed guide to the role of a staff engineer: strategy, influence, quality standards (see. review) Camille Fournier "The Manager's Path" - Engineer's Path (see. review) Will Larson's "An Elegant Puzzle" - Systems View of Engineering Management and Organizational Solutions (see. review)

In summary, this book seemed to me quite practical and useful for engineers who want to consciously develop their careers not just by jumping levels, but by building the right engineering foundation and focusing on important issues at every stage from June to staff engineer.

#Engineering #Management #Leadership #Processes #Software #Career #Staff #Career #Architecture