Articles in this category. Show all categories
The personnel information system of the City Government of South Tangerang: employees keep their own records and follow their services, administrators work on exactly their part of the organisation, and every rule comes from the regulation that sets it. Led and built by me since 2023.
The Vue browser application of a civil-service personnel system: a self-service portal where employees keep their records and propose changes, and administration of a versioned organisation chart, reference data and accounts — built from a few shared definitions, not a page per record.
Money crosses every layer of my systems: database, services, JSON, browser and printed documents. I keep one convention everywhere — amounts are integers in the currency's minor unit, as ISO 8583 carries them, named with a suffix, rounded in one place and converted only at the edges.
Salary tables, salary steps, promotion, retirement age and allowances are set by regulations that keep changing. I read the regulations themselves, store what they change as data with an effective date, and keep the arithmetic in code that cites its legal basis.
The Vue browser application of a document-signing platform: sessions held in memory and renewed by one queued refresh, PKCE sign-in, stamps placed precisely on PDF pages, identity checks with a face challenge, client consent, and role-based administration.
How I run Laravel as the core of a team-built platform: nodes that hold no state, slow work handed to queued jobs and specialised services, files kept off the server, one internal token for every login, and every request, job, and call observable.
Each endpoint is one procedure that carries a request from start to finish, with its concerns in modules beside it — Fowler's Transaction Script as I shape small one-job Python services, bundled into one binary, until their rules outgrow it.
Feature-Based Frontend Architecture is one of the architectures I use: the shape I give Vue web interfaces — one folder per feature, shared code in a few global folders by kind, data flowing one way through stores and services to one HTTP client, and my own design system pinned by version.
One folder per kind of code at a single level, a short path from route to repository, one file per operation — the shape I give a Rust service that must work fast or fit a local AI agent's context, before it grows into Clean Architecture.
The shape I give small tools: one file, one job, sections in a fixed order, an exit-code contract at the top, and three ways in for input — plus its Bash variant for generators, and when a tool outgrows it.
Get an email when a new article is published.