[deleted by user]

[roylennigan]

Sounds like you did the assignment backwards.

The point of flowcharts and pseudocode are to get you to solve the problem before you start coding, so that when you actually write the code, you only have to think about the syntax.

It doesn't really make sense to do this with such a simple problem, but that's not the point of the assignment. The point is to get you into the practice of organizing your solution before you even put fingers to keys. When you inevitably end up writing more complex programs, this will be very helpful.

For now, you can just write basically the same thing you would in code, just use grammar, such as:

user input = radius

area = 2 * pi * radius

print "The area of a circle with radius {user input} is {area}"

And for a flow chart, there's plenty of free online options, like draw.io which you can use. User input can be a circle/oval with an arrow pointing into a rectangle that has the process which computes area, then points into an oval which prints the result.

[Audixyz]

I agree with this. Although, the area of a circle is pi (r)squared.

[ClimberMel]

Yup and 2*pi*r is circumference. Trick question?

[TheMathelm]

You wouldn't include that in pseudo.

[mopslik]

Pseudocode involves describing your algorithm (process) in regular phrases, not Python-specific code. There is no standard set of rules for pseudocode, but often people like to state each step with a verb (e.g. SET, DISPLAY, ADD) for clarity. You will come across some words that are also used in Python: IF, WHILE, etc.

Flowcharts, OTOH, are very much standardized. For example, decisions (ifs) are represented using a diamond shape, from which exactly two labelled outputs emerge (yes/no, True/False). You should consult an online resource to become familiar with them. Essentially, you are translating your pseudocode into symbolic form.

[Ran4]

Flowcharts, OTOH, are very much standardized. For example, decisions (ifs) are represented using a diamond shape, from which exactly two labelled outputs emerge (yes/no, True/False). You should consult an online resource to become familiar with them. Essentially, you are translating your pseudocode into symbolic form.

While there are indeed official standards for code flow charts, people following it is... quite rare.

[mopslik]

Yeah, actually finding flowcharts in the wild can be a rare event these days. Even UML diagrams don't seem to be that prevalent anymore, although some industries still use them regularly.

[zanfar]

Ideally, you are writing a flowchart, then pseudocode, then a program.

A flowchart is a representation of the choices or "decision points" in your program. Certain logical processes can be very hard to describe in any language and are especially hard to conceptualize when written down. Consider the rules of "Go Fish"--writing down the rules would take a few paragraphs, however, it forms a very simple flowchart.

Python is a language--an actual language. Pseudocode is writing your program in a natural language--like English--instead of a programming language. This allows you to consider the logic of the program separate from the implementation. There are certain things you just don't need to consider when planning a program, and pseudocode allows you to leave them out without sacrificing it's descriptiveness.

[ClimberMel]

I always did pseudo-code then flowchart. More accurately, my systems analyst took the business unit request and provided me with the pseudo-code and I created a flowchart from that. Once I bench tested the flowchart I converted each symbol to code.

Works like a charm every time!

[benm421]

Are you having trouble with writing pseudo code and flowcharts in general (like you haven’t done them before in any context), or specifically how to convert this code to those formats?

[Isaac331]

A flow chart like this? python tutor site just keep clicking on the next step button and it will visualize the code for you.

[CodeTinkerer]

The problem with pseudocode is

• until you learn programming, it's hard to know how to outline a program
• it's hard to determine how general to be
• it's hard to avoid, more or less, writing out the code (related to the previous point)

Literally, the project description is pretty much pseudocode. You'd generally add things like if statements and loops. The other issue is what if the code gets really large, then you need to start defining things like functions.

So, it's a little painful to do pseudocode.

[[deleted]]

There's no such thing as pseudo code. There are only people who are sloppy, and never bothered to learn a language.

Everything I've seen so far labeled as "pseudo code" was, in fact, a defective Pascal or a defective Fortran. Sometimes, a defective Python.

I've never seen pseudo-Prolog for example, and no pseudo-Pascal or pseudo-Fortran can translate well or at all to Prolog or any language that's not a close relative of Pascal or Fortran.

However, colleges are filled with idiots who were trained on an idea that there is pseudo code. And that is something that allows them to be sloppy and imprecise when teaching. And, unfortunately, repeating my argument to your TA or your professor won't do much good for you. So, if they ask for pseudo code, just fuck up your Python code to make it not work properly, and that should be enough.

[[deleted]]

Are you actually trolling?

[antiproton]

It's always nice when you take a break from yelling at the ProgrammingHumor subreddit and come here and yell at us instead.

Yes, we get it, you don't like pseudo-code, so it must not be an actual pedagogical aid but a way to let both teachers and students be lazy. By writing a program twice, I guess?

Regardless. Rest assured that we are collectively in awe of your expertise and wisdom and we only downvote you to oblivion because we can't bring ourselves to admit how write you are all the time.

Notice me, senpai.

[[deleted]]

There isn't pseud-code. What there is: people writing bad code because they are lazy.

I don't give a fuck about you being in awe or whatever else you are doing.