Programmers please discribe how you handle psuedocode in the real world?

Question

Firstly, how much do you use flowcharting vs psuedocode?

I assume you get a 'program requirements sheet' then you write your psuedocode and then you develop the code. Is this how it works?

How and where do you keep your code for future reference?

How important is the psuedocode?

Do you update the psuedocode so that it reflects any changes made to the program itself?

I am in programming classes in college and would like to get an accurate idea of what I can and should expect in regard to psuedocode. I have programmed for years but I rarely do any precode work so I need to learn new habits and I would like those habits to reflect real world practices.

I was considering hard copies of code in project folders along with corresponding documentation modules in Visual Studio 2005.

If there is a more common practice or things I should know, please tell me.

Thanks!

I do alot of psuedocode and am very good at it, I just want to know how employed programmers are 'required' to handle psuedocode. Or is psuedocode just something that programmers do to make life easy but employers dont care a whole lot about it???

Answer 1

employers could care less about pseudocode, they want completed, usable code. I personally rarely use pseudocode or flow charts. the only time i use them is if im not near the computer, and thought of a possible way to make a part of code work. even then, I usually remember it and dont bother to write it down. for flow charts, i only use them if someone gives me one (which never happens).

to answer your other questions:
yes, you are given program requirements, and objectives. from there, you just start writing code, building the basic shell, then working on each requirement (usually) one at a time.

i always create a new folder for every project. in each folder i have backup (older) versions, and the current version im working on. i tend to save all, even when the project is complete.

i personally dont think pseudocode is very important.

on the rare occasion i use pseudocode, i never update it to reflect changes. in fact, i usually just throw it out when im done.

Note: everyone is different, and writes code different but this how i work with regards to pseudocode.

Answer 2

Pseudocode is just code written in more easily understood terms, without all the syntax "markup" associated with real code. To me pseudocode is very important, I use it all the time, particularly when I've thought of a solution to a problem but I'm not at a computer - just grab a pen and paper and write pseudocode instead. There isn't any trick to it, or any "rules" to follow - just use what suits you :)

Rawlyn.