Does anyone actually do this?
I have never seen people write pseudo code as part of the programming process.
Diagrams, comments, tests, stubs sure, but never really pseudo code.
I have never seen people write pseudo code as part of the programming process.
Diagrams, comments, tests, stubs sure, but never really pseudo code.
I do it to structure my code, but I remove the comments as I implement it because I try to make it obvious in the code what's being done. You know, regular good programming, pick good names, keep the code reasonably short, add comments when needed, etc.
The same way you won't see the detailed outline of a writing once it has been written. Yet, the author likely started with an outline.
I mean if it's just a few lines, a change to existing code, etc, you can jump straight in with actual code.
But if it's a new object/module etc, start by writing some function names, and some rough structure within them, etc. All in IDE/editor. And I wouldn't call it pseudo-code, just a rough outline.
An outline is a very different beast compared to pseudo code.
It's effectively the difference between operational semantics and denotational semantics.
Hate to break it to you ... but those are all forms of pseudocode (or verification of your process (which is nearly the same thing)) :)