From Building Projects to Building Systems

When I started building projects, my main goal was simple: make the application work. A button should do something, a page should look good, and the API should return the expected response.

But after building projects like Wanderly, AI-powered applications, and machine-learning systems, I realized that writing code is only one part of software engineering.

The interesting problems often appear behind the interface — how data flows between services, how APIs are designed, how authentication is handled, how databases are structured, how applications are deployed, and what happens when something goes wrong in production.

That shift in mindset is one of the biggest parts of my journey from simply building projects to understanding systems.

I am still learning. But now, whenever I start a project, I try to ask a different question: not just 'How can I build this?', but 'How should this system work?'