This is the second post in a series about designing and creating SoundFloored, an open source soundboard pedal! Check out the other posts in the series:
- Part 1 – Planning
- Part 2 – Software Implementation (you’re already here!)
- Part 3 – Breadboard Implementation (coming next Monday)
So now that I’ve prepared what I can, it’s now the step that can often derail the whole project: implementation.
For context the “Plan” section of this post was written before I started writing any code and “Implementation” was written shortly after I’d put the first version together.
I know, I know, I’ve already done the planning in the first part, “when are you actually going to start writing code“?
Well, except for tiny projects (usually single file, one-off scripts) I like to spend some time considering how the different parts will interact. The reasoning is that as soon as you start working with multiple modules and classes you’ve really got to consider how the parts will hang together, including what should “own” which parts of the logic, what the different interfaces should be and how the code should be laid out.Continue reading “SoundFloored: Open Source Soundboard Pedal (Part 2 – Software Implementation)”