Who do pseudocode here?
Pseudocode is my arch enemy. **HATE**
Printable View
Who do pseudocode here?
Pseudocode is my arch enemy. **HATE**
You, sir, are an idiot. Actually, forget I called you sir. Pseudo code is a great tool used by pros and newbs alike - its the best thing to plan out pieces of code. Whats wrong with it??
no, it is too... much work.
Psuedo code kicks ACE mofo.
I personally hate to code, I wanna spend as little time writing code as I have to - I just want the end product. Psuedo code allows me to put Pen to paper and plan out my Objects, functions, design of program, and the goal and flow of the functions. I can then sit down and BUST out my program with little time wasted, all I have to do is find the particular STD lib fxn that I need to accomplish this step.
Ppl who don't like psuedo-code don't speak good engrish.
> Ppl who don't like psuedo-code don't speak good engrish.
w3rd.
Pseudo-code's the best thing since sliced bread. I dare you to make a big project without any kind of pseudo-code, flow charts, or anything else.
Every single thing I write goes thru the design phase. Part of that design phase is always writing pseudocode. I could not live without it. Pretty much all of the professional coders I know do a similar thing.
>Who do pseudocode here?
I do, but I don't use pseudo-code a lot, I prefer using diagrams (flow charts and other kinds of diagrams) since it gives me a better overview of the design.
Though pseudo-code is very useful when making a detailed design of an algorithm, because you can use your natural language to describe the algorithm instead of using the programming language.
Pseudocode saves you from having to use flowcharts, I'd say that's enough reason to use it.
-Prelude
>Pseudocode saves you from having to use flowcharts,
Then how do you get an overview of your software? I prefer diagrams, to get/create an overview of the code. But maybe it's because I have an electronics background that I prefer diagrams. ;)
And wasting hour upon hour trying to track down a bug that could have been avoided by proper pre-code planning is not too much work?Quote:
Originally posted by Wraith_Master
no, it is too... much work.
:eek:
Depending on what the particular problem is I use both flow charts and pseudo code. Usually when dealing with a large problem I flow chart it. Then as the large problem is whittled down into the individual smaller problems I may (depending on the complexity of the problem) use psuedo code to work out the smaller problems.
I think Wraith_Master is coming from the perspective of a school teacher going over pseudocode. I remember when it was taught to me in school and the teacher treated pseudocode as if it needed to have a strict syntax. I rembember serious frustration when being marked off for not following the proper pseudocode structure.
Pseudocode is you're note taking and planning. There isn't a strict syntax it just needs to be readable and understandable. You wouldn't start building a house without first drawing a blueprint would you?
I use it all the time, especially when the code gets a little tricky. It helps to write out what you want to accomplish it just words and then turn that into code.
I was never really taught how to do it, are there any standards for it?
it's pretty much an a "whatever works for you" basis.
I love to use UML to model my programs before i program them.. i'm a student of OOD so i'm mainly concentrating on effective design now instead of speedy implementation.
>>I dare you to make a big project without any kind of pseudo-code, flow charts, or anything else.
how's 20+ pages of source without pseudocode? i never use it, i get down to it and start cranking out code. I start with a basic construct of a program, then work into the logic, then memory, then add glamour.
Whether you use pseudocode really has to do with how you think, i've played chess for years, ever since i could talk. I think that's made me code the way i do. I can think and code at the same time...sometime throwing typing in there at the same time has some weird outcomes lol, i've been known to IM semicolons to my friends quite often.
That won't work too well in a business environment, at least not in the one I work in. There are other people to consider, who will want to know how you plan to write your code up front. No point in spending hours writing code, when someone in your team takes one look at it and says "that'll never fit in with what everyone else is doing because....". It's about teamwork ;)Quote:
Originally posted by Waldo2k2
how's 20+ pages of source without pseudocode?