Shipping Words: How I Use Dev Habits to Finish Writing Contests

Javis Frederick — Wed, 24 Sep 2025 00:03:08 +0000

I used to treat writing like an “R&D spike” that never shipped. Once I started entering writing contests, it clicked: prompts are specs, word counts are budgets, deadlines are CI. The same habits I use to deliver code help me deliver words.

Map it to engineering

Prompt = Ticket / Spec. Read it twice. Confirm acceptance criteria (theme, format, word count).

Draft = First working build. Compiles, not optimized.

Edit passes = Refactors. Small, focused sweeps beat one giant rewrite.

Feedback = Code review. You don’t need 100 comments—just a few actionable notes.

Submit = Release. Tag, ship, learn, iterate next sprint.

The routine (small, repeatable, boring—in a good way)

Pick fast. If the prompt doesn’t spark an image in 10 seconds, skip it. If it does, lock it.

Draft in one sitting (25 min). No second tabs. When you hit a gap, drop a TODO and keep moving:
[TODO: replace with a sound image: server fan / elevator chime]

Refactor for –20%. Cut duplicate ideas and filler (very, really, just, that). Swap vague verbs for precise ones.

Run “read-aloud” tests. Fix stumbles, long sentences, and choppy jumps.

Land the ending. Echo the opening or turn the idea. Make the final line carry the meaning solo.

Five quick passes (separate concerns)

Meaning: one-sentence heart line. If you can’t state it, you have two pieces—split.

Cut: remove 15–25%; compress phrases; kill redundancy.

Flow: read aloud; smooth transitions and rhythm.

Image: one concrete detail a reader can see/hear/touch; trim decoration.

Landing: draft three endings; keep the cleanest. If cutting the last line helps, keep the cut.

Tiny PRs, not mega-commits

Before I submit, I check:

One-sentence “heart” summary

One concrete image

Final line that turns or echoes

Filler trimmed; verbs strengthened

Word count + rules verified

Results are snapshots, not verdicts

Some entries place; others don’t. I still win if I finish, submit, and learn. I keep drafts, refactor later, and (when rules allow) ship a stronger v2. Consistency compounds more than any single result.

Want the full workflow?

I documented the 7-day plan, checklists, and examples here: writing contests

Forem: Javis Frederick

Shipping Words: How I Use Dev Habits to Finish Writing Contests