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.
Every project eventually needs a checklist. Not a ceremonial checklist. A practical one. For AI-assisted builds, mine keeps getting longer: Does the app still build? Does the install path still work? Did the ZIP structure stay flat? Did settings survive an update? Did the known compatibility fix remain intact? Did the README match the current…
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…
Writing about technical work requires boundaries. The most interesting stories are often close to real systems, real people, and real organizations. That does not mean every detail belongs on a public website. For this site, the goal is to write about lessons, patterns, and ideas without exposing private workflows, current-employer details, client information, or anything…
A project without notes becomes harder to trust over time. This is especially true with AI-assisted development. The code can change quickly, but the reasoning behind the code can disappear just as quickly. A build log helps preserve intent. It answers: Why did this feature exist? What problem was it solving? What broke last time?…
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…
For a long time, Git felt like something software developers used because they had to. Then I started building enough projects that the need became obvious. When AI is helping write code, the pace changes. Files move quickly. Features appear quickly. Mistakes also appear quickly. Version control turns that chaos into a history. It gives…