PurPassionAll fields
Digital / Everywhere zone

Software Engineering

Roles 5Reads like Building, then fixing

5 roles live in this world

↗
Backend Developer
You build the part nobody sees.
Creation · Nothing → Something
↗
Frontend / UI Developer
You build the part everyone sees and touches.
Creation · Nothing → Something
↗
Machine Learning Engineer
You build systems that learn from data instead of being explicitly programmed.
Discovery · Unknown → Known
Unexpected
DevOps / Infrastructure Engineer
You build and maintain the ground that other software runs on — servers, networks, deployment pipelines, monitoring, and security infrastructure, the invisible layer that lets applications exist in the world and not…
Organization · Disordered → Ordered
↗
Full-Stack / Product-Focused Developer
You build the whole thing, or at least enough of the whole thing to ship it.
Creation · Nothing → Something

Nothing exists, and then you write something, and then it does something. That is the core of it. Software engineering builds working systems out of pure logic — no raw materials, no physical constraints, just a long chain of "if this, then that" that, once written, runs on its own and keeps running when nobody is watching. A thing you build can be used by one person or a billion, and the marginal cost of the billionth copy is essentially zero. No other field has quite that property, and it is the reason a single person at a kitchen table can build something that reaches the whole world.

It is tempting to call the structural pull Creation, and Creation is genuinely half the life of the work. But the honest version of the field, the one a 17-year-old needs to hear, is that the dominant daily pull is Resolution. Software does not stay built. It breaks — constantly, in ways nobody predicted, across layers of systems other people wrote years ago and documented in a hurry. The running joke in the field is that you spend twenty percent of your time writing new code and eighty percent figuring out why existing code does not do what it claims. The defining act, the thing that fills most working hours and separates the people who last from the people who burn out, is the move from broken to functional: tracing a failure through a system you only partly understand, forming a hypothesis, testing it, and making the thing work again. The people who thrive are the ones who find the debugging as satisfying as the building, who like the puzzle as much as the product.

🦊
There's a guide here if you want one

Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.

Software Engineering · PurPassion