1. Home
  2. Blog
  3. Opinions
  4. Why I build my own tools: Canopy and Sprache
Opinions

Why I build my own tools: Canopy and Sprache

I built Canopy because my agentic IDE kept missing one feature, and Sprache because a paid language app taught me too little. Why I build my own.

On this page
  1. The tool that was almost right
  2. Go, and why a side project is a good place to learn it
  3. A different reason for Sprache
  4. What this costs, and what it doesn’t mean
  5. Takeaway

TL;DR: I build my own tools when an existing one is almost right and I would spend more time shopping for a better one than building the missing part. Canopy and Sprache came from that. It is not advice to build everything.

This is for engineers who wonder if a side project is worth it.

The tool that was almost right

Before Canopy, I used an agentic IDE. It was good. I mean that. But there was always something I wished it had. It had other features I liked, and it lacked one or two I wanted. Most agentic IDEs I saw are built around a chat window. I wanted to see everything happening in one place, and move between different agents and workspaces easily.

I could have looked for another one. But that means reading what each tool offers, installing it and testing it. For me, that was already too much work. I wanted the features I wanted in one place.

So I built Canopy. It is written in Go and Next.js and runs teams of Claude Code agents as a live workspace tree.

I want to be clear. Canopy is not a new idea. There are many open-source agentic IDEs you can pick up today. I don’t think the tool I used was bad, and I don’t think the others are bad. I built Canopy to make my own workflow easier.

Go, and why a side project is a good place to learn it

I am learning Go right now. A side project is a natural place to practise it.

I also believe Go is faster than Python or Node.js, and I want a fast backend and a fast client for this kind of tool. That is my reason for choosing it. Don’t take my word for it: benchmark it yourself for your own case.

There was a second reason. I wanted to learn Go better by watching a complex application get built, and by reviewing and writing parts of it.

A different reason for Sprache

Sprache came from a different place. I am learning German.

I picked a popular language app because I had seen its ads. The ads looked good, so I signed up. I used the free version for a few chapters. The ads were a headache, but I kept going.

Then I decided I was serious and bought the premium plan. After that, I felt I was learning very little. I had seen people say the same, and I didn’t believe them at first. Then it happened to me. That is my experience, not a review of the app.

So I collected the best ways to practise and the best course libraries I could find, and asked an AI to build me an app from them. I wanted a dictionary, and new words delivered to me regularly so my vocabulary keeps growing. That app is Sprache. It teaches German and French for Nepali speakers.

What this costs, and what it doesn’t mean

I am not saying you should build everything. Building your own tool is work, and a good tool already exists for most jobs.

My rule is smaller. I build when:

  • an existing tool is close, but misses a feature or two I want,
  • finding and testing alternatives would take about as long as building the missing part, and
  • I also want to learn something from the build.

If you only want the tool to exist, use one that already does.

Takeaway

Build your own tool when the gap is small and personal, and the build teaches you something. Otherwise, use what exists.

If you are curious, try Canopy or Sprache. Tell me what is missing.