| layout | post | ||||
|---|---|---|---|---|---|
| title | TODO: Title (under 70 chars, sentence-style, no em dashes) | ||||
| description | TODO: 1-2 sentences. The hook for skim-readers and search. State the topic and the takeaway. | ||||
| date | YYYY-MM-DD | ||||
| tags |
|
||||
| permalink | /blog/TODO-slug/ |
TODO: 3-5 sentences capturing the project, the insight, and why it matters. A leader should be able to stop here and have the headline.
If you take one thing from this post: TODO: the single most quotable claim.
| Outcome | What it means |
|---|---|
| TODO: concrete outcome | TODO: why it matters |
| TODO: concrete outcome | TODO: why it matters |
| TODO: concrete outcome | TODO: why it matters |
| TODO: concrete outcome | TODO: why it matters |
TODO: 1-2 paragraphs framing the problem for someone who does not live in this area day-to-day. Land the headline insight here, not at the end. This is where the leader reader should nod and say "okay, this is a real problem."
Goal: TODO: one-sentence Task statement. What was the actual goal of this project? This sentence is the Task in STAR; recruiters lift it verbatim.
TODO: 1-2 paragraphs of high-level approach. Then a bulleted decomposition by category:
- Category 1: what, how scoped, how measured.
- Category 2: same.
- Category 3: same.
TODO: closing paragraph that ties back to the "why this matters" insight.
TODO: engineer-targeted section. Pipeline design, specific patterns, numbered steps when useful, code blocks for config/policy snippets. This is where someone implementing a similar project gets actionable detail.
2-4 lesson-shaped bullets. Forward-looking framing. Each bullet is a genuine lesson; cut filler.
TODO: lesson 1. Short explanation.
TODO: lesson 2. Short explanation.
3-6 bullets. Each must be unique to the post.
- TODO: bold headline lesson. One-sentence explanation.
- TODO: bold headline lesson. One-sentence explanation.
- TODO: bold headline lesson. One-sentence explanation.
- TODO: bold headline lesson. One-sentence explanation.