I am very bad at planning and visualizing what a program should look before I start writing it. I'm sure a lot of other developers are in that boat as well. I'd even venture to say that (almost?) all developers have a hard time doing that even if they think they understand the problem. Well, that's probably actually the root of the issue. Without writing or tackling them, it's hard to understand problems. You can only reach so far by thinking very hard in isolation. In my case the only real way ...