A year of small tools

For most of last year I built small tools instead of big ones. A script that renames photos by the day they were taken. A page that tells me when the next bus actually leaves. A form that fills itself in from a spreadsheet.

None of them took more than a weekend. All of them are still running.

Why small

A small tool has one job, so you can tell at a glance whether it's doing it. When it breaks, the fix fits in your head. When it stops being useful, you delete it without a meeting.

Big tools ask you to adapt to them. Small tools adapt to you, because you made them for exactly one person.

What I'd keep

  • Write the README before the code. If the README is long, the tool is too big.
  • Put it where you'll see it: a bookmark, a home screen, a shortcut.
  • Let it be ugly at first. Polish what you actually use.