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 becomes a sketch. The sketch becomes a prototype. The prototype becomes a project.
Scarlco Labs is where those complaints go to become experiments.
Codex is most useful when I treat it like a capable collaborator, not a vending machine. The better I describe the project constraints, the better the results become. The more I preserve context in READMEs, checklists, and changelogs, the less likely future work is to drift. The pattern is becoming clear: ChatGPT helps shape the…
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…
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…
Scarlco Events is a generalized event information and schedule display concept. The interesting challenge is not simply putting events on a screen. The challenge is making the display reliable, readable, and appropriate for the environment where it runs. A browser on a desktop computer is forgiving. A signage endpoint may not be. That difference changes…
"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…
RecoveryCue did not begin as an abstract app idea. It began with the practical reality of recovery: reminders, notes, medication timing, vitals, exercises, and the mental load that falls on both the patient and the caregiver. That made the project feel different from the beginning. It was not about building an app category. It was…