Cheap implementation raised one engineer's workload

Ioannou pulled his GitHub contribution counts, private work included, for every month from January 2019. As Principal Engineer he averaged 114 contributions a month from August 2022 to July 2025, against 173 as a full-stack engineer. By October 27, 2026 he was at 2,102, more than any full year from 2021 to 2025. August 2026 was the busiest month in the timeline at 427, against a previous high of 319 in April 2020. His median weekday went from 3 or 4 contributions (2022 to 2025) to 7, and he counts 16 days with 24 or more contributions this year, against one per year before.

He calls the counts "a rough signal of activity, not a measure of value," and they mix commits, pull requests, reviews and issues. This is one person's record, with an incomplete 2019 baseline. His account of the cause is that running several agents in parallel means each one returns with a question, a plan or a diff, and the context switching is what tires him. He describes three bursts since January, each followed by a pullback.

Why it matters: This is a single self-reported case, not a measurement of agent productivity. It does name a constraint that is easy to miss when planning agent fleets: the human attention needed to review and decide scales with the number of agents running, not with how cheap each task has become.