The Engineer’s Writing Kit
A four-week course that teaches engineers how to write essays, docs, and blog posts that people actually want to read — without sounding like a marketing email or a corporate memo.
What you’ll learn
Most engineers can write code that communicates intent. But when it comes to prose — blog posts, documentation, internal memos, RFCs — we default to either bone-dry technical writing or overly casual stream-of-consciousness. Neither lands well.
This course teaches you to find your voice, structure your ideas, and edit with precision. You’ll write four real essays during the course and get feedback on every one of them from me and a small cohort of peers.
By the end, you’ll have a repeatable process for going from “I have a vague idea” to “I published something I’m proud of” — in hours, not weeks.
Curriculum overview
Week 1: Finding your voice
We start by reading five essays that work — and dissecting why. You’ll identify the writing tics that make technical prose feel flat (passive voice, hedge words, unnecessary abstractions) and practice rewriting real examples. Your first assignment: a 500-word essay on something you built recently, written as if you’re explaining it to a friend over coffee.
Week 2: Structure and rhythm
Good writing has a shape. This week covers the anatomy of an essay: openers that hook, paragraphs that flow, transitions that don’t clunk. We’ll study the inverted pyramid, the narrative arc, and the “show-then-tell” pattern that works especially well for technical content. Assignment: restructure a draft you’ve been sitting on.
Week 3: Editing ruthlessly
First drafts are supposed to be messy. The skill is in the edit. This week you’ll learn to cut 30% of your word count without losing meaning, spot sentences that are doing no work, and develop an eye for rhythm at the sentence level. We’ll do live editing sessions where I rewrite paragraphs in real time and explain every decision.
Week 4: Publishing and feedback
The last mile: titles, deks, meta descriptions, and the psychology of hitting “Publish.” We’ll cover distribution basics (where to post, how to build an audience of 1,000 readers), and you’ll publish your final essay to the real internet. Then we do a group critique session and celebrate.
What past students say
“I’d been blogging for three years but never felt confident about my writing. After this course, I published an essay that got to the front page of Hacker News. The editing framework alone was worth the price.”
“Fazliddin doesn’t teach you formulas. He teaches you to hear your own writing. I write internal docs differently now — my team actually reads them.”
“The cohort feedback was the best part. Having five other engineers read your draft and tell you where they got bored is brutally useful.”
Frequently asked questions
Do I need prior writing experience?
No. If you can write a clear pull request description, you have enough skill to start. The course meets you where you are.
How much time does it take per week?
Plan for about 3–4 hours: one hour of lessons, one hour of reading, and 1–2 hours of writing. It’s designed to fit alongside a full-time job.
Is there a refund policy?
Yes. If you complete Week 1 and decide it’s not for you, email me and I’ll refund you in full, no questions asked.
When does the next cohort start?
Cohorts run every 6–8 weeks. Join the waitlist and you’ll be notified 2 weeks before the next one opens.