TAKE A BREAK

Most side project ideas die for the same reason: they have no end. A project starts with energy, then drifts into a folder nobody opens. The fix is not a better idea. It is a smaller one with a finish line. Below are 10 side project ideas that take a weekend to about a month. Each one has a defined scope, a time estimate, and a stop point, the moment you ship and stop adding features.
We wrote this list at 3minread for readers who have more half-finished projects than shipped ones. Most ideas use tools you probably already own: Google Sheets, Google Docs, a Mac, a mechanical keyboard, and a bottle or two of whisky for the tasting projects.
There is evidence behind the if-then habit. In a 2006 meta-analysis of 94 independent tests, Peter Gollwitzer and Paschal Sheeran found that implementation intentions, which are if-then plans that name the next action in advance, had a medium-to-large positive effect on goal attainment (d = .65). In practice, 'When I finish dinner, I log one bottle in the sheet' works better than 'I'll work on my tasting log soon.' The Gollwitzer and Sheeran meta-analysis is the study behind that idea.
The pull to return to unfinished work is real, but the popular story is overstated. A 2025 meta-analysis in Humanities and Social Sciences Communications found no memory advantage for unfinished tasks. It did find a general tendency to resume interrupted work. That is the useful part. A half-built project keeps asking for attention, so a clear stop point lets you answer that pull on purpose instead of with guilt.
Each entry lists the scope, the time, and the stop point. The stop point matters most, because it tells you when to stop.
Define what the scores mean before you start. A 7 might mean you would pour it again for a friend. Without that rule, your numbers will drift and stop being comparable.
Islay is widely known for smoky, peated whiskies, while Speyside is often described as lighter and fruitier. Treat those descriptions as starting points, and let your own tasting notes do the rest. A guide built on your notes is more useful than a generic one, and it is short enough to finish.
The difference is worth stating in your guide. By US rules, bourbon must be at least 51% corn, and rye whiskey must be at least 51% rye. Rye tends to read drier and spicier, while bourbon often reads sweeter. Keep the guide focused on those criteria instead of brand rankings, and it will stay useful longer.
The status column is the part that pays off. It stops the common problem of buying the same part twice because you forgot what was already on the way.
This is a good fit for coding on a Mac because the payoff is immediate. Each alias you actually use saves a few keystrokes every day, and the project has a clear, testable finish.
This one is a project about finishing projects, which makes it a useful first build if you keep starting and stopping.
This build pairs well with the keyboard projects above, since it gives you a quick way to compare how a new board feels.
| # | Idea | Main tool | Time | Stop point |
|---|---|---|---|---|
| 1 | Spirits tasting log | Google Sheets | 1-2 evenings | 15 bottles logged |
| 2 | Islay vs. Speyside guide | Google Docs | 1 afternoon | One page, shared |
| 3 | Bourbon or rye pick guide | Google Docs | 2 evenings | Five situations covered |
| 4 | Keyboard parts budget | Google Sheets | 1 evening, then updates | Board built, total recorded |
| 5 | Keyboard maintenance log | Google Docs | About 2 hours | Checklist used once |
| 6 | Mac dotfiles repo | Git | A weekend | New Mac set up in 15 minutes |
| 7 | Screenshot sorter script | Python or shell on macOS | 1 evening | One week on the real desktop |
| 8 | Weekly open-projects email | Google Apps Script | 1 evening | Two Monday emails received |
| 9 | Static portfolio page | HTML on a Mac | A weekend | Page live and linked |
| 10 | Typing test page | Plain JavaScript | 1-2 evenings | Three correct test runs |
A tracker can help, but it carries a risk. It can become one more place to avoid finishing. Keep it to a single list and update it once a week.
If you want one place for this, try continuu.it, a project tool built for people who start more than they finish. Every project has a state: Active, Paused, Killed, or Completed, so unfinished work does not sit in limbo pretending it is still alive. Tasks live inside each project, so when you come back after three weeks you can see where you stopped. Notes keep the context you would otherwise have to rebuild, and ideas can be parked without becoming projects yet. Analytics show how much you start compared with how much you finish, and killed projects go to a Graveyard, because stopping a project on purpose is also a form of finishing. It is not a replacement for Notion as a docs or wiki tool, but it fits the job of tracking side projects. A free plan is available.
Pick one build from the list, write its stop point in a single sentence, and block two evenings this week. Ship it, share it, and then close it. A small finished project teaches you more than a large unfinished one, and it makes the next idea easier to start.
For a small build, a weekend to one month is a sensible target. If a project runs past that, our rule of thumb is to cut scope rather than extend the deadline.
Usually not. Several open projects split your attention, so keep one active build and mark the others as Paused with a short note about where you stopped.
It is done when it meets the stop point you wrote before you started. Any extra feature after that is a new project with its own scope.
In our view, a small finished project with a live link or a clear result says more than an ambitious project that is still half-built. Choose the build that shows a finished result you can point to.
Not always. A single sheet or document works for one or two projects. Once you have more than that, a tracker with clear states helps you see which projects are active and which are waiting.