Agile: The Good and Bad Parts

Agile: the Good Parts (according to Bertrand Meyer): developing in short iterations of two to six weeks … has profoundly transformed the software industry for the better. absolutely no one, regardless of rank, is allowed to add anything during [an] iteration. And now, some bad bits of Agile: the general rejection of what’s derisively called… Continue reading Agile: The Good and Bad Parts

SimpleProgrammer’s: 11 Rules All Programmers Should Live By

Yesterday’s Simple Programmer post has a lot of good ideas in it.  If you’re in a rush I give you the rules themselves below. Read his post for the details.

  1. Technology is how you get to the solution, it is not THE solution
  2. Clever is the enemy of clear
  3. Only write code if you absolutely have to
  4. Comments are mostly evil
  5. Always know what your code is supposed to do before you start writing it
  6. Test your sh—code before you ship it
  7. Learn something new every day
  8. Writing code is fun
  9. You can’t know it all
  10. Best practices are context dependent
  11. Always strive to simplify

He correctly predicted getting a lot of comment grief on number 4. I personally agree with him. Developers tend to over-use/mis-use comments.

#7 is a lot like yesterday’s post One-a-Day Keeps Mediocrity at Bay.

YMMV: Try out TutsBucket

TutsBucket.com

Tutorials and resources for web developers and hybrid mobile developers

@ManagerJS was recently followed by @tutsbucket. With it following over 1,800 users that’s probably not much of an honor. 😉 Still, the website looks like a useful collection of tutorials. Your mileage may vary.