Thirty Days to Better Software
- Share
-
- |
Read later
My Reading List
In Thirty Days to Better Software J.T. King blogs about Alistair Cockburn's Reflective Improvement practice can be combined with Steve Pavlina's "30 Days to Success" concept. Cockburn believes that you should take the time every so often to consider how you could improve the way that you work. For example, perhaps you want to consider adopting the practice of test-first development to improve the quality of your code or database refactoring to improve your database. Pavlina suggests that you try a new concept on a "30 day trial basis" in order to give it enough of a chance to work. King combines these two ideas in his blog. It's worth checking out.
Related Sponsor
Agile Project Management That Adapts With You. Provide your global development team a shared space that adapts to the way they work.
Educational Content
Concurrency in Clojure
Stuart Halloway May 17, 2013
Confessions of an Agile Addict
Ole Friis Østergaard May 16, 2013
Web Development: You're Doing It Wrong
Stefan Tilkov May 16, 2013
Programming The Feynman Way
Ben Evans May 15, 2013
Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think