4 ms·

I went through phases. At first I'd go on an on about having the most awesome process out of all the companies so as to make programming awesome software into a

I went through phases. At first I'd go on an on about having the most awesome process out of all the companies so as to make programming awesome software into an assembly line, then declare any programs written in Java or C/C++ to unmanageable untelligble dreck, to declaring assembly the best language because it gave you the most control. These days I'm in a phase where I am curious about improving the development process in simple (but high impact) ways that do not interfere much but nonetheless are hard to voice because of their social unacceptability, like not comparing developers quantitatively and changing the culture from "works on my machine, push!" to "test your damn shit!"

mikekchar 11y ago
It's interesting that this thread is so much more important than what the author was originally talking about. I hope he gets a chance to see it. A lot of us seem to follow the same path. We complain about the same things at the same time in our careers. We see our way around it only to meet another stumbling point -- that everyone else on the path has also hit. It is probably the most interesting (and annoying!) thing about my job ;-)