choutos

That's exactly my experience. I achieve more in those 2 hours than in the rest of the day.

Pretty much all the code I produce nowadays is generated with AI help, to some extent. No problem admitting it.

The value is not writing the code anymore, but deciding what to create and keeping the code maintainable and understandable.

Start early, before everyone is working. Or late, when everyone stopped. Block "focus" periods in your calendar, disabling notifications.

This should be an 'Ask HN', but it’s an ad instead.

Do you mean in terms of a loss of employment rights?

Sufficiency versus maximization. China maximizes output given the means available (and treats ever-growing means as self-evidently good), the Netherlands treats wellbeing as the fixed end and then economizes on the means needed to reach it: effort, resources, consumption.

In words of E. F. Schumacher: "the maximum of wellbeing with the minimum of consumption"

15% monthly

This is a fair observation, and I think it actually reinforces the argument. The burnout you're describing comes from treating AI output as "your code that happens to need review." It's not. It's a hypothesis. Once you reframe it that way, the workflow shifts: you invest more in tests, validation scenarios, acceptance criteria, clear specs. Less time writing code, more time defining what correct looks like. That's not extra work on top of engineering. That is the engineering now. The teams I've seen adapt best are the ones that made this shift explicit: the deliverable isn't the code, it's the proof that the code is right.

LogSeq, with the "brain" shared across devices using Koofr over webdav

Can you (or anyone) recommend a good one? Thank you!