The Wicked Reason Removing Code Beats Better Scheduling

My colleague Marko Ilić has published an insightful piece on how to schedule work on the critical path, and I recommend reading it before proceeding here. ContentsElimination vs. Scheduling: An Organisational PerspectiveWhat's Good for the Goose..."Preloading" as SchedulingScheduling Is For ClosersGeneral-Purpose Advice ...and welcome back. As you likely anticipated, Marko's beautifully presented post kicked off healthy discussions around the office. As we almost always see eye-to-eye, it seemed interesting to surface some of that discussion here. With his permission, what follows is a longer verion of some of the points I posed in reply. Elimination vs. Scheduling: An Organisational Perspective There's no daylight between our positions on having less code: having and running less code is always ideal. While it may be hard to remove code, my view is that it is generally not much harder than re-ordering code. Why? The primary cost of both code removal and scheduling interventions is…