— journal · Weekly
W27 · Pin Down the Vague.
One concept, three names, three layers — so nothing lined up. This week I pinned it down.
160 words1 min
Explore
Follow tags, themes, series, and time.
All(21)Engineering(5)Weekly(5)Ai(4)Fde(4)Learning journals(4)Skill(4)Delivery(3)Monthly(3)Review(3)Api(2)Llm(2)Notes(2)Product(2)Tips(2)Tools(2)Agents(1)Architecture(1)Context(1)Deploy(1)Design(1)Evaluation(1)Feedback(1)Fonts(1)Go(1)Incident(1)Miniapp(1)Performance(1)Programming(1)Report(1)Soft skill(1)Tech Report(1)
— report · Monthly
June · Converging the Toolchain.
June shipped no new features. It only made the existing ones hold. It may be the most valuable month of the year.
146 words1 min
— journal · Weekly
W26 · Fonts Arrive First.
One Chinese typeface weighed seventeen megabytes. Split into ranges, first paint drops under one — and the page finally looks like itself.
148 words1 min
— journal · Weekly
W25 · A Bad Rollback.
The rollback took forty minutes. Thirty-five of them went to working out which version to roll back to.
129 words1 min
— journal · Weekly
W24 · Interfaces as Contracts.
Renamed one field. Three downstream places broke at once. A week spent re-learning the word "contract".
141 words1 min
— tech · Ai
Wiring an Agent into Your System.
An agent is not a new system. It is a new client of the system you already run — treat it like one.
180 words1 min
— journal · Weekly
W23 · Fewer Tools.
Deleted four tools I never opened. Output held steady; the low-grade anxiety halved.
126 words1 min
— report · Monthly
May · The Mini Program as a Card.
In May one thing became clear: the mini program is not a mirror of the site. It is a business card that moves.
132 words1 min
— tech · Ai
Evaluation First, Then Everything Else.
Without an eval set, every change is a hunch. With one, iteration finally means something.
194 words1 min
— tech · Ai
Context Matters More Than Prompts.
Prompt tuning hits a ceiling fast. What actually decides output quality is the material you feed in.
184 words1 min
— report · Monthly
April · Rebuilding the Knowledge System.
In April I moved my notes out of the tools and reorganised them around one question: can this ever be cited?
118 words1 min
— tech · Ai
Let the Model Do What It Is Good At.
Models are good at making vague things concrete. They are bad at guaranteeing that something happens. That boundary is where engineering lives.
197 words1 min
— engineering · Fde
From One Delivery to a Product.
Turning one client's solution into a product is hard not because of abstraction, but because of deciding which specifics deserve to survive.
197 words1 min
— engineering · Fde
Building a Feedback Loop on Site.
The point of being on site is that feedback is fast. Route it through three layers of email and you have thrown that away.
186 words1 min
— engineering · Fde
Translate Requirements into Slices.
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.
211 words1 min
— engineering · Fde
Don't Write Code in Week One.
The first week of a forward-deployed engagement belongs to observation: see the real workflow before you touch anything.
210 words1 min
— journal · Skill
From Notes to Writing.
Writing is the output of a knowledge system, not an extra burden. The third entry in building a personal knowledge system.
188 words1 min
— journal · Skill
Connecting Your Notes.
Isolated notes are just fragments; connection turns them into knowledge. The second entry in building a personal knowledge system.
190 words1 min
— journal · Skill
The Foundations of Note-Taking.
Notes are for thinking, not for storage. The first entry in building a personal knowledge system.
185 words1 min
— journal · Skill
Productivity and Time Management.
Course notes on productivity, time management, and self-management.
737 words4 min
— report · Go
What is new in Go 1.15?
A field note on Go 1.15, with editorial components for code, references, tabs, steps, and callouts.
998 words5 min
— engineering · Fde
From One Delivery to a Product.
Turning one client's solution into a product is hard not because of abstraction, but because of deciding which specifics deserve to survive.
197 words1 min
— engineering · Fde
Building a Feedback Loop on Site.
The point of being on site is that feedback is fast. Route it through three layers of email and you have thrown that away.
186 words1 min
— engineering · Fde
Translate Requirements into Slices.
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.
211 words1 min
— engineering · Fde
Don't Write Code in Week One.
The first week of a forward-deployed engagement belongs to observation: see the real workflow before you touch anything.
210 words1 min