|
We hear a lot of things about best practices, quite a lot, actually. However, the question I've linked to has a great answer for why it's important to evaluate best practices. My real question is, what are the criteria that something fits into before we can call it a best practice? What makes criteria makes version control a best practice? What criteria does premature optimization miss such that it is not a best practice? |
|||||||||
|
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
|
I consider it to be a passing title that doesn't mean all that much. It's like a product that has a good review, enticing you to check into it further. Using a hammer was best practice at one point, but once the nail gun came around it became best practice. The hammer still works just fine, though. Version control is a great way to manage a changing code-base, especially with multiple developers. It's an incredible tool, and an obvious candidate for being labeled as a best practice. Premature Optimization is negatively connoted right in the word, so people are definitely not going to consider it a best practice. It's all about what a group of people think and attribute to something, and could be very objective or completely subjective, depending. |
|||
|
|
