The engineer as a social type
What it means to «write code» in the platform economy — and who the work makes you.
An engineer is used to thinking about themselves technically: I solve problems, design systems, write code. This is true, but it is not the whole truth. A profession is also a social type: a set of habits, values and ways of seeing the world that work forms and that the worker often fails to notice, because they have become second nature.
01What code does to thinking
Anyone who writes code for long begins to see the world as a system that can be decomposed. Every problem invites being broken into modules, finding interfaces, removing duplication. It is a powerful lens — and it is not neutral. It works well where there are clear boundaries and badly where ambiguity, history and context matter. The engineer as a type tends to overrate what can be formalised and underrate what resists it.
The habit of seeing the world as a system to be decomposed is not a neutral skill but a particular way of looking.
02Autonomy and its limits
Engineering work seems autonomous: you decide how to structure the code, you are valued for expertise, you are not on an assembly line. But this autonomy is partial. What to build, for whom, on what terms — these questions are usually decided not by the engineer. Freedom in the how, unfreedom in the what and the why. It is a convenient arrangement: it gives a sense of independence without ceding control over direction.
Hence a characteristic tension in the profession. The engineer takes pride in craft while often dimly sensing that the craft serves ends they did not choose and sometimes do not share.
03The platform changes the type
In the platform economy this type changes. Work is increasingly mediated by tools that are themselves built like platforms: trackers, CI/CD, dashboards, metrics. Productivity is measured and visualised. The engineer both builds systems of observation and becomes their object. The line between the one who designs control and the one subject to it runs straight through the profession.
Add to this the figure of the entrepreneur from the neighbouring texts: the engineer is increasingly invited to treat a career like a startup, skills like capital, the self like a project. The profession absorbs entrepreneurial logic even when the person formally remains an employee.
04Why see this
I write this not to devalue the profession — I am in it and I love it. I write to give it back its depth. An engineer who sees themselves only technically easily becomes the executor of others' decisions with a craftsman's pride. An engineer who understands themselves as a social type can ask different questions: what am I actually building, whom does it serve, which consequences am I leaving in by default.
That is the point of the view from within: not to abandon craft but to add to it responsibility for direction. Code is a social practice. Which means the engineer is not only a specialist but a participant in how shared life is arranged.