Hi, I'm Kwaku Ampem Affram, a security-focused software engineer

Backend systems in Kotlin and Spring Boot, web portals in Nuxt, mobile apps in Expo, and the CI pipeline and hosting that run them. Usually all of it for one product, because the seams between those parts are where projects go wrong.

A conversation first, with no forms and no discovery fee. Then a written scope with the first milestone fixed: what ships, by when, for how much. You get the repository on day one, every change lands through a reviewed merge request with tests, and you see a running version every week rather than a slide. At the end it is deployed on infrastructure you own, with monitoring, backups and a runbook.

Yes. It starts with reading the repository in full and writing down what is actually there, which is often different from what the last document says. You get that assessment whether or not we go on to work together.

Send a message describing what you are building and who it is for. You will get a reply within two working days saying whether this is the right place for it, and what the next step would be.