I'm Rabboni Kabongo, a full-stack developer passionate about building scalable systems and exploring the fascinating intersections of electronics, mathematics, and physics. Currently pursuing Electrical and Electronic Engineering while teaching myself the art of backend architecture—because apparently, sleeping is optional when you're debugging distributed systems at 3 AM.

I believe the best engineers are eternal students. Every bug is a lesson, every refactor is growth, and every "it works on my machine" is an opportunity for humility.

I'm working on a platform focused on:

• Real-world backend education — Because tutorials that end at "Hello World" help nobody
• Training industry-ready engineers — Bridging the gap between academic knowledge and production code
• Self-hosted solutions — Teaching digital self-reliance in an increasingly centralized world
• AI safety awareness — Because with great computational power comes great responsibility

Goal: Make backend development less intimidating and more accessible. Also, to finally understand why my Docker containers work perfectly until demo day.

Skills I'm actively using and continuously improving—because technology waits for no one

2024 - 2028

• Relevant Coursework: Fundamentals of Electric Circuits, Calculus, Database Management
• Current Learning Focus: Bridging the gap between electrical engineering principles and software systems
• Side Quest: Figuring out if I can apply Kirchhoff's laws to microservices architecture (spoiler: sort of)

Because technology moves faster than my git commits

• Exploring distributed systems patterns and their inevitable failure modes
• Deep-diving into database optimization (because JOIN queries can always be faster)
• Learning why "eventually consistent" means "consistently confusing"
• Studying the ancient art of writing documentation that people actually read

Currently building projects that solve real problems, not just look good in portfolios

I'm working on several initiatives focused on backend architecture and developer education. Check back soon for detailed case studies, or feel free to explore my repositories where I document my learning journey—bugs, refactors, and all.

Philosophy: I'd rather ship working code with known limitations than perfect vaporware. Every project here is a snapshot of what I knew at the time, not what I wish I knew.

"There are two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." — Anonymous (and accurate)

Currently pondering: If a microservice fails in production and nobody's monitoring it, does it make a sound? (Yes, it makes the sound of a 3 AM Slack notification)

I'm always interested in connecting with fellow developers, learning from experienced engineers, and discussing backend architecture, distributed systems, or why tabs vs. spaces still matters in 2026.