3 ms·
> Caring about quality and craftsmanship is not professional - it's just not being economical with company time and money. I disagree, but only partially. The
by bluGill 2y ago
> Caring about quality and craftsmanship is not professional - it's just not being economical with company time and money.
I disagree, but only partially. The real question is when is the project done as in you would shred the source code and nobody would ever care. Some projects are done when they ship version one - you wouldn't fix any bugs or add new features, so code quality doesn't matter. Some projects are never done - someone will be touching this code in 50 years (after you are dead), so quality matters.
If the code is done then craftsmanship doesn't matter and putting effort into it is an unprofessional waste of time. However if the code will be maintained for years in the future then not putting effort into craftsmanship is unprofessional. You need to know where you are. Sometimes writing ugly code is a good use of your time, sometimes writing good clean code is well worth it.
The important thing is to know where you really are. The wrong choice will hurt you.