01
Modernize a business-critical system
I take a platform that's become hard to change — legacy .NET, a fragile integration layer, a system nobody wants to touch — and turn it into something you can run, extend, and hand over.
.NET / Next.js
Oslo · Independent software practice
I develop, deploy, and maintain business-critical systems.
I'm David Davis Bukenya. I build .NET and Next.js systems on Azure and Supabase, and I add AI where it actually helps — with evaluation and human oversight built in. You work directly with me from start to production.
Stack — C# / .NET · Next.js · Azure · Supabase · Practice — Applied AI under EU / GDPR constraints
try
- Live in production
- 5 sites
- Products shipped
- 6
- Based in
- Oslo
- I reply within
- 48 h
What I take on
I usually help in one of four ways.
02
Ship AI with evaluation and governance
I build AI features that are scored before they ship, reviewed by a human before they act, and logged so you can explain what happened afterwards.
Evals · Human-in-the-loop
03
Build software that survives procurement
I build in what reviewers ask for — tenant isolation, real authentication, audit trails, documentation — from day one.
RLS · Entra ID
04
Own delivery end-to-end
I take a system from architecture through deployment and day-to-day operation — one person holding the whole context.
Design → Ops
Work
6 products, one under NDA. Swipe through them, or lay them all out.
1 of 6
NorskCoach
A Norwegian-language coach that finds your gaps, then talks with you. A fast model for practice, a stronger one for correctness.
DEPOT
Curated resale for vetted pre-owned fashion from independent boutiques. Buyer-protection escrow on every order, EU-wide returns.
KlubN
Event listings, artist profiles, ticketing and community for Oslo nightlife — one codebase I also operate.
DJDiP
Brand and booking site for an Oslo DJ: sound, mixes, dates and a press kit in one place.
DJ Miss Kiki
Full artist site for an Oslo DJ — bookings, mixes, gigs and the brand identity behind them.
How I work
The same four steps, whether the job takes two weeks or six months.
01
Scope in writing
We agree on what ships, what doesn't, and what "done" means — before I write code.
02
Ship in increments
You see working software at short intervals instead of one big reveal at the end.
03
Document the tradeoffs
I write down every non-obvious decision, so the next person — including you — understands why.
04
Leave it maintainable
I hand off code and docs another engineer can pick up. Nothing depends on me staying.
Idea
Have an idea? Tell me about it.
Every engagement above started the same way — someone described what they needed in plain words.
I read every idea myself and reply personally, usually within a day or two. No bots will email you.
Prefer to talk it through first? Ask my AI in the terminal up top — or use the full form with budget and timeline.