Work
Each one is the problem, the constraint, the wrong turn I took first, the decision, and what happened. The wrong turns are the part that is hard to fake.
No client architecture appears anywhere on this site. Every study is written at the level of the problem and the decision, which is also the level that transfers to a different company with a different stack.
I am the only engineer on Enaton, a school management platform used daily by 112 schools across Kenya. I designed it, I ship it, I operate it, and I am the one who gets called when it breaks.
A user could ask two parts of the same system the same question in one afternoon and get two different answers. Both were defensible. That is the worst kind of bug, because nobody can tell you which one to trust.
The cron entries had multiplied to the point where nobody could say what ran overnight, whether it had finished, or what would happen if the process died in the middle of it. That is the moment a scheduler stops being a convenience.
The office had a queue every morning. Every extra click on the screen the clerk used was not a usability detail, it was another person waiting in a corridor.
The brief was a website. The actual requirement, which nobody said out loud, was that the owner could add a car at nine at night from a phone without calling me.
Building the same shape of product twice is the cheapest education available. The second one tells you which of your decisions were real and which were habits you had not noticed.
An internet provider site is not really a marketing site. It is a single question with some marketing attached, and the question is whether the service reaches the visitor's building.
Most portfolios quietly delete the early work. Mine keeps it, because how somebody got from a salon booking page to running a platform is more useful information than the platform on its own.
For the reasoning behind how any of this gets built rather than what got built, read how I work .