Skip to main content

Blog-as-Thinking: One Post Per Quarter

What This Concept Is​

A technical blog is not a publication schedule. It is a forcing function for thinking. The concept here is a modest cadence (roughly one substantive post per quarter, four per year) with a specific goal: to turn work you have already done into a piece of prose another engineer would read.

The minimum viable version is four 800-1,500 word posts per year, each tied to something real you built, debugged, or decided. That rate is low enough to be sustainable and high enough to compound.

Blogging at this cadence is explicitly a low-ambition commitment. It is not "I am going to become a content creator." It is "I will write down the four most interesting things I did this year, in prose another engineer can read." That reframing is the whole reason it becomes sustainable: the stakes on any single post are low, which makes shipping easy, which keeps the pipeline moving.

The compounding effect is where the value lives. One post a quarter is not much. Forty posts over a decade is a body of work. Forty posts cross-linked to forty capstone-era ADRs, bug write-ups, and benchmarks is a career-level artifact that an interviewer, a collaborator, or future-you can read without clone-and-run.

Why It Matters Here (In the Capstone)​

Writing exposes thinking. Every post enforces three things:

  1. You re-examine the decision with fresh eyes.
  2. You confront the parts you never fully understood.
  3. You produce an artifact a reviewer can read without cloning a repo.

Posts also compound: four posts per year for three years is a body of work. It makes your bio linkable. It gives interviewers something to ask about. And -- most usefully -- it gives future-you a reliable way to recall why you did things.

This concept is SUPPORTING because it is not strictly required to graduate. But without it, the other concepts in this cluster have no place to live. The bio needs a link. The case study needs companions. The portfolio needs writing that is not just code.

Concrete Example: Four-Post-Per-Year Structure​

Four slots per year, each mapped to a type:

QuarterPost typeTypical source
Q1Deep dive on one technical decisionAn ADR from the last six months
Q2Debug storyA real incident or hard bug
Q3Tool or pattern comparisonBenchmarks or design exercise
Q4Retrospective / year in reviewThe previous three posts plus what they missed

This is not a rigid map. It is a default structure that removes the "what should I write about?" question, which is the main reason blogs stall.

Concrete Example: Post Skeleton​

# <specific title, not clickbait>

**One-paragraph summary of what you're about to read,
including the answer.** (The reader should be able to stop
here and leave with the main point.)

## Context

<What problem, what constraints, why this was interesting.>

## What I Tried

<2-4 approaches, each with one short paragraph.>

## What Worked

<The chosen approach, with a diagram if it helps.>

## Tradeoffs

<What you gave up. This is where posts earn credibility.>

## What I'd Do Differently

<One paragraph. No padding.>

A post following that shape runs 800-1,500 words and reads fast.

Concrete Example: Capstone Post Candidates​

For a typical capstone, at least five post candidates exist on Day 1:

CandidateTypeSource artifact
"The idempotency layer that saved three feeds"Deep diveADR-0007
"The race condition that took a week to find"Debug storyIncident postmortem from M04
"Three rate-limiters walk into an API"Tool comparisonBenchmark from M02
"What I wish I had known about Postgres indexes"RetrospectiveSchema evolution history
"One diagram that replaced three sections of my case study"CraftThe failure-mode diagram from cluster 1 concept 03

Pick the one whose answer surprises you most; that is usually the most honest post.

Common Confusion / Misconceptions​

Writing posts that try to teach a topic the author just learned. Tutorial posts compete with ten thousand others and mostly fail. Posts that describe what you actually did -- with the specific numbers, specific failures, specific tradeoffs -- do not compete with anyone, because nobody else was there.

Chasing engagement metrics. The goal is the post existing, not the post trending. Two readers who actually use your post beat two thousand who skim it.

Writing to impress. Ship the one that makes you slightly uncomfortable. A post that exposes a real mistake you made reads higher-trust than a post that presents you as a consistent winner.

Treating cadence as willpower. A quarterly cadence needs a pipeline, not discipline. If the idea list is empty the day you want to draft, the system failed two months ago.

How To Use It (In Your Capstone)​

The sustainable cadence requires a pipeline, not willpower:

  1. Keep a running "post ideas" file, one line per idea, captured the moment it appears (usually mid-incident or mid-ADR).
  2. At quarter boundaries, pick the most honest idea, not the most impressive.
  3. Draft in one sitting. Do not polish on day one.
  4. Sit on it for 3-7 days, then edit (see concept 09).
  5. Ship.
  6. Cross-link to the related ADR, code path, or incident so the post survives context-loss.
  7. Archive any post older than three years whose claims no longer hold; replace with a "see also" pointer to the newer one. Rot is real.

Check Yourself​

  1. Do you have a running "post ideas" file? If not, start one today.
  2. Can you name four specific post ideas from your capstone work right now?
  3. For your best idea, is the answer already decided, or are you planning to "figure it out while writing"?
  4. Is any existing post of yours more than two years old with claims you no longer believe? If yes, edit or archive.
  5. Does each post link back to a capstone-era artifact (ADR, incident, benchmark)?
  6. If you had to ship a post this week, which idea would feel honest? That is next quarter's post.

Mini Drill or Application (Capstone-scoped)​

Three drills:

  1. Candidate list. From your capstone, list five candidate posts. For each, write just the one-paragraph summary that would sit at the top of the post. If you cannot write the summary, you are not ready to write the post.
  2. Surprise pick. Of the five, pick the one whose summary surprised you most. Schedule a drafting session this week -- two uninterrupted hours in one sitting.
  3. Pipeline file. Create writing/ideas.md in your portfolio or site repo. Paste the five candidates plus any new ones. Commit. Every idea that hits you over the next six months goes in here without judgment; you pick at quarter boundaries.

The goal by end of capstone: first post drafted and shipped, pipeline file seeded, second quarter's candidate chosen.

Transfer / How This Synthesizes Prior Semesters​

Quarterly posting is a specific instance of a general pattern from across the degree: disciplined, low-stakes cadence producing compounding artifacts.

The transferable fact: consistency beats intensity. One sharp 1,200-word post per quarter, four times a year, for three years is a more career-shaping artifact than one 4,000-word magnum opus that nobody finishes.

See also (integrative)​

Source Backbone​

Portfolio assessment packages evidence from the whole curriculum. These books provide the technical and professional backbone for the narrative.