ABOUT
The engineer behind the project
Software, engineered. Not just written.
Millwright-Inspector grew out of one engineer's conviction that building software well is an act of engineering, not just typing code. This page is about the person who shaped that idea, and the path that led to it.
WHO I AM
Emin Akkoç
I'm a software engineer based in Ankara, Türkiye. I hold a Master's degree in Software Engineering from the Middle East Technical University (METU) and a Bachelor's degree in Computer Engineering from Başkent University. My graduate work focused on the engineering side of software: how systems are designed, structured, and reasoned about, rather than on code alone.
Across more than a decade of practice I have worked at every end of a software product: backend services, frontend interfaces, system and architecture design, and the project management that ties delivery together. I have built and shipped production-ready applications, and that breadth taught me how a piece of software truly behaves once real people depend on it.
HOW I SEE IT
Engineering, not just coding
Hacking something together until it runs is the easy part. The work that lasts is engineering: understanding how a system fits together, why each decision was made, and how it will hold up as it grows and as people come to depend on it. Code is only the visible surface; the real craft lives in the structure, the reasoning, and the discipline beneath it. Millwright-Inspector exists to keep that discipline at the centre of how software gets built, even, and especially, when an AI is doing the typing.
ADAPTANCE
Built to keep adapting
Every leap in human history has been a story of adaptation. We learned to farm, to build, to industrialise, to compute, and at each turn the people and crafts that endured were the ones that adapted rather than resisted. Software engineering is living through another of those turns right now, as AI reshapes how products get built.
Adapting does not mean abandoning what we know. It means carrying our engineering judgement forward into the new way of working, keeping the rigour, the review, and the accountability while the tools change underneath us. Millwright-Inspector is one attempt to do exactly that: to adapt to AI-assisted development without surrendering the discipline that makes software trustworthy.