Top 10 Reasons a Software Engineer Should Read
It’s time to add reading to your list of habits
If I went back in time, one of the things I’d tell my past self to do is read a bit more. Doing your day-to-day job and being in a comfort zone will make you feel comfortable and you might not feel that you are missing anything by not reading, but if you read, you’ll discover how much you were missing. I think reading is one of the most valuable skills one can have. This is why…
1. Exploring different concepts
You can certainly learn a lot from working in a company and having hands-on experience with the system you are working on. Still, you can end up being stuck in one way of doing things and not exploring other ideas, especially if you stay there for a long time (depth vs. breadth of knowledge).
Personally, I used to work for a big company where reliability and latency were very critical. In such an environment, synchronous communication between services is the preferred option. So although I was part of a critical team, I could not perform well in a design interview later because my event-driven design skills were too weak. I was not aware of how powerful asynchronous communications can be in certain scenarios. If I had spent some time reading a relevant book in this area, I would have…
