~ $ cd simulators/developer-meetings && cat *
Developer Meetings Simulator
How different meeting types and schedules, through their effect on focus and fatigue, change what a developer delivers over several weeks.
How it works
- Focus and fatigue: each hour of work adds to both. What gets done in that hour is the difference, clamped between 0 and 100.
- Meetings produce nothing, and move focus and fatigue by what that kind of meeting does to a person. Lunch resets both; a planning session drains focus and adds fatigue.
- A feature is finished when the hours add up to its size. Finishing one costs the focus that was built up for it.
- Weeks are five days of eight hours, 9:00 to 17:00.
The simulation
Pick a meeting type, then click and drag on the calendar to schedule it. Click a meeting to remove it. Everything recalculates as you change it.
Things to try
- High focus, low fatigue: focus 75, fatigue 10, and few meetings. Watch the features pile up.
- A meeting-heavy week: several boring meetings a day. Watch the compound effect on delivery.
- No lunch: remove the lunches and watch fatigue build through the afternoon.
- Planning on Monday: put the sprint planning first thing, and compare with spreading it through the week.
What it tends to show
Breaks that reduce fatigue pay for themselves. Meetings that break focus cost more than their length. Where a disruptive meeting sits in the day matters as much as whether it happens. And a consistent rhythm beats an erratic one.