[wiether]

I used to be intrigued by _software craftsmanship_, but I mainly saw people using it to practice heavy gatekeeping. Be it on the job, in code reviews, in job interviews...

Furthermore, given how they behave in a cult-like way, it feels like they are straight-up delusional.

People working as consultants for big retail chains, talking all day long about "the craft". Nobody cares. They sell trash. They don't put marble in their store. They don't want fancy software. Furthermore, if, by trying to force "the craft" to their peers, all they do is making the life of others miserable... Just stop. Please.

Now my approach is as follow:

if stakeholders are only interested in two things (how-much it cost, when it's ready), which is 99% of the case at $JOB, then make something that does the job and that won't make you hate yourself if you have to maintain it in a year

if I'm the stakeholder, like creating internal tooling that nobody asked for but that will solve issues, then yes, I do things as good as I want them to be

same for working on FOSS on my personal time

[port11]

The one issue that stands out is that, by optimising for cost and time now, you might build unmaintainable messes for later. Therefore, later the cost and time goes up.

EDIT: child commenter is right, my bad.

[munksbeer]

In the post they already addressed that

"and that won't make you hate yourself if you have to maintain it in a year"