[template]
This writeup is a placeholder. Soopy is a side project and the details here are invented while I write up the real story. Most projects start with a small annoyance that will not go away, and Soopy was no different.
The one-liner
Soopy is a small tool that takes something you give it and turns it into something more useful. It helps you do a common job without the usual fuss.
If that sounds vague, the sharper version is that it produces a concrete result you would otherwise assemble by hand.
The problem
Today, doing the thing Soopy handles means:
- A clunky workaround that mostly works
- Steps that get tedious the tenth time
- Time lost that you never really notice going
None of these are hard alone. Stacked together they add up to a real drag.
Who it’s for
| Audience | What they get out of Soopy |
|---|---|
| People doing this task often | The main time saving |
| Occasional users | A quicker path than doing it by hand |
The sweet spot is someone who hits this job regularly enough to feel the friction.
What it actually does
You give Soopy an input, and it hands back a finished result. A quick mental model:
input the user provides
|
Soopy (the core step that does the work)
|
output the user getsThat is the whole loop. Everything else supports it.
Why now
Building this got easier and cheaper than it used to be, which is part of why I finally did. Existing options either do too much or stop short of the part I cared about.
Where it’s going
Right now Soopy is an early project. Near term I want to make it steadier. Longer term the bet is that the core loop is useful to more than just me.