Isn't the whole point of pseudocode that it's a language-agnostic description of an algorithm? Pseudocode written in the 1970s still stands up -- imagine if a COBOL block had been in its place.
Re:Reviewing the worst piece of code ever
by raverbashing on Monday August 03, 2020 @08:23AM
(#24036790)
Yes, and up to some point it's fine (like, giving an overall description of the algo)
But today it's more of a crutch than anything else, when you can have actual code running.
Re:Reviewing the worst piece of code ever
by dijksterhuis on Sunday August 02, 2020 @11:34AM
(#24029310)
Pseudocode is useful for academic papers to demonstrate an idea/algorithm in a condensed form - i.e. Without having to write out many detailed paragraphs.
Although I personally prefer a link to a public repo of code. But I'm a code monkey.
Where is the problem in putting pseudocode in a CS paper?
Why is this not surprising at all.
Oh I know, because people think it's "ok" to put CS papers with pseudocode out there.
At this point I'm not sure you can even blame the person if the interview process was so bad that it let a person like that get in.
(Yes please interviewers bore me with another long winded description of FizzBizz or somethng because you don't know how to ask constructive questions that show competency)