Developer Professionalism Guidelines

Apr 3, 2012

This post is a reminder to me of the importance of professionalism as a developer. It’s way too easy to fall into a trap of quantity and speed over quality and deliverable software. The following is a (growing) list of things that I think are important in preserving professionalism when creating software.

  • Never write code until you completely understand the problem.

  • Strive for zero bugs in production code.

  • Plan and write your code for simplicity and future collaborators.

  • Empower users to perform tasks free of developer interaction.

Hit me up on Twitter if you have more @scottradcliff

If you enjoyed this and would like to be notified the next time I write something, you can subscribe with your choice of RSS or Email.

I promise not to spam you and you can unsubscribe at anytime.

Also, here are some other items you might like longer longer:

or go see everything in the archive.