The great mathematician Carl Jacobi once said “Invert, always invert”. He advocated that, by analyzing a problem backward, one could uncover the best solution to it.
With that in mind, Berkshire Hathway’s legendary partner Charles Munger gave a terrific speech to the Harvard School on how to not be successful (I originally read this and other Charles’ speeches in the amazing Poor Charlie’s Almanack: The Wit and Wisdom of Charles T. Munger). That made me think – how is the easiest way to become a bad developer?
What you will see next is a highly subjective, non-exhaustive unordered list of principles that, if you follow, I can guarantee will lead you to become a bad developer. I say “principles” because I am not interested in technicalities (e.g. choose bad variable names, never comment your code, etc), once they are a sub-product of the guidelines you follow.
If your goal, fellow reader, is to become a good developer instead, don’t worry. Remember that via negativa is way more powerful than via positiva. That means that knowing what notto do is safer and easier to figure out than exactly what to do. So pay attention to the following topics and decide which type of developer you want to be.
Read in full here:
This thread was posted by one of our members via one of our news source trackers.