Ady Shaputra — Software Engineer / Fullstack Developer
Building digital products that actually work.
Engineering scalable solutions, designing better experiences.
I design and build web systems end to end — enterprise data platforms, reusable application architecture, and the APIs that connect them. Frontend to database to deployment, with the details treated as part of the product.
# hierarchical asset lookup GET /api/assets?site=plant-a &system=hvac&status=active → 200 OK · 84 ms { "data": [ { "code": "AHU-01", "name": "Air Handling Unit", "health": "operational" } ], "meta": { "total": 128 } }
Selected projects
Case studies in enterprise systems, reusable architecture, and integration work — what was built, the problems inside it, and the decisions that solved them.
Note on images: all project screenshots and mockups on this page are temporary local placeholder graphics. They mark where the real, anonymized screenshots will go — no image here depicts the actual systems.
About
A fullstack developer who treats software as a system: data model first, interface second, deployment always in view.
I work across the whole stack — React and Next.js on the frontend, Node.js and Laravel on the backend, with MySQL and PostgreSQL underneath and Docker, Nginx, and Linux carrying it into production. Most of my work sits in operational software: the internal systems companies actually run on, where data is messy, hierarchies are deep, and reliability matters more than novelty.
My approach starts with the problem, not the framework. I map the data and the workflows first, design the API contract, then build the interface around real tasks — dense where operators need density, simple where they need speed. Reusable architecture is a habit, not an afterthought: boilerplates, shared components, and conventions that let the next feature ship faster than the last.
The goal is straightforward: software that stays maintainable after launch — typed, tested where it counts, documented where it matters, and honest about its trade-offs.
- a.
Model the domain first
Hierarchies, states, and relationships get designed before screens do. Most UI problems are data problems in disguise.
- b.
Contracts before code
API shapes, validation rules, and error formats are agreed up front, so frontend and backend never guess at each other.
- c.
Build once, reuse deliberately
Layouts, CRUD patterns, and form handling are extracted into shared modules — the reason a boilerplate became a project of its own.
- d.
Ship, then harden
Logging, error handling, and deployment pipelines are part of the definition of done, not a later cleanup phase.
Technical expertise
Grouped by where the work happens. Filter a category to see how the pieces fit together — no percentage bars, just the tools and where they are used.
Experience & education
The focus areas behind the projects above. Employer names and employment periods are not published on this page — the owner can supply them for the public version.
Let’s build something meaningful.
Have a system to build, an integration to untangle, or a role that needs a fullstack engineer who thinks in architecture? Start with the CV, or reach out directly.