1. Stop theorizing 2. Write lots of software 3. Learn from your mistakes
@codinghorror @CodeWisdom Agree! Also, you can't write any software without at least /some/ theory of what it should be good for!
@codinghorror i.e: PROGRAMMING MOTHERFUCKER programming-motherfucker.com
@codinghorror @RobAshton Write lots of software != release lots of software.
@codinghorror "write lots of software" quantity over quality?
.@codinghorror @anjacks0n provide constructive feedback for those trying. Don't simply criticise. Look outside your own style.
Show me the code ;) Via @jmbeas @codinghorror: 1. Stop theorizing 2. Write lots of software 3. Learn from your mistakes”
@codinghorror If you build it they will come. If they don't, you still built something
@codinghorror When do you get to "5. Profit!"?
@codinghorror is this tweet inspired by @headinthebox recent talk?
“@codinghorror: 1. Stop theorizing 2. Write lots of software 3. Learn from your mistakes” 4. Test in Production
@codinghorror 4. Help others learn from your mistakes; 4;
@codinghorror 4. Start theorizing again, 5. Goto 1.
@codinghorror He means write lots of good software. Mind the subtext. :)
@codinghorror Misinterpreting this tweet is why most developers never ever get good
Agreed. It's all about "doing" RT: @codinghorror: 1. Stop theorizing 2. Write lots of software 3. Learn from your mistakes
"@codinghorror: 1. Stop theorizing 2. Write lots of software 3. Learn from your mistakes" Replies to this show Waterfall is alive and well
@codinghorror 2/ corollary is that you can't learn from your mistakes...
@codinghorror 1/ the problem is that programming languages have no semantics to write code in the conceptual view ebpml.org/blog2/index.ph…