---
title: The writing routine that works
description: "A daily writing habit that finally works: one post a day, a weekly format rota, and a hard time box that forces the draft to exist."
canonical: https://lukeocodes.dev/building-a-writing-routine-that-works
type: article
locale: en_GB
published: 2026-07-05T00:00:00.000Z
modified: 2026-07-05T00:00:00.000Z
authors:
  - Luke Oliff
section: Developer Experience
tags:
  - Developer Experience
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/building-a-writing-routine-that-works#article
        headline: The writing routine that works
        alternativeHeadline: Building a writing routine that actually sticks
        description: "A daily writing habit that finally works: one post a day, a weekly format rota, and a hard time box that forces the draft to exist."
        datePublished: 2026-07-05T00:00:00.000Z
        dateModified: 2026-07-05T00:00:00.000Z
        url: https://lukeocodes.dev/building-a-writing-routine-that-works
        mainEntityOfPage: https://lukeocodes.dev/building-a-writing-routine-that-works
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: Developer Experience
        articleSection: Developer Experience
        about:
          - "@type": Thing
            name: Developer Experience
        abstract: I have been writing about technology for a long time. I have also been inconsistent about it for that entire period. A few months ago something clicked and I have published something every day since. Not because I found more willpower. Because I changed the system.
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=The+writing+routine+that+works&d=A+daily+writing+habit+that+finally+works%3A+one+post+a+day%2C+a+weekly+format+rota%2C+and+a+hard+time+box+that+forces+the+draft+to+exist.&e=Writing
        wordCount: 554
        timeRequired: PT3M
        publisher:
          "@id": https://ably.com/#organization
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: The writing routine that works
            item: https://lukeocodes.dev/building-a-writing-routine-that-works
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# Building a writing routine that actually sticks

Jul 2026 · [Developer Experience](/blog/category/developer-experience) · 3 min read · [Luke Oliff](/authors/luke)

I have been writing about technology for a long time. I have also been inconsistent about it for that entire period. A few months ago something clicked and I have published something every day since. Not because I found more willpower. Because I changed the system.

### The one day at a time rule

The single biggest change was stopping myself from writing posts about multiple things at once. I used to have three or four drafts open at any time, each a paragraph or two long, none finished. Every time I switched between them I lost context and momentum.

Now I write one post per day. Not two. Not a post plus a draft for tomorrow. One finished post, published, then I stop. The constraint forces me to actually finish things instead of collecting half-written ideas.

### The structure matters more than the inspiration

I used to wait for inspiration. That meant I wrote when I felt like it, which was not every day. Now I have a loose weekly structure that tells me what type of content to write on which day. Monday is industry analysis, Tuesday is a short tutorial or trick, Wednesday is a deep dive, and so on.

The structure removes the hardest part of writing: deciding what to write about. When the day tells me the format, I only have to choose a topic within that bucket. That is a much smaller decision and one I can make in a few minutes instead of agonising over for hours.

### The timer

I set a rough time budget per post type. Short posts get a hard stop after 45 minutes. Deep dives get two hours. If the post is not done by the deadline, I publish what I have or skip the slot and try again the next day. The time box forces me to write to length instead of writing until I run out of things to say.

This was counterintuitive. I thought better writing came from more time. Actually, better writing comes from editing, and editing only happens when the draft exists. A time box forces the draft to exist.

### What I still struggle with

The hardest part is still the blank page. I have gotten faster at filling it but the first paragraph is always the slowest. I have learned to write the introduction last instead of first. Write the body, then go back and figure out what the post is actually about. The introduction writes itself once you know what you said.

Also still working on not over-editing. I can spend an hour moving sentences around and end up with the same post I had after 15 minutes. Learning to ship good enough instead of perfect is an ongoing process.

### Why it matters

Writing every day has changed how I think about my work. I process what I am learning more deeply because I have to articulate it. I notice patterns I would have missed because I am looking for things to write about. And I have a record of what I was thinking about on any given day, which is surprisingly useful for spotting when my own opinions changed and why.

The system works because it removes the friction. Not because I got better at being disciplined. That is the real lesson.

[← Newer: Pricing wars are good for developers](/pricing-wars-are-good-for-developers)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
