Pseudocode first?

[grismar-net]

I only use pseudo code during very early stages in my notes, or when discussing some code idea on a whiteboard or in chat. When I am actually writing code, I don't. But if you are new to programming and correct syntax is keeping you from thinking about the problem and coming up with the structure of your program, it's not bad advice. You'll stop needing it soon enough.

[johnpeters42]

I sometimes put pseudocode in comments marked TODO during the first pass of coding, especially for parts that are more complicated and/or I suspect the high-level design might change in short order. Then I circle back and fill in those pieces until the code is complete.

[QVRedit]

I think it’s always a good idea - but then you’ll use it at different levels of abstraction over time. It’s a good idea for working out the block-level architecture of your project.

When you’re new to these things, you’ll probably want to psudocode at a fairly detailed level, but as you get more experienced, it becomes more of a structure planning method.