T. Kaczocha
RSS
Menu

Drawing set TK-2026 / Sheet 1 of 6 / Rev 22 / Issued for construction

Hey, I'm Tom Kaczocha

Software engineer, Brisbane. Eighteen years in. I ship a lot, kill things fast, and keep the receipts.

I build software,
run a lawn business,
and write about both.

  1. 1
    Currently buildingExpertDrip

    Course platform for first-time founders trying to get to their first 100 customers.

  2. 2
    Real mowers, real customersVista Lawn Care

    Lawn mowing business operating on Brisbane's Southside.

  3. 3
    Start here, 8 minSeven days, 194 tasks, one daemon

    What an autonomous task loop shipped when I stopped supervising it — and why I still went back to the terminal.

Tom Kaczocha
Fig. 0 · T. KaczochaScale 1:1 · Brisbane, AEST
Drawing no.
TK-2026
Sheet
1 of 6
Drawn by
T. Kaczocha
Checked by
Production
Scale
1:1
Location
Brisbane
Latest rev
2026-05-16
Status
Building

General notes

  1. New here? Start with Vibe Coding Without Guardrails is a Disaster (5 min). A do-work manifesto.
  2. Then read Seven days, 194 tasks, one daemon (8 min). What an autonomous task loop shipped when I stopped supervising it — and why I still went back to the terminal.
  3. Then read The Mental Architecture of Physical Transformation (5 min). Preface - What this book will not do for you.
  4. Then skim the revision history below. The one-liners live there. Pull one at random if you are in a hurry.
  5. Note that every number on this sheet is a receipt, not an estimate. Two of the six parts are on ice. That is what keeping receipts looks like.

Status / currently building

ExpertDrip

Course platform for first-time founders trying to get to their first 100 customers. Built around behavioural modelling of founders who've already done it — delivered as audio, not another video course you won't finish.

Stamp
Active
Focus
Primary
Format
Audio-first
expertdrip.com

Sheet 2 / Writing

Details

7 details on file. Long-form, with receipts. See the full set →
Detail A
Scale 2:1
Featured

/ 8 min read / #do-work #programming

Seven days, 194 tasks, one daemon

What an autonomous task loop shipped when I stopped supervising it — and why I still went back to the terminal.

Read detail A
Receipts, to scale (log)
7 days
47 briefs
194 tasks, one commit each
573 hermetic tests
12,500 lines of C

One 263 KB static binary.

Detail B

Why Meso Tracks Two Streams, Not Streaks

Why I'm rejecting both streaks and single rolling percentages for Meso's adherence tracking, in favour of a two-stream model (diet scoped to phases, training scoped to mesocycles) that matches how serious training programs are actually structured.

2026-05-19 · 5 min read
Detail C

Vibe Coding Without Guardrails is a Disaster

A do-work manifesto

2026-04-15 · 5 min read
Detail D

Chapter 1 - Why willpower-based transformation fails, and what ten people installed instead

Chapter 1 - Why willpower-based transformation fails, and what ten people installed instead

2026-04-15 · 7 min read
Detail E

The Mental Architecture of Physical Transformation

Preface - What this book will not do for you

2026-04-15 · 5 min read

Sheet 3 / Log

Revision history

22 revisions on record. A microblog with anchor permalinks and no per-entry pages. Full history →
Rev
Date
Description
By
22
do-work parallel mode landed. /do-work run is now safe to launch from multiple terminals. Each orchestrator picks a different REQ via atomic git mv; ownership stamps identity in-flight slots; conflict-on-commit waits up to 110 seconds with backoff, then exits with concurrent-conflict.
TK
21
Spent the evening teaching a button to do its job. It had been pretending for months. Click, navigate, return to the same page - a perfect impression of working software. Today the button got honest and started actually duplicating jobs.
TK
20
Today I learned 15 of our customers share the same phone number: 'Notprovided'. Spaces removed, stored as data, returned in queries, ignored when real numbers later arrived. A perfect little ghost of a default value, haunting the contact table.
TK
19
Briefs say what. Clarifications say why. The first 'fix' is rarely the right one - it's the user's first guess at how to ask for what they actually want. Listen for the gap between the words and the goal.
TK
18
Names carry weight. 'Mesocycle' promises a coherent plan across weeks - same exercises, rising sets, a deload at the end. If the code re-randomises exercises each week, it isn't a mesocycle; it's a slot machine with a calendar. Either rename the thing, or fix the code to match the name.
TK
17
The post TOC was always there. Today is the first day anyone will actually see it. Same links. Same slugs. One word and a card were all that stood between nav and noise.
TK
16
Two code paths that render "the same thing" are a deadline waiting to surface. WYSIWYG is only worth building if the "what you see" is generated by the same function as the "what you get". Anything less is rehearsal in a different theatre.
TK
15
You don't need a scheduling feature. You need one query scope. 'Schedule a post' is just 'hide it until pub_date.' That's a two-line scope, not a subsystem. Most roadmap items shrink this way if you read them honestly.
TK
All 22 revisionsEight shown, newest first.

Sheet 4 / Projects

Parts list

Exploded view. Six parts, two on ice. Assembly notes →
6REPLYMATE5YARDPILOT4VISTA LAWN CARE3DO-WORK2TOMKACZOCHA.COM1EXPERTDRIP
Fig. 1 · Exploded assemblyNot to scale
Item
Part
Description
Status
1
ExpertDripexpertdrip.com · primary focus
Course platform for first-time founders trying to get to their first 100 customers. Built around behavioural modelling of founders who've already done it — delivered as audio, not another video course you won't finish.
Active
2
tomkaczocha.comtomkaczocha.com
This site. Personal blog and digital garden, built with Laravel + Vue. My corner of the internet for long-form writing, quick logs, and project updates.
Active
3
do-workgithub.com/rawphp/do-work · open source
A Claude Code framework with a two-command interface, UR-to-REQ decomposition, TDD enforcement, and a build-in-public log. Built it because the frameworks I tried were too slow for how I actually work.
Active
4
Vista Lawn Carevistalawncare.com.au · offline
Lawn mowing business operating on Brisbane's Southside. Real mowers, real customers. The reason I understand service businesses from the inside, not just the SaaS pitch deck.
Offline business
5
YardPilotyardpilot.io
SaaS for lawn care operators. Built it partly to run Vista, partly as a product. Still use it myself; not actively selling it. Might come back to it, might not.
On ice
6
ReplyMatereplymate.io
AI phone receptionist for Australian service businesses. Shipped, learned a lot about Google Ads and conversion tracking the hard way, deprioritised when ExpertDrip became the focus.
On ice

Sheet 5 / About

Specifications

Full specification →
Material
Laravel, PHP, Vue
Service life
18 years as a software engineer
Location
Brisbane, AEST (UTC+10)
Operating mode
Build in public
Current focus
ExpertDrip and do-work
Tolerance
Opinions strong, usually wrong the first time
In progress
A book: The Mental Architecture of Physical Transformation

Eighteen years of software. A lawn business with real mowers. A course platform for founders. An open-source Claude Code framework. A book on the way.

I'm Tom Kaczocha. I run a lawn care business in Brisbane and build software for founders trying to figure out the same things I am.

Turns out service businesses are everywhere, and the tools they run on are universally terrible. That observation keeps informing what I build, who I build it for, and what I leave alone.

Read the full spec

Approval / issue register

Get the next sheet

Get notified when I publish new writing.

Check your inbox to confirm. Double opt-in.

Or keep your own copy

Approved for issue
T. Kaczocha
Date: 2026-05-16