3 min read

TAKE A BREAK

Side Project Ideas: 10 Small Builds You Can Finish This Month

Tech
Updated: 11/20/2026
Side Project Ideas: 10 Small Builds You Can Finish This Month
#SideProjects
Side project ideas you can finish this month: 10 small builds on Sheets, Docs, Mac and keyboards, each with scope, time estimate, and a stop point.

Why most side project ideas stall, and how to pick one that ends

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.

Three rules to set before you start

  • Define done in one sentence. 'A one-page guide, published' is done. 'A better guide someday' is not.
  • Cap the time, not just the scope. Give each build a fixed number of evenings.
  • Keep one active build at a time. Several open projects make each one harder to finish.

Does a plan actually help you finish?

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.

10 side project ideas you can finish this month

Each entry lists the scope, the time, and the stop point. The stop point matters most, because it tells you when to stop.

1. A spirits tasting log in Google Sheets

  • Scope: One sheet with columns for distillery, style, age statement, price paid, nose, palate, finish, a 'would buy again' yes or no, and a score from 1 to 10.
  • Time: One or two evenings.
  • Stop when: You have logged 15 bottles and the columns stop changing. Skip charts until you have used the log for a month.

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.

2. An Islay versus Speyside guide in Google Docs

  • Scope: A single document comparing the two Scotch whisky regions, using only bottles you have actually tasted. Use a five-row table: peat, sweetness, body, finish, and best occasion.
  • Time: One afternoon.
  • Stop when: The document fits on one page. Share it as a link with one friend and call it finished.

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.

3. A bourbon or rye pick guide

  • Scope: A decision sheet with three questions (sweeter or spicier, mixing or sipping, and budget) that point you toward a bourbon or a rye.
  • Time: Two evenings.
  • Stop when: The guide gives a clear answer for five common situations, such as a Manhattan, a neat pour, or a gift.

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.

4. A keyboard parts budget in Google Sheets

  • Scope: One sheet listing every part for a single mechanical keyboard: case, PCB, plate, switches, keycaps, stabilizers, and cable. Add columns for price, status (to buy, ordered, arrived), and a running total.
  • Time: One evening to set up, then a few minutes each time a part arrives.
  • Stop when: The keyboard is assembled and the total is recorded. Do not start a second board until the first one types the way you want.

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.

5. A keyboard maintenance log in Google Docs

  • Scope: A checklist for cleaning, lubing switches, and checking stabilizers, plus a dated entry for each service.
  • Time: About two hours.
  • Stop when: You have used the checklist once, from start to finish. Resist the urge to write a complete guide to every switch type.

6. A dotfiles repo for your Mac terminal

  • Scope: A Git repository with one shell configuration file, five aliases you use every day, and a short README.
  • Time: A weekend.
  • Stop when: You can clone the repo onto a second Mac and get your setup back in about 15 minutes. After that, stop tuning prompt colors.

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.

7. A screenshot sorter script for macOS

  • Scope: A short Python or shell script of about 30 to 50 lines that moves screenshots from your desktop into dated folders.
  • Time: One evening.
  • Stop when: It has run on your real desktop for a week without losing a file. Test on a copy of your folder first, and write any bugs in a notes file for later.

8. A weekly open-projects email with Google Apps Script

  • Scope: A Google Sheet listing your projects with a status column, plus a short Apps Script that emails you the Active ones every Monday using a time-based trigger.
  • Time: One evening.
  • Stop when: The email has arrived for two Mondays in a row. No dashboards and no login system.

This one is a project about finishing projects, which makes it a useful first build if you keep starting and stopping.

9. A static portfolio page built on a Mac

  • Scope: One HTML file with a title, three project cards, and a contact link, hosted on a free static host such as GitHub Pages.
  • Time: A weekend.
  • Stop when: The page is live and linked from your profile. Do not add a framework or a blog until you have used the page for a month.

10. A typing test page in plain JavaScript

  • Scope: One HTML file that runs a 60-second typing test, counts words per minute, and shows the result. No accounts and no leaderboard.
  • Time: One or two evenings.
  • Stop when: Three test runs produce correct scores. It is tempting to add themes and high scores, so put those ideas in a second project instead.

This build pairs well with the keyboard projects above, since it gives you a quick way to compare how a new board feels.

Quick comparison of the 10 builds

#IdeaMain toolTimeStop point
1Spirits tasting logGoogle Sheets1-2 evenings15 bottles logged
2Islay vs. Speyside guideGoogle Docs1 afternoonOne page, shared
3Bourbon or rye pick guideGoogle Docs2 eveningsFive situations covered
4Keyboard parts budgetGoogle Sheets1 evening, then updatesBoard built, total recorded
5Keyboard maintenance logGoogle DocsAbout 2 hoursChecklist used once
6Mac dotfiles repoGitA weekendNew Mac set up in 15 minutes
7Screenshot sorter scriptPython or shell on macOS1 eveningOne week on the real desktop
8Weekly open-projects emailGoogle Apps Script1 eveningTwo Monday emails received
9Static portfolio pageHTML on a MacA weekendPage live and linked
10Typing test pagePlain JavaScript1-2 eveningsThree correct test runs

How do you pick the right one?

  1. Choose the idea whose stop point you can write in one sentence.
  2. Write the scope in three bullets. Cut anything that does not serve the stop point.
  3. Block a calendar slot for each evening you will work on it.
  4. Copy the stop point to the top of your notes so you see it every session.
  5. When you reach it, share or publish the result, then close the project.

Where do you track each idea?

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.

Takeaway

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.

Frequently asked questions

How long should a side project take?

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.

Should I work on several side projects at once?

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.

How do I know when a side project is done?

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.

Are side projects worth it for getting hired?

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.

Do I really need a tracker?

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.