I rebuilt eddn.dev to serve as my engineering notebook. It is where I can explain Achronyme, document production work, and keep a record of decisions that would otherwise disappear inside commits and issue threads.
What 2025 changed
2025 was difficult. I was recovering from burnout while trying to turn scattered experience into work I could stand behind. Production incidents taught me more about software than polished demos did. CI stopped being a badge in a README and became the place where I learned which assumptions only held on my computer.
Freelance work was difficult for a different reason: before people know your name, they have little reason to trust a claim about quality. Friends helped me find the first projects, and Sylestudio gave me room to contribute while I was still learning how to present my work clearly. I am grateful for both.
What this site is for
In 2026 my main technical goal was to publish a usable Achronyme release. I also wanted to study low-level systems more carefully: memory layout, virtual machines, compilers, cryptographic circuits, and the less glamorous work required to ship them.
I use code assistants, but I do not want generated prose or generated code to stand in for understanding. The useful standard is simple: I should be able to explain a decision, test it, and show the evidence behind any public claim.
This site applies that standard by recording the technical work behind the things I build.
Update, August 2026: the first stable goal is complete. Achronyme 0.1.0 is published, together with the evidence that held the release back.
Edd.