Books I recommend

Atomic Habits (James Clear) is a fascinating book. This book helped me understand how habits are formed and how to create systems that will help us achieve our goals. By following this simple framework, we can create lasting change in our lives. Must read for everyone trying to get better at something.

Show Your Work (Austin Klein) is a great book to motivate you to do something in public. There are two key points that I’d like to highlight from this book:

1. Share your work even if you’re not an expert. Share everything, your journey, your failures, your backstage.
2. By sharing your work, you attract similar people who care about the same stuff you do – this can lead to many opportunities that have the potential to change your life.

The key points of “The Unfair Advantage” by Ash Ali and Hasan Kubba are that success in the startup world requires a unique approach and mindset. The authors advocate for a focus on execution and a willingness to take calculated risks, as well as a commitment to constant learning and adaptation. They also emphasize the importance of building a strong team and fostering a culture of innovation.

Overall, the book offers practical advice and strategies for achieving success in the fast-paced and competitive world of startups.

In his book “Can’t Hurt Me” David Goggins shares his journey of overcoming adversity and pushing himself to the limits, both physically and mentally. This book is a sort of motivational book, but I think it’s also useful for Software Engineers looking to get into discipline and callous your mind. (Callousing your mind means you have to intentionally expose yourself to discomfort and pain.)

Some interesting takeaways:

1. Embrace change, learn new skills, and be open to feedback and criticism. It will be painful, but it will get easier.
2. Set big, audacious goals to get to the next level: Strive for a leadership position, take on a challenging project, or learn a new programming language.
3. Embrace discomfort and never give up: Goggins talks about how he pushed himself to the limit, physically and mentally, in order to achieve his goals.

Clean Code is a must-read book for any software engineer, it was written by Robert C. Martin and covers topics such as naming conventions, structure, functions, and classes, as well as design patterns and testing. I’ve read this book several times once I was studying SE.

One of the key principles of clean code is the concept of “writing code for the next person” – meaning that the code should be easy to read, understand, and modify by other developers that come after you.

Other key takeaways from the book include:

• The importance of simplicity and avoiding over-engineering solutions
• The reasons why you should follow industry standards and best practices
• The value of collaboration and communication within a team.