I occasionally use them. But to call them "flowcharts" would be to use the term liberally.

If the project is not entirely obvious I usually find myself writing down the "blocks" or modules that I'm going to have to write. These often end up being subroutines. I find that once I've identified the blocks many programs--even complicated ones--become very obvious. The trick is just breaking down the process into its component parts which, as I said, usually become subroutines. Then it's a matter of calling them in an order that is usually pretty obvious.

That said, I am not much of a "visual" person. I need to do something to learn it and I need to go through the process in my head to figure out where the problems are going to be. Generally speaking, a visual representation in the form of a flowchart just makes things look more complicated to me.

But that's just me...

Regards,
Craig Steiner