プロフェッショナルの条件

自戒を込めてメモ

ref http://www.killersoft.com/randomstrings/2006/02/16/walk-the-walk-before-talking-the-talk/

It doesn’t work that way in professional development; You’ve either got the chops to call yourself a pro, or you don’t. And more importantly, you either behave like a pro, or you don’t. You can’t just claim to be a professional software developer, and in the act of making that claim, become one.

I was reminded of my thoughts along these lines today after reading Ian Kallan and J. Scott Johnson’s discussion regarding PHP Best Practices.

What professionalism boils down to in software development (and acting, for that matter) is one thing: discipline.

• You must be disciplined enough to write good code.
• You must be disciplined enough to write well-documented code.
• You must be disciplined enough to use source control.
• You must be disciplined enough to write unit tests.
• You must be disciplined enough to write code with error reporting (by whatever name your language of choice calls it) cranked to the max.
• You must be disciplined enough to be disciplined even if you’re the only one working on a project.