The origin story

Built by a programmer learning guitar — not a guitarist explaining it

TL;DR: Every other guitar tool is made by a guitarist, musician, or teacher trying to put information out there simply. Decage was built by a developer with 20 years building web and mobile apps who picked up the guitar two years ago — and saw the fretboard the way an engineer sees anything confusing: a system waiting to be mapped. That's not a marketing angle. It's why the tool is shaped the way it is.

Musicians explain the fretboard. Engineers map it.

When a guitar teacher hits the fretboard, they reach for the tools they know: lessons, videos, diagrams, repetition. The result is the entire market — 100+ courses, 100,000+ videos, 5,000+ books, all explaining the neck a slice at a time.

When a programmer hits the fretboard, the instinct is different. You don't memorise a system — you model it. You find the repeating structure, render it, and make it interactive so you can poke at it until it's obvious. That's exactly how Decage was built.

It doesn't — it just hadn't been drawn as a system yet. The fretboard is organised around five repeating chord shapes (the CAGED system), root notes, and intervals. An engineer's first move is to make that structure visible and clickable, instead of describing it in a lesson.

The tool was built from real questions, not a curriculum

Decage didn't start as a course outline. It started as a developer's own stack of stuck-points — the exact questions a logical, non-musical brain asks when the neck won't make sense:

Each one became a thing you can see and click, not a paragraph to read. That's the difference between a tool built by a learner and content built for one.

Why this beats "explained simply"

Plenty of teachers explain CAGED clearly. But explanation still leaves you translating words into fingers. A system you can manipulate skips the translation: pick a chord, watch every position appear across all 12 frets, move it, and the pattern installs itself. Software does what a paragraph can't — it responds.