THE BEGINNING
I discovered something that would become a big part of my career.
- 01How applications are structured
- 02How teams work
- 03How requirements become software
- 04How .NET is used in a real application
I learned how to write code.
The first thing I shipped that other people used.
IFBT People Dashboard

- 01Server-rendered MVC over SPA — the team needed reliability, not interactivity.
- 02Normalized schema so reports stayed correct as data grew.
- 03Reused layout components so new report pages took hours, not days.
- ASP.NET MVC
- C#
- .NET
- SQL Server
GOING DEEPER
I wanted to understand .NET beyond building applications.
Different systems. One language between them.
Mapping Library

- 01Declarative mapping definitions instead of hand-written conversion code per app.
- 02Fail loudly on unmapped required fields rather than writing partial data.
- 03Version the mappings so an app change never silently breaks another integration.
- .NET
- C#
- REST API
- SQL
STUDY
While interning and working part-time, I was also finishing my degree.
The same year I was learning how software breaks, I was completing the formal path that started it all.
THE UNEXPECTED
I thought I would spend most of my time building.
But my role took another turn.
- UNIT TEST
- MANUAL QA
- TEST CASES
- KATALON
I learned how software breaks.
A NEW CHAPTER
In December 2023, I joined Impetus Fintech — the technology arm of Synergy Financial Advisers — as a Software Engineer.
Building with a different perspective.
Legacy Module Migration

- 01Incremental migration over big-bang rewrite — the business could not afford downtime.
- 02API-first design so the new modules could serve multiple frontends and future integrations.
- 03Behavior parity verified module by module before any cutover.
- .NET 8
- C#
- ASP.NET Core
- REST API
- SQL Server
Performance Reporting & Reliability

- 01Profile first, tune second — optimizations driven by measured bottlenecks, not guesses.
- 02Sentry-driven debugging: every production error traced from log to root cause to fix.
- 03Full module ownership: errors, fixes and future updates are my responsibility.
- .NET
- C#
- SQL Server
- Sentry
- Performance Tuning
Singpass FAPI 2.0 Migration

- 01Full ownership of the migration — from spec reading to production verification.
- 02Security-first implementation: every change validated against the FAPI 2.0 profile, not just made to work.
- 03Regression-tested every dependent flow so users never noticed the cutover.
- .NET
- C#
- Singpass
- Myinfo
- FAPI 2.0
- OAuth
THE NEXT CHAPTER
THE IDEA DIDN'T START WITH AI.
It started with a problem.
What should we cook today?
What ingredients do we already have?
How can we prepare meals efficiently for the family?
How can we adapt meal preparation for children starting MPASI?
AI-assisted meal preparation for families — and for the MPASI stage.
- CHICKEN
- CARROT
- POTATO
- RICE
- Chicken & carrot porridgeMPASI 8m+ · 20 min
- Potato chicken stewFamily portion · 35 min
- Steamed rice + brothShared base · 15 min
One pan. A family meal and a baby's first meal, decided in seconds.
satuwajan.id

- 01AI as a planning tool, not a chat gimmick.
- 02One pan, two outputs — family portion and baby portion from the same base.
- 03Extensible architecture so a real model API can be plugged in later.
- React
- TypeScript
- AI
I learned how to write code.
I learned how software breaks.
I learned how to build software.
Now I'm learning how to take end-to-end ownership of products.
Focused on building reliable .NET backends, production-grade REST APIs, and full-stack web applications. Open for full-time and high-impact engineering roles.
Every chapter changed how I build.