s4.codes exists to make you a better engineer.
It explores the principles of the craft, so you can look at a design or a piece of code and know whether it’s good, and why.

What is s4.codes for?
What makes an engineer good is the decisions behind the code: how a system is shaped, what changes, and what stays as it is. Those decisions come from understanding the craft, and that understanding is what s4.codes is about.
The lessons explore the principles and ideas that make an engineer good at the job, and explain them clearly. The next time you face one of those decisions, you can make it well and know why.
Doesn’t AI write the code now?
Many people believe it does. The tools write working code in seconds, so learning the principles behind good software can seem optional. It’s a fair thought, and the tools really are that fast. But they don’t replace an engineer.
AI tools multiply what you bring to them.
You still decide what to build, how to structure it, which of the generated code to accept and what to fix when something goes wrong. Making those calls well comes from understanding the craft.
Without that understanding, faster generation just means more code nobody can judge. With it, the same tools make a good engineer faster. That’s why the craft is worth more now, not less.
How do the lessons help?
They’re clear to follow. Each idea is explained so you always know what’s happening and why.
They’re good to watch, too. Visuals and animation show each idea at work, so you see it as well as read about it. The lessons come as courses, blogs and videos, and they cover whatever makes an engineer better at the craft.
Where should you start?
The lessons make the case better than this page can, so the best next step is to try one.
If you’d rather go deeper, see the courses. And when you only have a minute, watch the short videos.