Learning in Public Without Performing

There is a difference between documenting a journey and performing expertise.

I am trying to stay on the useful side of that line.

This site is not here to pretend every build is brilliant or every idea becomes a product. Some experiments will stall. Some will be rebuilt. Some will turn out to be less useful than expected.

That is fine.

The value is in capturing the process honestly enough that the next version benefits from the previous attempt.

Similar Posts

  • The Long Way Into Software

    Some people enter software through school. Some through startups. Some through computer science programs. My path wandered through technical theatre, live entertainment, production systems, operational troubleshooting, and a long habit of asking why a workflow had to be so painful. That background changes how I think about software. I am less interested in elegance for…

  • Designing Tools for Operators

    Operators do not use tools the way designers imagine users use tools. Operators are often busy, interrupted, watching multiple systems, and trying to prevent a small issue from becoming a large one. That changes the design priorities. Status must be obvious. Errors must be plain. Controls must be predictable. Dangerous actions should be hard to…

  • Tools I Wish Existed

    A surprising number of projects begin as complaints. Not angry complaints. Just quiet, repeated observations: "Why can't I see all of this at once?" "Why is this schedule so hard to display?" "Why can't I go back and verify what was on that stream?" "Why is this configuration trapped in one machine?" Eventually the complaint…

  • The Story Behind Scarlco

    "Scarl" came before Scarlco. In production environments, names get shortened quickly. There may be multiple Steves on headset, multiple people with similar names on a schedule, and not much patience for ambiguity when a cue is coming up. My name often appeared as S. Carl. Over time, that became Scarl. Later, when I wanted a…

  • Why I Like Small Utilities

    Small utilities are underrated. Not every idea needs to become a platform. Some tools only need to do one job well enough that a recurring annoyance disappears. A tiny recorder. A simple cue sender. A configuration exporter. A status page. A converter. A monitor. These may not sound glamorous, but they are often the tools…

  • Notes From the Workshop

    The workshop metaphor fits because most of these projects are in motion. Some are polished enough to share. Some are half-built. Some are sketches. Some are reminders to revisit an idea when the timing is better. That is how real making works. A website can make everything look more finished than it is. I would…