Why Senior Devs Write Dumb Code and How to Spot a Junior From A Mile Away


One of my all time favorite quotes is from Brian Goetz, a smart dude in the Java world who is one of the authors of Java Concurrency in Practice, among other things. The quote appears in an interview that Oracle published under the title, “Write Dumb Code”. Goetz was asked how to write code that performs well. Here is what he had to say:

Often, the way to write fast code in Java applications is to write dumb code — code that is straightforward, clean, and follows the most obvious object-oriented principles.

The rest of the ~1000 words is devoted to explaining why trying to optimize code and trying to be clever is a common programmer mistake 

Read more at HackerNoon