This. My company recently had a training session for their new development platform. Creating one entity with four attributes using "best practices" of TDD and abstracting everything resulted in over 20 Java and XML files and over 2000 lines of code. Each individual piece of that bloat had a somewhat reasonable justification, but the net result was just ridiculous. I had already decided to accept a less enterprisey job elsewhere, and am now even more convinced it was the right call.
As a web developer I've lately been noticing this problem as well. Pretty much everything I do lately is about integrating this or that API, producing a little bit of glue code and that's it.
Even working for startups mostly doesn't solve the problem ... what I need is a good algorithmic challenge. Something fun and cool.
But I fear I might have lost the ability to even design algorithms due to all this tools stuff.
16 comments
[ 3.9 ms ] story [ 53.2 ms ] threadMan, this place it very quickly turning into reddit with the voting.
http://www.findinglisp.com
How large is non-trivial? I've built some pretty big systems using only javac, java, a text editor, and make.
Suppose your car mechanic did that?
Even working for startups mostly doesn't solve the problem ... what I need is a good algorithmic challenge. Something fun and cool.
But I fear I might have lost the ability to even design algorithms due to all this tools stuff.