Hello,I'm Odhiambo Atieno.
I am a software engineer, AI builder, and infrastructure specialist. I build and maintain production systems — from servers and networks to AI models and distributed applications — and I write about the parts that are hard to learn from documentation: how to shape a system, how to model data, how to keep a large codebase changeable, and how to ship without fear.
This site is not tied to one language or framework. Engineering is the subject; the stack is whatever the problem needs. Examples here span backend and frontend work, databases, AI systems, servers, infrastructure, DevOps and the human side of building software in teams.
What I write about
System design
Service boundaries, consistency trade-offs, queues, caching and the failure modes that show up long before a rewrite is justified.
Backend engineering
APIs that are pleasant to consume, data models that age well, and background work that does not lose your customers' money.
Data and databases
Relational modelling, indexing and query plans, migrations that ship safely, and analytics that people actually trust.
Frontend architecture
State ownership, routing, data loading and the boundaries that keep a large interface from turning into a knot.
AI & machine learning
Building, deploying, and reasoning about AI systems in production — from model selection and prompt engineering to inference infrastructure and guardrails.
Infrastructure & servers
Networks, compute, containers, observability, and the plumbing that keeps systems alive — from a single VPS to distributed clusters.
DevOps & delivery
Small changes, fast rollback, useful observability, and pipelines that a team can debug without a specialist.
Engineering craft
Code review, testing strategy, documentation and the habits that separate a codebase people enjoy from one they endure.
How I think about the work
- Explain the why, not just the how — reasoning transfers, recipes do not.
- Prefer boring, well-understood tools until the problem genuinely demands otherwise.
- Language and framework choices are implementation details; engineering judgement is not.
- Write for the engineer who inherits the system, including your future self.
Articles published
Courses in the library
Topics covered
Get in touch
I read everything, and I answer most things. Corrections to articles are especially welcome — this site is meant to be right, not just published.