— journal · Weekly
W27 · Pin Down the Vague.
One concept, three names, three layers — so nothing lined up. This week I pinned it down.
Follow tags, themes, series, and time.
— journal · Weekly
One concept, three names, three layers — so nothing lined up. This week I pinned it down.
— report · Monthly
June shipped no new features. It only made the existing ones hold. It may be the most valuable month of the year.
— journal · Weekly
One Chinese typeface weighed seventeen megabytes. Split into ranges, first paint drops under one — and the page finally looks like itself.
— journal · Weekly
The rollback took forty minutes. Thirty-five of them went to working out which version to roll back to.
— journal · Weekly
Renamed one field. Three downstream places broke at once. A week spent re-learning the word "contract".
— tech · Ai
An agent is not a new system. It is a new client of the system you already run — treat it like one.
— journal · Weekly
Deleted four tools I never opened. Output held steady; the low-grade anxiety halved.
— report · Monthly
In May one thing became clear: the mini program is not a mirror of the site. It is a business card that moves.
— tech · Ai
Without an eval set, every change is a hunch. With one, iteration finally means something.
— tech · Ai
Prompt tuning hits a ceiling fast. What actually decides output quality is the material you feed in.
— report · Monthly
In April I moved my notes out of the tools and reorganised them around one question: can this ever be cited?
— tech · Ai
Models are good at making vague things concrete. They are bad at guaranteeing that something happens. That boundary is where engineering lives.
— engineering · Fde
Turning one client's solution into a product is hard not because of abstraction, but because of deciding which specifics deserve to survive.
— engineering · Fde
The point of being on site is that feedback is fast. Route it through three layers of email and you have thrown that away.
— engineering · Fde
A requirement is not a task list. It is a claim waiting to be tested — cut it into something you can ship within a week.
— engineering · Fde
The first week of a forward-deployed engagement belongs to observation: see the real workflow before you touch anything.
— journal · Skill
Writing is the output of a knowledge system, not an extra burden. The third entry in building a personal knowledge system.
— journal · Skill
Isolated notes are just fragments; connection turns them into knowledge. The second entry in building a personal knowledge system.
— journal · Skill
Notes are for thinking, not for storage. The first entry in building a personal knowledge system.
— journal · Skill
Course notes on productivity, time management, and self-management.
— report · Go
A field note on Go 1.15, with editorial components for code, references, tabs, steps, and callouts.
— report · Monthly
June shipped no new features. It only made the existing ones hold. It may be the most valuable month of the year.
— report · Monthly
In May one thing became clear: the mini program is not a mirror of the site. It is a business card that moves.
— report · Monthly
In April I moved my notes out of the tools and reorganised them around one question: can this ever be cited?
— Keyboard shortcuts