The scoping conversation that stops a project going wrong in month three
Scope failures are discovered late and paid for by the engineer. These are the questions that surface them early.
Growth
The business half — search, audience, and what solo distribution actually costs.
15 posts
Most productivity advice fails engineers, and the reason is measurable
Advice built for shallow task-switching inverts when the task takes forty minutes to hold in your head.
The post that went to the wrong account
A publication identifier is an optional field that silently defaults. The API reports success either way, so the only way to know is to verify the response.
A status column is wrong within a week
A hand-maintained status field said draft for a hundred posts while sixty-eight were live. State that is stored is a memory; state that is derived is a measurement.
Twenty-four of my tags file exactly one post
Across 219 posts I had 88 distinct tags and 24 appeared exactly once. A tag that gathers one item is a label, and labels do not help anybody find things.
One of the two links is always missing
A syndicated copy links home immediately; the original links out only after a rebuild. The asymmetry means one direction is reliably broken for a while.
The two fields that only exist in the interface
Two SEO fields have no API path on the platform I syndicate to. That single gap is the reason the pipeline stops at a draft instead of going live.
Syndicate to a 404 and you donate the SEO
A canonical that 404s when the syndicating platform fetches it does not transfer authority. Their copy becomes the original, and the order is the whole fix.
Your meta description is cut mid-sentence
A description clipped to a character limit is severed mid-clause. Writing to fit whole is the fix, and the field you edit may not be the one that ships.
The ad slots on this blog are finished and render nothing
Nine ad placements built, gated and verified to render nothing. What you can decide before approval is where ads may go, and that is the decision that matters.
A tag feed is not a list of your posts
A feed returns what it decided to include, not everything that exists. Reading a lower bound as a complete list produces duplicates and false gaps.
A hundred posts is the easy half
Producing a hundred technical posts is a scheduling problem. Keeping the hundredth as good as the first needs a standard the work is checked against.