The Clean Coder (Week 1)

This was my first time reading this book, and so far, i’ve throughly enjoyed it. Prior to reading the book, I took a stab at what kind of book this would be. Based on the title, i figured that the book will touch base on the qualities of being a person who appreciates their craft. After reading the first two chapters, this book does just that. It explains in details of how one should go about on being professional. One of my favorite lines from the book is on continuous learning.

Would you visit a doctor who did not keep current with medical journals? Would you hire a tax lawyer who did not keep current with the tax laws and precedents? Why should employers hire developers who don’t keep current?

I found this quote to be quite thought-provoking, because i’m a believer that learning is never done. Learning is a life long process and that I too, would hope my doctor would be up to date with his medical journals, and if I have a tax lawyer, that he/she would keep current with the tax laws and precedents. The same thing goes for software developers. The industry is currently changing and concepts that you may have grasped and think you know well, might not be relevant in future frameworks. For example, after doing a little reading about AngularJS two, a javascript framework, migrating from AngularJS one to the newer version won’t be a walk in the park. Things that will work in AngularJS one won’t work in the newer version.

The second chapter touches base with the idea of saying “no” in the workforce. When you are first starting out, you want to excel and meet every expectations and demands that are laid out by your boss. You do so by doing your work to the best of your ability, but when you are given a project with a lot of features to include and you know that father time is not on your side, it’s hard to say no. You end up saying “yes” just to keep everyone happy. By everyone, you mean everyone, but you. This then could result in you being burnt out and have completed it(but did a crappy job), or more commonly, you’re boss and the customer isn’t very happy because you promised x, y and z, but could only deliver x. It’s important to say no, because it could prevent all of the headaches and unwanted meetings with angry customers wondering why something isn’t finished.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s