2 Non-Programming Books That Changed My Life

Coding is challenging. You can spend days solving a single bug. Most of the times it’s not actually you. It’s not that you lack foundation on a programming language or framework. And definitely not an advanced topic  you need from books or watch from YouTube. 

Sometimes it just about changing and developing some habits.

I share to you two non-technical books that actually helped me become better at coding.

(1) Why We Sleep: Unlocking the Power of Sleep and Dreams by Matthew Walker

I know. It sounds funny that the first book that I recommended is a book about sleep.

But you know how it is and it happened to me lot. You spent an extended 4 hours solving one bug in your code only to solve in 5 minutes after taking a quick nap or getting  30 minutes of break with a clear mind.

 Walker explains the science behind how deep REM sleep boosts productivity. His insights changed my perspective on the relationship between productivity and the number of hours spent working. I used to sacrifice sleep, working for extended hours with little rest. However, I discovered that a good night's sleep significantly enhances my productivity, allowing me to solve difficult problems more efficiently with less effort. 

There is a beautiful science around our brain’s repair and strengthening during sleep that enforces learning and improve our problem solving skills. 

You won’t get bored reading Walker’s book on Why We Sleep by Matthew Walker

  

(2) Show Me Your Work by Austin Kleon

I must admit. I don’t have a good memory. 

Countless times when I solve a bug for hours and then when that problem occurs after a week, I would forget how I solve it.

The book Show My Your Work by Kleon talks about the benefits about documenting your everyday work. 

The book is my inspiration on starting this blog. I write every single problem (big or small) I encounter in my programming career. I wish I had started blogging when I started learning programming but since I still encounter problem everyday even as an experienced programmer there is always something to write about.

 How does writing and documenting improved me as a programmer? 

 Well, when I encounter the same bug I fixed a week or months ago, I could get a quick reference on how I fixed it and its easier to recall it because I wrote it myself.

Also, when you write a bug and document in details on how you solve it, you get a clearer understanding on the root of problem. 

 How about you? Do you have a non-programming book that improved you as a programmer you will like to share? Comment down below. Would love to hear your experience.