March 7, 2007

Best Practice

I won't be the first to offer argument against doing things according to so called "best practice". I feel that if a methodology is adopted as a "best practice" then it probably would be worth my time to follow. I would however put my 2 cents in and say that if all else fails, do something right.

Best practices are exactly what they claim to be: practices. Sometimes we (especially as software developers) get so caught on following the latest best practice that we fail to deliver the most important thing: the product (and yes I am insinuating that these best practices change and often).

It's not so much that best practices aren't worth their salt (it's an expression, look it up) that they are constantly replaced, but practice can only be based on current knowledge (scope if you will). You can only practice what you currently know, and as you practice you may learn better or quicker solutions that you can practice later.

But while I'm honing my skills as a master methodoligist I need to remember that at the end of the day I still have to deliver a product (in my case software) and even if I'm the best at perfecting a practice if I don't deliver software then I don't pay the bills.

this rant brought to you by the letter b

Until next time


powered by performancing firefox

No comments: