4 ms·
best approach for software development: trial and error
by rjzzleep 14y ago
best approach for software development: trial and error
- rjzzleep 14y agonext best approach for software development: stop talking start acting
- k_bx 14y agoNo, it's been there for a while already http://programming-motherfucker.com/ http://programming-motherfucker.com/
- jetsnoc 14y agoI always tell my team "there are people who program and then there are people who /talk/ about programming, be the former" I always try to hire the ones who program. People who program learn domain knowledge and become better developers through ... writing code.. their managers leadership and not talking about methodologies all day long but actually executing and learning from their mistakes! I tell them if they'll get to work -- I will worry about requiring things like testing frameworks that add overhead but only when they add more value than the overhead costs.
- 5h 14y agomethodologies attract cringeworthy acronyms, lets dub this gtfowidd, get the fuck on with it driven development, and lets all just go back to however we were doing it already ;)
- bitwize 14y agoA.k.a., Programming, Motherfucker!
- jawr 14y agoI think the best approach is whatever feels like the best.
- Apocryphon 14y agoLike all methodologies, it has a formal name despite its informal nature: http://c2.com/cgi/wiki?CodeAndFix http://c2.com/cgi/wiki?CodeAndFix
- rjzzleep 14y agowow, i can't tell if its irony or not. who said you can't do trial and error coding without a certain amount of standards, which include coding standards, dry, peer reviews etc.? sure, you can squeeze out some ok code from bad developers, by making them follow enough conventions. but are they really what you want in your company? "i don't have a choice, that's not my company and not my employees" - sure you do. build your own