About Me

Full-stack developer passionate about clean code, scalable systems, and continuous learning.

My Story

I'm a full-stack developer based in Kenya, building real systems that ship. I focus on the full lifecycle: from auth flows and data modeling to DNS troubleshooting and deployment pipelines.

My work spans product dashboards, REST APIs, and infrastructure setup. I'm comfortable debugging the "messy middle"—certificate issues, broken builds, caching problems, and the kind of production fires that require both code and ops thinking.

I've shipped systems with custom domains, email workflows, role-based access, and proper service boundaries. I care about boundaries, caching strategies, auth flows, observability basics, and practical tradeoffs—not just "clean code" in isolation.

I write for maintenance, prefer simple architectures that scale with usage, and believe performance is a feature you design for, not optimize after.

Profile Highlights

  • ✓Active since July 2022
  • ✓24+ projects completed
  • ✓10+ programming languages
  • ✓Full stack capabilities
  • ✓Functional programming experience
Download CV

Experience

Full Stack Developer

Rynode Solutions

2022 - Present

Building production-ready applications and experimenting with emerging technologies.

  • ›Developed 24+ projects across multiple tech stacks
  • ›Expertise in TypeScript, React, and backend technologies
  • ›Explored functional programming (Haskell, Rust)

Hard Lessons

If boundaries aren't clear, bugs multiply—especially around auth and data ownership.

Shipping in slices beats big rewrites. A working v1 is better than a perfect plan.

Caching solves performance, but it creates debugging problems—make it explicit.

Most "frontend issues" are actually data contract issues.

Good UX is mostly removing friction, not adding features.

Principles

Prefer simple architectures that scale with usage, not assumptions.

Secure by default: least privilege, no shared credentials, clear ownership.

Performance is a feature: cache intentionally, measure, avoid N+1 calls.

Write for maintenance: predictable structure, consistent naming, clear data flow.

Toolbox

Primary

TypeScriptReactNext.jsNode.jsGoTailwind CSS

Secondary

Express.jsREST APIsPostgreSQLGitDockerLinux

Supporting

Vue.jsRustHaskellPythonJavaWordPress

Education & Learning

Self-Taught Developer

Full Stack Web Development & Systems Programming

2022 - Present

  • ›Completed 24+ projects covering frontend, backend, and systems programming
  • ›Active exploration of functional programming paradigms
  • ›Continuous learning through experimentation and open-source contribution

Interested in working together?

I'm always open to discussing new projects, creative ideas, or opportunities.

Get In Touch