I’ve never been a fan because writing some simplified Python seems better. Or even better, writing Python that doesn’t necessarily follow every syntax rule to a T and takes liberties where necessary to improve readability
It probably depends on when you were taught to code, and what language you learned on/most familiar with.
This is exactly how I learned to write psudo code in the 80’s… We were also diagramming our code back then, with a pencil and paper, using a template. https://www.ebay.com/itm/294862492558
Kind of like with this thing.
Now I usually do a bit of a hybrid, but it also depends on how complicated the programs are. I’ll do some python/comment-psudo-code.
It doesn’t really matter what the process is, as long as it works for you, and doesn’t interfere with collaborating with anyone you work with.
I started doing exactly this. Write a bunch of functions, that may end up in different systems, on different machines, even. This allows you to define the interfaces, figure out data dependencies, and so on.
The code may be runnable, just printing out some statements. Then I copy blocks of it to the place where it will belong.
The paper doesn’t use psuedocode as I know it. In my experience pseudocode looks much more similar to real code. (According to Wikipedia I’m more used to mathematical pseudocode)
I’ve never been a fan because writing some simplified Python seems better. Or even better, writing Python that doesn’t necessarily follow every syntax rule to a T and takes liberties where necessary to improve readability
It probably depends on when you were taught to code, and what language you learned on/most familiar with.
This is exactly how I learned to write psudo code in the 80’s… We were also diagramming our code back then, with a pencil and paper, using a template.
https://www.ebay.com/itm/294862492558
Kind of like with this thing.
Now I usually do a bit of a hybrid, but it also depends on how complicated the programs are. I’ll do some python/comment-psudo-code.
It doesn’t really matter what the process is, as long as it works for you, and doesn’t interfere with collaborating with anyone you work with.
I definitely write pseudocode like this, albeit perhaps with some more shorthand. It’s commonly taught this way too.
I started doing exactly this. Write a bunch of functions, that may end up in different systems, on different machines, even. This allows you to define the interfaces, figure out data dependencies, and so on.
The code may be runnable, just printing out some statements. Then I copy blocks of it to the place where it will belong.
It’s more of a thinking tool, than “actual code”.
I agree. Instead of pseudocode, using a simple language like Python that is pretty understandable seems to be a better way of representing your idea.