The TWIMCO notebook
Field notes.
Useful observations from inside the work.
For people building a better way.
387 notes

OpenAI's text watermark isn't your record of what AI wrote.
OpenAI's new text watermark is a faint signal that light editing wears away, and you can't check it yourself. Decide the switch per project, then keep your own record.
Read the note ↗︎
Before peak, re-read last year's rescued orders.
Carrier peak fees widen in late October. Before then, pull ten orders your team had to rescue last holiday and follow each one back to the moment it first went wrong.
Read the note ↗︎
Ride along for a shift before you design the field app.
Spend one shift in the van with the person who'll use your field app. Gloves, a weak signal, and a customer watching will redesign it faster than any workshop.
Read the note ↗︎
TikTok's new buy button is the easy part.
TikTok now lets people buy from your own store without leaving the feed. Before you say yes for the holidays, picture the night a video takes off, and ask what your stock count, product pages and support inbox would do.
Read the note ↗︎
A comparison table is not a decision.
Forty rows of checkmarks don't help anyone choose. People want to know which difference matters for them, and what it would mean in their situation.
Read the note ↗︎
Your first suppliers need a person, not a form.
Your launch got sign-ups. Most of those suppliers still can't take an order. Walk one of them from yes to first payout and you'll see what the signup form left out.
Read the note ↗︎
Price what you'd own before you switch to open weights.
Reflection's open-weight model hasn't shipped yet, and people are already asking whether to switch. The download will be free. Running it won't be. Here's what you'd be taking on.
Read the note ↗︎
Your spreadsheet is already software. Treat it like it.
There's a tab called FINAL v3 that three people edit and one person really understands. That isn't a messy file. It's an application nobody has designed yet.
Read the note ↗︎
Rotate credentials like a cutover, not a chore.
A calendar ping is not a rotation plan. Keep both values valid for a named window, flip callers in order with probes, and name who rolls back if the new one fails.
Read the note ↗︎
Before your Gems become Skills, find the ones doing real work.
Google started putting Skills into Workspace today, and Gems are on their way out. Most of your team's Gems can just move. A few are quietly running a process, and those need more than an auto-convert.
Read the note ↗︎
The clock does not advance on a promise.
Someone says the deal is ready while someone else is still waiting on a signature or a funds check that was "basically done." In a complex close, the clock should move when named conditions are met and proven, not when the room feels finished.
Read the note ↗︎
A retry is not a second write.
A payment capture times out, and the honest next move is to try again. The dishonest result is a second charge. "Our API is idempotent" isn't a policy until someone says what counts as the same attempt and who owns the duplicate.
Read the note ↗︎
Bound the AI answer with a citation pack before it hits the queue.
A fluent recommendation lands in the review queue looking finished. The reviewer has three minutes and no link to the record behind it, so they rubber-stamp it or redo the work. Answers need to arrive with their sources attached.
Read the note ↗︎
Write the change-communication brief before you flip the flag.
Engineering called it a small UX tweak. At 10 a.m. ops finds a status that means something different and a filter that's gone, and support starts inventing explanations. Tell the people who run the system before the flag flips.
Read the note ↗︎
Detect inventory truth drift before you trust the count.
The storefront says three, the warehouse says one, the marketplace says two. Someone ships on one number while someone else promises a buyer on another. Counts will disagree under load. The trouble starts when nobody decided what happens then.
Read the note ↗︎
Spec the batch-failure alert before the nightly job.
Just after midnight the batch fails, and someone gets "job failed" with no counts, no sample records and no safe first step. Or it half-fails, reports success, and the gap turns up at 9 a.m. in customer care.
Read the note ↗︎
When your vendor gets bought, use the quiet week.
Reports Sunday had Schneider Electric close to buying PTC. When a tool your team runs on lands in a headline like that, the reassuring email isn't a plan. Here's how we'd spend the first month instead.
Read the note ↗︎
Make the submission prove itself before a person reads it.
Google just paused an open source bug bounty because machine-written reports buried the people reading them. If your support queue, claims inbox, or seller applications run on human reading time, you're next in line.
Read the note ↗︎
Who may refund what—before macros invent policy.
If a support macro can say "we'll refund that," it's already making policy. Decide who can approve which amounts and reasons, and what the payment record has to show, before anyone promises money back.
Read the note ↗︎
Test the deny shapes before you trust the policy.
Your agent policy says no rm -rf. Has anyone tried TZ="$HOME" rm -rf, a command chained after &&, or a symlink to the file you blocked? Try the odd shapes before you call it enforced.
Read the note ↗︎A familiar problem? Let’s look closer.
Tell us where you want to go. We’ll find the first thing worth changing.
Tell us about it ↗︎