There's too much information. Any jamoke with an internet connection can write a blog and consider themselves an epic hax0r for following <latest nifty developm

There's too much information. Any jamoke with an internet connection can write a blog and consider themselves an epic hax0r for following <latest nifty development principle>. People get bogged down worrying about idioms - am I following SOLID? Would Uncle Bob like my code? Am I writing unit tests? Should I mock my foo class, or maybe make it a stub? Should I integrate my build with Jenkins, and set up email automation when builds fail? Should I follow the factory decorator observer enterprise pattern? The result is lots of time spent sweating over whether or not you're following the latest snake oil pamphlet of "best practices" published on whatever hip tech site you frequent. The days of putting your head down and cranking out functional code and worrying about how "clean" it is later are mostly gone. Programmer productivity has plummeted. Complexity has increased exponentially for simple tasks. It's not great.