It’s more common for devs to suffer from under-design, but just as problematic.
I’m susceptible to over-design problems because I tend to document everything- I’ve written my inner monologue during this project in 
Building A Music Engine and have no intention to stop.
But I do tend to start designing myself in circles.
So today, I cut straight to the point in From Audio Chaos to Actual Music, wrapping up what I need to start coding.
And then I forced myself to start coding.
There are risks to jumping into code without having a clear idea of what you’re building.
But its just as risky to avoid code until you have “perfect clarity”.
So no fear of ambiguity from me today. Design sets the direction, code reveals the reality, and it’s my job to start stepping:
OpenSimple enough start for this song section feature. Generating a musical idea, which is a dead simple hardcoded switch for common chord progressions.
It’s far from its final form, but sufficient for its current form. And that means its perfect code.