Kinda along those lines. What works best for me is to start with high level comments in plain English after thinking about what I'm trying to achieve for a bit.

Kinda along those lines. What works best for me is to start with high level comments in plain English after thinking about what I'm trying to achieve for a bit. Then I make a skeleton of all the methods and classes that that will require. Then I'll comment each method (if not trivial) in plain English and only then actually begin development. The development phase seems to go by pretty quickly that way. And as another plus, that makes my code very readable for others. I leave the comments in.