Entries for May 16, 2026
-
I am at @aiDotEngineer singapore, come and say hi if you are around!Image hidden -
-
the new /goal feature in codex still underperforms queueing my implementation prompt. for now e.g. when I give a goal to refactor the whole codebase, the model takes shortcuts, like only refactoring a subfolder, instead of the whole project --- presumably because it decided that it would be too big of a scope somewhere along the way, even though I instructed specifically to finish the whole thing so now I started doing both: set a goal, and then queue my regular implementation prompt. it's a stupid practice. just /goal should be enough in the long run, if implemented correctlyImage hidden -
i0 to i4 interest scale
One cool small invention in engineering management is the
p0,p1,p2,p3,p4priority scale.It compresses a lot of social and operational context into two characters. Lower number means higher priority. More importantly, priority is tied to action. If something is
p0, somebody needs to do something.But there is another scale I want for personal knowledge work:
i0,i1,i2,i3,i4.The
istands for interest. Priority is for actions. Interest is for attention.- If
p0means “act now”,i0means “do not lose this”. - If
p1means “schedule work”,i1means “read soon”. - If
p2means “do later”,i2means “useful context”. - If
p3means “low priority work”,i3means “weak signal”. - If
p4means “almost never work”,i4means “almost never revisit”.
This is useful when you need to rank interest concisely across many topics, sources, or articles.
For example, you might follow several sources about the same broad topic. One source is must-read, another is useful background, and another is only worth keeping around for occasional context. They are all about the same thing, but they do not deserve the same amount of attention.
I use this for myself in Scoop, a news intelligence system I am building to collect articles, group related ones, and rank how much attention they deserve.
- If