26 ms·

> A certain sensibility of care and craftsmanship has faded away. It got replaced with professionalism, as in "being a professional", which nowadays seems to m

> A certain sensibility of care and craftsmanship has faded away. It got replaced with professionalism, as in "being a professional", which nowadays seems to mean prioritizing business needs above all. Caring about quality and craftsmanship is not professional - it's just not being economical with company time and money. It's better for the business for dev teams to tick features off a list as quickly as they can, because marketing can polish a turd and shove it down customers' throats much more cost-effectively than devs can make a half-decent piece of software that provides genuine value. No surprise more and more people don't care. They keep hearing everywhere - including here - they should abandon childish pursuits, stop reinventing the wheel, writing too clever code, shaving yaks, going down rabbit holes, etc. - they should be professional. Well, that's what we're getting now.

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.
Glawen 2y ago
It sure makes children cry when we talk about quality. Thing is, who holds the truth with respect to quality and craftmanship? And how to identify the person which will improve quality ? Which path is best to follow ? I inherited a failed project, where each team member developped a repo. Nothing is unified, and it's a big architectural mess. Nothing really stands out, but god did I hear them crying about giving them time to build quality software.

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.

Glawen 2y ago

It sure makes children cry when we talk about quality. Thing is, who holds the truth with respect to quality and craftmanship? And how to identify the person which will improve quality ? Which path is best to follow ? I inherited a failed project, where each team member developped a repo. Nothing is unified, and it's a big architectural mess. Nothing really stands out, but god did I hear them crying about giving them time to build quality software.