A program built on questions
Why do some coding habits create confusion while others bring clarity? Our mission is to challenge every assumption about clean code, logic, and databases—together, one question at a time.
Contact usOur core principles
If you’re wondering how to write code that feels effortless to read, you’re not alone. We focus on the idea that every developer is both a learner and a teacher. Could the next naming decision help someone else solve a problem faster? That’s the philosophy driving every session—always curious, never complacent.
Is perfect code possible? We doubt it. But striving for clarity means fewer headaches and better teamwork, even if the journey is full of corrections.
Database design isn’t just about structure—it’s about understanding what data will actually be useful later. Sometimes that only becomes clear after you’ve built the first version.
We ask: How can logic be more obvious to someone reading your code a year from now? The answer changes as projects and teams change.
Documentation gets overlooked. Yet, those little comments often save hours later. How much documentation is too much? We’re still testing that.
Clarity first
Every step starts with clear intentions, even when the outcome is messy. We value transparent code that invites collaboration.
Feedback loops
Real improvement comes from honest, ongoing feedback. We believe that admitting confusion is a strength, not a weakness.
Learning never ends
There’s always a new way to solve a challenge. Each project opens the door to fresh ideas and experiments.
Meet our team
Lebo Sithole
Lead Instructor
With a background in software design and a passion for collaborative
problem-solving, Lebo helps teams see that every code review is a chance to learn.
She encourages students to share their questions openly.
David Venter
Application ArchitectDavid’s experience spans enterprise and startup projects across South Africa. He believes the best logic comes from groups willing to debate and rework code together. His specialty: making data models less intimidating.
How we got here
Always evolving, always curious
-
First sessions launch
It started with a handful of local developers debating naming habits.
-
Expanded feedback loops
We added weekly peer reviews and noticed more honest, productive conversations.
-
Database focus grows
Application logic was key, but our community wanted more database structure discussions.