Visit homepage

Think small

  • Planted:
  • Last watered:

I like writing and coding in my free time. The constraint is always time—not a lack of things to learn or ideas to build. The classic trope of developers buying dozens of domains and letting side projects collect dust definitely rings true for me.

I think the main reason for that is slippery scope. In other words, thinking too big. There are times for thinking big, of course (e.g. Bun), but for single-weekend side projects I am trying to think smaller these days.

And that’s not to say I don’t want to build big projects. For bigger projects, I’d like to ship a Simple, Lovable, and Complete thing first and then build toward the big thing.


I heard the concept of Simple, Lovable, and Complete (SLC) as an alternative to Minimum Viable Product (MVP) on a podcast recently. I like it—especially for side projects that aren’t really “products” but more projects meant to do something useful or just delight people (or person, singular). The best side projects are often tiny, useful things.

Others who think small

Linus Lee does this really well. To be fair, he has built many amazing big things, too, but I heard him talk on a podcast about limiting himself to one new unknown per project and scoping something to a single weekend. is the king of small, fun projects. I like Draw Logos From Memory. Lynn Fisher's work is in the same boat, like is a very useful, well designed project. It’s actually pretty feature rich, so not small necessarily, but it does one thing really well. Josh Comeau’s goodies are another example of useful single-purpose things. So is

Small, useful things are not only more likely for you/me the developer to actually ship, but they are also more likely to be used. If someone can understand something quickly, they will be more likely to give it a shot, I think. is a good example of that. You can understand it immediately, and you can play with it immediately. Copy-paste the testing URL in your address bar then update the text/color/font params, and you have a decent custom favicon. is one of my favorite examples. Not only is it very fun to play with for custom Slack emojis, but it’s awesome for favicons. I used it for the favicon on

Small mediums

Finding a medium that lends itself to thinking small is helpful. Building browser extensions is a good example. The coding bootcamp I did a couple years ago when I was learning to code had a single-night hackathon in the second week of the program, and the prompt was simply, “build a Chrome extension.” My partner and I built an accessibility extension that made all text on a website high contrast and highlighted links more clearly.

Val Town is another perfect medium for thinking small. Vals are meant to be small and composable. The email subscription Val I created for this website, for example, took about a day to ship. Val Town is also a great medium for small projects because it’s still so new and it’s social. You run into less of “I would build that, but I bet it already exists” and more of “I should build that...I bet other people would use it!”

When I’ve thought small

Yesterday I was off work, so I built a website where you can create a visualization of your life in weeks: I definitely had no shortage of stretch goals, but I scoped down enough to ship an SLC version. I can always add features when I want and patch bugs when they come up, but now a working project is out there for people to play with.

About a year before I redesigned/refactored this website in the fall to start writing consistently, I published a single blog post on I knew I wanted to write on the Internet, and I already invested too much time researching fantasy football, so I spent a weekend on an SLC fantasy football blog.

When I’ve thought too big

This essay is as much for myself—as a reminder and to set an intention—as it is for an audience, which is generally true about most things I write. As I said up top (and in my note on silly TLDs), I’ve often fallen into the trap of buying domain names on a whim and leaving projects unfinished.


The first real website I wanted to build when I started coding a few years ago, before I got my first software engineering job, was non-prophet. The static version of the site is still up, but I didn’t get around to finishing the part that actually matters: accepting money in return for clothing. It’s not surprising in retrospect that I didn’t complete that given the scope I chose and the many new things I was learning on the fly, including the act of scoping itself. I was learning React (and still JS, HTML, CSS), responsive design, deployment, etc. And I spent time on shiny engineering things like Storybook and Cypress that felt like prudent decisions but probably just added unnecessary overhead.

I still want to revisit and finish non-prophet for a few reasons. It was my first website that I got really excited about, so there’s some nostalgia there. Plus, building an e-commerce site is somewhat of a seminal web dev experience (along with a blog). I also find the design task of making physical clothes and creating a brand interesting. And lastly—perhaps most importantly—I want to follow through on my original intent to bring in donations to EJI.

When I do dust it off, I’ll change my approach to start by shipping an SLC version: a single page (literally—not SPA) that sells a single piece of clothing. There’s still plenty to do for that—I need to integrate payments, e.g. Stripe, and drop shipping, e.g. Printful—but I can throw out anything that isn’t core, like an email signup list and multiple products.

Only the platform

More recently, this past summer, I started building a website using only the platform, i.e. just HTML, CSS, and JavaScript without any external libraries. My goal for v1 was a nice looking website with demos for at least 10 interesting browser APIs, then add more over time. In retrospect, 10 was way too many. Some of the APIs—like service workers—have enough depth for weeks of interesting exploration. I should have aimed to ship just one browser API demo to start.

That’s not to say I can’t still do that, or that the time I spent experimenting wasn’t valuable. I think View Transitions and Service Workers are both very cool, and I am pretty confident I’ll return to those in the next year or two. But by overscoping, I left several features half baked and am less likely to pick that project up on the odd weekend.

It works, it’s fast, and it looks good

Along the lines of simplifying things, I heard Jerome Hardaway say something when I was first learning to code that stuck with me. He said (to paraphrase), people only really care if your website works, is fast, and looks good. In that order, too. It’s easy to get caught up in other stuff as a developer, especially for side projects in your free time where there might not be financial incentives, but people will be happy (or not unhappy) if it works, is fast, and looks good.



Respond with your thoughts, feedback, corrections, or anything else you’d like to share. Leave your email if you’d like a reply. Thanks for reading.