After reading Pragmatic Programmer at my recent vacation, I immediately found an urge to repeat myself and read it again.
Ironic that one of the most popular tips from it is “Don’t repeat yourself”. Even though the book was published in 1999 (before the agile manifesto), there are so many golden nuggets in the book, that I find myself constantly using it at work.
Many of the principles are well-known today — the DRY principle is constantly used when developing Ruby/Rails applications and is a good pointer to the ability to change code.
Many of the pragmatic tips are ubuquitous in Ruby on Rails and well known because of the popularity of agile principles. Still the book is good, relevant and everyday useful. And most of the tips from the book can be applied for motivation in the projects I work on.
Bonus link: Jeff Atwoods article about the Department of Redundancy Department:
I have an awfully hard time defending the unnecessarily verbose way objects were typically declared in C# and Java.BufferedReader br = new BufferedReader (new FileReader(name));
Who came up with this stuff?
Is there really any doubt what type of the variable br is? Does it help anyone, ever, to require anotherBufferedReader
on the front of that line? This has bothered me for years, but it was an itch I just couldn’t scratch. Until now.