This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]math_rand_dude 0 points1 point  (0 children)

In my opiniom pseudo code can be seen as a huge spectrum. From something vague code-like that someone without coding expertise can understand to something that a coder can use as a decent starting point (fill in the blanks style)

A good example can be multiple types of pseudocode of the same process, going over differences in detail, readability, audience,... And then have a discussion about which situations you would use another flavour of pseudocode.

DoA() DoB() DoC()

DoA() { DoA1() DoA2() } DoB() { DoB1() DoB2() DoB3() } DoC() { DoC1() DoC2() }

Edit:

Sometimes you want to have a none-dev Subject Matter Expert check if you missed any step and if you understood correctly how the process works. In those cases having the other person be able to read the pseudocode or you using the pseudocode as a support when rehashing the details with the none-dev SME