Labels, phone to printer
Making labels used to be tribal knowledge — vendor software, training, and every crew's output a little different. Now anyone drills room → rack → port on a phone and the label comes out of the printer — through a Linux driver I wrote from scratch, and a spooler that never splits one rack's labels across machines.
Inventory you can text
Ask the group chat.
The yard answers.
The laydown yard lives in software: the real floorplan with every shelf pinned, bays and levels laid out like the steel, a chain of custody on every part — and a bot in the crew chat that answers stock questions with a tamper-evident audit trail behind it.
Records that stay alive
Validation tickets. Cable tracking from pull to test. An as-built drawing that fills itself in as work completes — ghost to built, stamped and flagged. The paperwork becomes a by-product of doing the work, not a second job after it.
Drill from the hall to the port
Every view drills down: hall → module → rack → U → port. The floor map, the labels, the reports — same motion everywhere. Pick a hall and land on a single rack: completion by phase, from first pull to link-up, with damage flagged right where it sits. Nobody asks "where are we at" — they look.
Building automation, the easy way
A self-hosted media & control hub: pick a show on any browser, and an agent on the local network wakes the display and casts straight to it — no apps on the TVs, nothing exposed to the internet. Scenes run whole rooms on one tap.
Off the screen
The software ends in physical things: printed labels on live cable, engraved metal, calibrated machines. Drivers, fixtures, and hardware tuned until they work on the floor — not just on the bench.
It follows me home: I modified my daughter's training toilet with a Raspberry Pi Pico — her cartoon plays when she sits down, pauses when she stands up. She basically trained herself.