A trade that found out it was a craft
Software engineering started describing itself in workshop terms (code smells, refactoring, patterns) without deciding to. What that vocabulary lets you say about the trade, and its limits.
You can draw up the chronology: Turing, then the languages, free software, agile methods and the platforms. It is accurate and teaches nothing. One fact is more interesting. In the late 1990s part of the profession started describing itself in terms of craft (code smells, refactoring, design patterns) without having decided to, like Molière’s bourgeois discovering he has been speaking prose for forty years.
The most telling lineage comes from architecture. Design patterns were taken from an architect trying to name the configurations that make a place fit to live in. The word passed into computing along with the idea that a trade advances by writing down what works, instead of rediscovering it on every project.
- Judging a piece of work by whether someone else can take it over. A craftsman delivers an object another person can repair, and that criterion still holds after its maker has left.
- Talking about apprenticeship rather than level. You progress by taking on problems slightly harder than the previous ones, and a change of job title makes no difference to that.
- Treating endurance as a skill. Like an athlete, you train to last while avoiding injury, which means also counting the periods when nothing is produced.
The analogy confers no title. In France artisan is a status tied to registration, and IT consulting does not fall under it. Nor does it say anything about working conditions: psychosocial risks, impostor syndrome and overwork cultures are not resolved with workshop vocabulary. A profession that describes itself as a craft while exhausting its practitioners has taken over only the vocabulary.
Once the analogy is set aside, what remains is what can be checked: work another person can read, an apprenticeship measured by the problems solved, a practice organised to last.