SPK PKH

Selecting social assistance recipients often relies on undocumented judgement: a meeting, a verbal agreement, then a name list. That is hard to defend when residents object. What is needed is not an app smarter than humans, but a tool that keeps criteria, weights, and calculation open.

I led a team of three and worked across the whole application. My main role was not maximum code output but ensuring criteria came from the requirement, formulas were implemented correctly, and results could be explained to non-technical people.

Work split three ways: data and criteria, calculation engine, then interface. Data came first because a wrong criteria structure propagates everywhere. Each stage had its own check — cases with known answers, and manual arithmetic.

With three people the main obstacle is dependency, not communication. I defined the data contract between parts first — the input and output of each — so work could run in parallel.

Progress meant passing test cases, not a finished-looking screen. Each part had to prove its output was correct before counting as done — slower visually, but it prevented building an interface on wrong calculations.