Back to Blog

Why I Build: The Philosophy Behind CodeMaaman

Exploring the motivation and philosophy that drives the projects at CodeMaaman - from solving personal problems to creating tools that matter.

March 1, 2024
2 min read
Aaron M Sabu
philosophybuildingproductivity

The Question I Get Asked Most

"Why do you build so many things?"

Its a fair question. In a world where theres an app for everything, why spend time creating new tools? The answer comes down to three things: learning, solving, and sharing.

Learning by Doing

Theres a difference between knowing about technology and knowing how to use it. Reading about machine learning is one thing. Building an AI that actually processes documents is another entirely.

Every project teaches something that tutorials cant:

  • How to handle edge cases
  • What happens when things break at 2 AM
  • The gap between "working" and "working well"

The best education is building something real and shipping it.

Solving Real Problems

The projects I enjoy most start with frustration. Something in my daily workflow is annoying or inefficient, and I think "there has to be a better way."

Sometimes theres an existing tool. Often theres not - or the existing tools are:

  • Too complex for the simple problem
  • Too expensive for personal use
  • Missing one crucial feature

Thats when building becomes worthwhile.

The Compound Effect

Each project builds on the last. Skills transfer:

  • Building a CLI tool teaches argument parsing
  • That knowledge helps when building a web API
  • API experience feeds into the next project

Over time, new projects become faster to build because so much is already understood.

Not Everything Ships

Heres what I dont often share: many projects never see the light of day. Some are abandoned halfway through. Others work but arent useful enough to maintain.

Thats fine. The learning still happens. The failed experiments inform the successful ones.

The CodeMaaman Philosophy

This is what CodeMaaman represents:

  1. Build to learn - Every project is an education
  2. Solve real problems - Scratch your own itch
  3. Keep it simple - Complexity is the enemy
  4. Share what works - Others might benefit too

What Are You Building?

If youve been thinking about building something - a tool, an app, an automation - I encourage you to start. It doesnt need to be perfect. It doesnt need to be original.

It just needs to be yours.