One of the things I appreciate most about being at Zone01 Kisumu is the culture of continuous learning. This week, I attended my second mini-conference, where the topic of discussion was backend frameworks.
Rather than comparing frameworks to determine which one is "the best," the speakers focused on something much more important: understanding where each framework fits.
Starting with the Fundamentals
The conference opened with an excellent presentation by Clare Gisore, who walked us through the foundations of backend development. Before discussing any framework, it's important to understand the role a backend plays in an application—handling business logic, communicating with databases, managing authentication, exposing APIs, and much more.
That foundation made the rest of the sessions much easier to follow.
Django: Rapid Development
Bramwel Mutugi introduced us to Django and demonstrated why it has become one of the most popular Python frameworks.
Some of the key takeaways included:
- Rapid development
- Built-in authentication
- Strong security features
- Excellent for database-driven applications
The session gave me a practical understanding of where Django excels and why many startups choose it.
Java Spring Boot: Enterprise-Ready Development
Haji Ibrahim and Richard Ochola showcased Java Spring Boot using examples from the Loot platform they are currently building.
Seeing a real project made the concepts much easier to understand. The presentation highlighted why Spring Boot is trusted for large-scale applications where scalability, maintainability, and performance are critical.
Ruby on Rails: Convention Over Configuration
Paul Oguda wrapped up the event by introducing Ruby on Rails.
Although I haven't built a Rails application yet, the philosophy behind it immediately caught my attention. Rails emphasizes developer productivity through conventions, allowing developers to focus more on solving problems than configuring projects.
It definitely left me curious to explore it further.
The Biggest Lesson
If there is one lesson I'll carry forward, it's this:
Frameworks are tools—not trophies.
It's easy to chase whatever framework is trending on social media or job boards, but choosing a framework should always depend on the problem you're solving.
Every framework has strengths, weaknesses, and ideal use cases.
A good developer understands why they're choosing a tool—not just which tool they're choosing.
The framework doesn't define the developer. The developer defines how effectively they use the framework.
Final Thoughts
Events like these remind me that learning software development isn't just about reading documentation or writing code alone. It's also about learning from other developers, understanding different perspectives, and seeing how people solve real-world problems.
A huge thank you to everyone at Zone01 Kisumu and LakeHub for organizing these mini-conferences. They continue to create an environment where developers can learn, share knowledge, and grow together.
I'm already looking forward to the next one.
What backend framework are you currently using, and why did you choose it? I'd love to hear your thoughts in the comments.
Top comments (0)