His IntelliSense-enforces-bottom-up-programming rant couldn't be more wrong these days. IntelliSense (plus refactoring suggestions) is perfectly happy for you

His IntelliSense-enforces-bottom-up-programming rant couldn't be more wrong these days. IntelliSense (plus refactoring suggestions) is perfectly happy for you to speculatively make a method call that doesn't exist and then to infer (and auto-implement) its definition based on the types of the parameters passed in the example call. I find meet-in-the-middle works quite well, starting with a top down outline of what I'm trying to accomplish combined with implementations of the design-critical algorithms that I know I need at the bottom, and having all of that come together in the middle. I find that the bridge rarely fails to join up correctly in the middle of the lake.