What does craftsmanship mean as a company value?

Doing the version that will still be good when somebody else has to work on it. It is a judgement about the second person to touch something, which is why it always looks slower than it needs to be at the time.

How do you recognise craftsmanship at work?

Say what it cost and that it was right. The behaviour looks like over-investment in the quarter it happens, and the only thing that makes it survivable is somebody senior confirming the trade was correct.

Is craftsmanship at odds with shipping quickly?

Not in the version worth recognising. Doing something quickly on purpose and saying so is craftsmanship. Doing it quickly and leaving no trace is what makes a codebase unpleasant three years later.

What craftsmanship goes unnoticed most often?

Edges. Empty states, error messages and behaviour on a slow connection are rarely specced, rarely demoed and always the first thing a user hits when something goes wrong.

Company values

Craftsmanship

Craftsmanship is the value most likely to look like underperformance in the quarter it happens and obviously correct two years later.

It looks like slowness at the time

An extra day on the migration. Pushback on the quick approach. The empty state nobody asked for.

All of it reads as over-investment in the quarter it happens. It becomes obviously correct about eighteen months later, by which point nobody remembers who made the call.

Say it was right

That gap is the reason this value needs recognition more than most. The person making the judgement is absorbing a visible cost now against an invisible benefit later, and the only thing that makes that sustainable is somebody saying out loud that the trade was correct.

How you would know

Leaves it better: Improves the thing next to the change, without being asked or filing a ticket.
Names the shortcut: Says out loud when something has been done quickly on purpose, so it can be found again.
Finishes the edges: Handles the empty state, the error copy and the thing that happens on a slow connection.
Refuses the version that will hurt: Pushes back on an approach that works now and will be expensive in a year.

6 messages that name it

You handled the empty state and the error copy without being asked. Nobody specced either one.
Peer
Names the two things always cut first.
Thank you for the comment explaining why rather than what. The code was clear; the reason was not.
Peer
A precise distinction engineers recognise.
You said out loud that the shortcut was a shortcut. That is how we found it again in June.
Manager
Recognises labelling debt as a real practice.
Elena spent an extra day on the migration so nobody would have to do it twice. She was right.
Manager
Includes the verdict, which is the point.
Thanks for pushing back on the quick version. The quick version would have been our problem all year.
Manager
The counterfactual, stated as a cost.
You fixed the thing next to the thing you were fixing. That is why this area is pleasant to work in now.
Peer
Connects a habit to a lasting property.

What its absence looks like

Where craftsmanship is absent, everything ships and everything is slightly painful to change. Nobody can point at a decision that caused it.

Recognising it well

Recognise it in the quarter it costs, not the year it pays. Nobody needs convincing in year two.
Name the specific edge. Empty states, error copy and slow connections are the first things cut and the last things thanked.
Thank the labelled shortcut. Craftsmanship is not refusing to move fast; it is leaving a note when you did.

Questions people ask

What does craftsmanship mean as a company value?: Doing the version that will still be good when somebody else has to work on it. It is a judgement about the second person to touch something, which is why it always looks slower than it needs to be at the time.
How do you recognise craftsmanship at work?: Say what it cost and that it was right. The behaviour looks like over-investment in the quarter it happens, and the only thing that makes it survivable is somebody senior confirming the trade was correct.
Is craftsmanship at odds with shipping quickly?: Not in the version worth recognising. Doing something quickly on purpose and saying so is craftsmanship. Doing it quickly and leaving no trace is what makes a codebase unpleasant three years later.
What craftsmanship goes unnoticed most often?: Edges. Empty states, error messages and behaviour on a slow connection are rarely specced, rarely demoed and always the first thing a user hits when something goes wrong.