About

My journey into software engineering started with experiments, not formal theories. One of my earliest projects was a website for "Salon Cantik" that I built with my friend, Aldi Saputra (aldisaw). Later, I built a simple site on my own to share Bitcoin referral links.

The code was far from perfect. It was mostly native PHP, without frameworks or clean architecture. The project never really went live, but the experience was enough to make me curious. I started to understand that software is not just about syntax. It is about building something useful for other people.

Over time, I learned that good engineering is not about writing the most clever code. It is about writing code that can still be understood, changed, and trusted later.

I have worked across different stacks, mostly PHP, Laravel, JavaScript, TypeScript, and Next.js. Each project taught me something different: how to structure backend logic, design APIs, work with databases, handle integrations, and build interfaces that make sense for users.

A lot of those lessons came the hard way. Broken assumptions, unclear requirements, legacy code, late-night debugging, and systems that looked simple at first but became complex over time.

I care about maintainability because someone will always come back to the code. It might be a teammate, a client, or myself months later. I try to write code with that person in mind.

My approach is simple: understand the problem clearly, keep the architecture reasonable, avoid unnecessary complexity, and build systems that can grow without becoming painful to work with.

I also believe software is not only about the backend. A reliable system still needs a clear user flow. The best technical solution will not help much if people struggle to use it.

One project that matters a lot to me is Praesepe.id. I built it to help people learn programming in a more practical way, beyond just following tutorials.

The idea came from my own experience. Learning to code alone can be confusing. Tutorials can teach syntax, but it is harder to find someone who can review your code, explain the trade-offs, and show why a certain approach might become a problem later.

Through mentoring, code reviews, and real project work, I help developers move from simply making things work to building software with better structure, clearer decisions, and stronger engineering habits.

Praesepe.id also works as a bridge between learning and real-world practice. Client projects become learning opportunities, and mentees get to work on real problems instead of only building toy projects.

Today, as a Software Engineer, I focus on building web systems that are reliable, maintainable, and useful for real business needs. My work often involves backend architecture, APIs, databases, integrations, frontend implementation, and technical decision-making.

Outside of project work, I mentor developers and write about software engineering from a practical point of view. I am still learning, still improving, and still interested in the small details that make software better to work with over time.