Great line from the CTO of Proton. I’m paraphrasing and stealing it :
Your job is not to use agents to help you write code. Your job is to lead the agents to help them write code.
𝗬𝗼𝘂 𝗰𝗮𝗻 𝗰𝗼𝗱𝗲 𝗼𝗻𝗹𝘆 𝟰 𝗵𝗼𝘂𝗿𝘀 𝗽𝗲𝗿 𝗱𝗮𝘆. 𝗛𝗲𝗿𝗲'𝘀 𝘄𝗵𝘆.
That afternoon, brain fog isn't laziness. It's biology hitting a wall.
Cal Newport's research on deep work shows that most people max out at 4 hours of concentrated effort per day. K. Anders Ericsson found the same pattern studying elite violinists: 4 hours of focused practice, then performance drops off a cliff.
But here's what's worse: most developers don't even get close to that ceiling.
Software .com analyzed 250,000 developers and found the median coding time is 52 minutes per day. Not hours. Minutes. Clockwise data shows why engineers spend 10.9 hours weekly in meetings. Engineering managers? 18 hours.
And every interruption costs you. Gloria Mark's research: 23 minutes to recover from a single interruption. For programmers, rebuilding mental context? 30-45 minutes. One "quick question" can destroy an entire afternoon.
The flip side is promising. Csikszentmihalyi's 10-year study found that people in flow states are 500% more productive. But flow needs 15-25 minutes of uninterrupted time just to begin.
So we're stuck in a loop: meetings eat mornings, interruptions fragment afternoons, and that 4-hour cognitive window shrinks to almost nothing.
The fix isn't working anymore. It's protecting those few hours like they're the only ones that matter, because they are.
👉 Full breakdown with strategies: https://t.co/TnJf0gFx3J
Image: Sketchnotes (by SketchingDev .co .uk)
@Veldrin92 Вся деятельность людей на шкале всей деятельности, которая происходила с планетой, лишь незначительная погрешность. Планета будет норм себя чувствовать и после людей.
@from_ams @kuskuskiss@selflovefeels Проще в вакансии указать, только для жителей какой-то страны с имеющимся разрешением на работу. Но если ИТ компания такое требует, можно представить какое у них управление и все горит еще вчера.