Engineers Survival Guide: Advice, tactics, and tricks

I really wanted to like this book, but it was a lot of cookie cutter lessons and stories from folks who have worked in Software Development or IT in Silicon Valley. Reads more like a collection of blogs than anything with a demonstrable point. Some of the super short stories are great, don't get me wrong, but as a whole - definitely not worth $30.

A friend of mine recommended this book to me despite not having much knowledge in software engineering. Ive dabbled in it here and there but have never thought of it as a profession. I didn’t understand the recommendation at first and was skeptical, But after the first few chapters I fully understood why! This book has so many layers to it. There’s so much to be learned from it. The majority of the tips, tricks and advice can easily be transferred into any corporate work place! There’s was so many Parts of this book where I felt that the author was speaking directly to me! Merih does a great job of translating his own beginner experiences into a way that an up and comer can relate to. I’m very impressed with the simplistic nature of his explanation/experience with working in corporate America and all of the nuisances involved with it. Thanks to my buddy for bringing this book to my attention and Kudos to the Author for helping me feel more confident in my new endeavor.

Put down the technical books for a bit and explore the more personal side of your career. You will be enlightened by the authors advice, I promise.

"Engineers Survival Guide" is a valuable handbook for senior/lead engineers and people with such roles shortly. The book is a set of advice about surviving and being a valuable part of the company and project. From my point of view, it contains a lot of precious information and advice; I have worked as a senior developer for almost eight years, and I a lot of bits of advice and ideas what the author provides in this book are close to me. Still, I remember how hard it was to realize some ideas. The book is well-structured, contains around 60 chapters (each chapter is an idea/advice), and has different areas: starting with fundamental software development principles and progressing to more advanced topics, including project management, performance optimization, and teamwork. There is a common phrase: "Only a fool learns from his own mistakes. The wise man learns from the mistakes of others." this book definitely can help you learn from other mistakes and the pain of the other person. The author presents information clearly and accessible, using straightforward language and real-life examples from their experience. It's clear to read even if you do not read much English literature.

Best book on engineering survival tactics by far! Mandatory read for anyone at any stage in your career. Loved how the author summarizes each chapter with a handy survival tip

I really enjoyed reading this book. I love the fact that the tips are very “byte-sized” and straight to the point. One thing I would note is that the author clearly mostly worked at product-based companies (Microsoft, Snap), so not everything in the book is applicable to people at service-based companies. With that being said, the book still has great value for engineers of any level.

I really enjoy reading books and the advice and the stories I really founded I interesting and motivated

You can definitely tell this book was written by an engineer. Chapters are short and to the point with tldr summaries at the end. PROS: 1. Useful tips for working at a big engineering company 2. Applicable and practical 3. Completely relatable One of my favorite chapters was one-on-ones with leadership. I too used to HATE one on ones. I felt so much pressure, but after reading this book, I realized that one-on-ones is for MY benefit and I need to be the one to steer these one-on-ones so that I can get the most out of it. My only feedback is that there are certain chapters that left me wanting more and wished the author would go in more depth. For instance chapter 21: The importance of Tools and Patterns and chapter 46: Knowing Popular Framework and How They Work. I was engaged and wanted to know a little more about how do I know if a framework or tool is worth the investment? How do I know if I'm choosing the right one? How do I get over my decision paralysis!