A VP of Technology is back at full-stack commit pace with agents

Orestis Ioannou, VP of Technology at Bold.org, pulled his GitHub contribution calendar for every month from January 2019 to today. The chart is in a post he published on 27 October. The Hacker News thread had 263 points when it crossed the gate for this item.

He is now a VP. His role has less feature work in it than his old roles did. On paper his chart should look like his Principal Engineer years. Instead it is back where it was when writing code was his whole job.

The numbers he published

Ioannou joined Bold.org in January 2020. He was a Full Stack Engineer until August 2022. He was a Principal Engineer until August 2025. He has been VP of Technology since then. GitHub counts commits, pull requests, reviews and issues, including private work.

His busiest coding year was 2020, with 2,711 contributions. 2021 dropped to 1,839 and 2022 to 1,498. From August 2022 to July 2025 he averaged 114 contributions a month. As a Full Stack Engineer he had averaged 173 a month. His lowest year was 2023, with 1,189.

Then 2026. By 27 October he was at 2,102 contributions. That is already more than any full year from 2021 to 2025. His busiest month in the whole timeline is August 2026, at 427 contributions. His previous peak was 319, in April 2020. His median weekday went from 3 or 4 across 2022 to 2025, to 7 this year. He has had 18 weekdays with zero recorded activity so far in 2026. Each full year from 2022 to 2025 had 40 to 46 such days.

What he says changed

The pitch was that AI would write the boring parts, so engineers would go home earlier. Ioannou says that is not what happened to him. He uses agents for all of his engineering work. He can investigate and release things that would not have been worth starting two years ago. He is also working more than he ever has.

He describes a cycle. A new model or a new workflow makes something possible that was not possible last month. His head fills with ideas. Because implementation is cheap, there is no natural friction stopping him from pursuing all of them at once. So he does. He starts more agents. He opens more threads. He says yes to more experiments. That works for a few weeks. Then the reviewing and context switching catch up with him. He pulls back to a steadier flow.

August 2026 is the clearest example. Every weekday from 10 to 27 August was between 14 and 43 contributions. The month ended at 427. September stayed high at 301.

Why context switching is the cost

Two or three serious tasks a week was tiring in a familiar way. Working with many agents is tiring in a new way. Each agent eventually comes back to him. It brings a question, a plan to approve, a diff to read or a result to make sense of. Responding means loading a different problem, a different repository and a different set of decisions. Ioannou says his attention is spread across more problems. Moving between them is draining.

The practical read for anyone running a team. Agents raise the ceiling on what a single engineer can take on. The floor on reviewing capacity has not moved. Ioannou describes bursts followed by a pull-back. That is the shape of a team hitting the review limit one engineer at a time.

Source

AI Promised Less Work. I Have Never Worked More., Orestis Ioannou. Hacker News discussion.