Pseudocode, what it means for me.

Pseudocode is defined as a notation resembling a simplified programming language, used in program design. Now is the hard part, the definition above is broad and lax in specifics.

Pseudocode is plain language describing steps in an algorithm, a system. I would even say in scripting it is the blueprint or story of what the code is going to do without the strict coding convention.

There are two camps when it comes to Pseudocode. The first is strict and borrow syntax, structure and conventions from other languages and this type of thought is needed when it comes some academic assessment. The second thought is it is simply a way to explain code and what it does or what you want it to do in a simple plain language not using any systematic standard. I am somewhere in the middle and do use some syntax mixed into my Pseudocode depending on the language I am writing for.

Here is an example of a stricter pseudocode for the C style:

Strict, follows some syntax

Here is a more laxed pseudocode:

Laxer pseudocode

As you can see there is a big difference in the two examples above. Neither is incorrect one follows more of the conventions of the language being programmed for, while the other is just in plain language. Flowcharts, drakon-charts and Unified Modeling Language (UML) charts can be thought of as a graphical alternative to pseudocode.

Pseudocode is a great way to get a problem solved and a project started. It is a great way to figure out how you want to tackle a problem before getting into the nitty gritty of coding. Make your story on the problem before you code!