Over a decade of production experience, written down

Why this exists

Every tutorial I found when I was learning ended in the same place. You get a working feature, the page congratulates you, you close the tab.

The questions that decide whether software survives start one step after that, and almost nothing went there. Where does this logic belong? What breaks when the team doubles? Which of these two reasonable options will I regret in a year?

Books and conference talks explain the ideas. They don't tell you when to reach for one, why, or which fits the problem in front of you. That judgment is the actual skill, and it's the part nobody writes down. Nobody builds an entire product in the open with all of it applied together either, where you can follow the decisions in the order they get made.

So I learned it the slow way. Making the call, shipping it, living with the result.

Then I started writing it down.

Codyssey is one place for the part that comes after the fundamentals: building software that stays maintainable for years. System design, software architecture and design, infrastructure, planning, refactoring, and testing. Courses and learning paths that go past the happy path. Code reviews where I read real code and say what I'd change and why. Insights and quick tips for the decisions that come up in between.

None of it is tied to a framework or a tool. The systems I've worked on had almost nothing in common technically. The decisions that mattered were the same every time.