Ask
96
@crypt_cass ·

is it normal to get 90 good minutes on a weeknight after eight hours of coding Energy & Burnout

I sit down at 20:30 planning three hours. By 22:00 I am reading changelogs and moving trello cards around instead of writing anything. People online describe four productive evening hours routinely and I cannot get near it. Is 90 minutes what this actually looks like, or am I doing something wrong that other people have solved?

8 answers Share
Report

Answering anonymously — a moderator will review it first.

  • @ines_marchetti · 2mo ago · 3 replies

    Ninety minutes of real focus after a full day of the same activity is not low. It is approximately the ceiling. Most people describing four evening hours are counting time at the desk, not output, and if you asked them to log what shipped you would see something close to your number.

    Two adjustments that made mine feel bigger without being bigger:

    • Weeknights get mechanical work — copy, small fixes, support email, the thing you already know how to do. Anything requiring a decision or a design goes to a weekend morning. Trying to design a schema at 21:30 produces a schema you rewrite on Saturday.
    • End every session by writing the exact next step. Otherwise the first twenty minutes of your ninety go on reloading context, and you have just spent a quarter of your evening remembering where you were.
    121
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @crypt_cass · 2mo ago

      The split is what I was missing. I have been spending my worst hours on my hardest problems and then concluding I am bad at evenings.

      24
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
    • @bedroomsynth · 2mo ago

      Same rule here. If it needs a decision it goes on the Saturday list. Everything else is fair game at 21:00 and I stopped feeling bad about closing the laptop at 22:00.

      15
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @lena_arbogast · 2mo ago

    Normal. What is not sustainable is doing it five nights a week — three nights plus one weekend morning beats five nights when you measure it over three months, because five nights produces a week off every month or so to recover, and you never count that week.

    68
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @airflow_amir · 2mo ago

    Your day job is the same activity, which is the whole explanation. People whose day job is a warehouse or a classroom genuinely do get more evening coding hours out of the same body. It is not a discipline gap between you and them, it is a different starting state.

    39
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @leech_wrangler · 2mo ago

    Log it honestly for two weeks with a timer. Almost everyone finds their real number, stops comparing it to a fantasy number they read somewhere, and immediately feels better about their project.

    27
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @slowmiles_kat · 2mo ago · 2 replies

    90 minutes, four nights, fifty weeks is 300 hours a year. That is a product.

    11
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @dockerfile_yuki · 2mo ago

      It is also more focused hours than a lot of funded teams put in before their first launch, once you subtract their meetings.

      8
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report