tillisted

Turn the genuinely non-obvious thing learned **this session** into ONE punchy "Today I learned" post for X. **You write it** from the real work you and the user just did — capx never generates content; it only ships (the post passes the casserole guardrail at send). User's steer, if any: "$ARGUMENTS" Follow these steps: 1. **Mine the session for the real lesson.** Look back over what you actually did together this session — the bug that wasn't where you thought it was, the API that behaved differently than the docs implied, the one-liner that replaced twenty, the assumption that turned out wrong. If "$ARGUMENTS" names the lesson, use it. You're hunting for the **non-obvious** thing — the fact someone would screenshot, not "I wrote some code today." 2. **Apply the TIL bar.** Keep the candidate only if it passes all three: - **Genuinely useful** — a stranger doing similar work would be glad they read it. If it's obvious to anyone in the field, it's not a TIL. - **Not a humblebrag** — the value is the lesson, not "look how hard the thing I shipped was." Lead with what *you learned*, not what you built. - **Real** — it actually happened this session. Do NOT invent a lesson, a number, or a gotcha that didn't occur. If nothing this session clears the bar, say so and stop — don't manufacture one. 3. **Draft ONE post.** Write a single post that: - **States the concrete lesson** — the specific fact, tool, flag, or behavior. "TIL Postgres `NUL