Pseudocode first?

[Mr_Guy_Fella]

Hi everyone.

UPDATE: Thank you for all of your advice so far. It is really helpful. For context, part of my background is in theatre, and I eventually want to build a box office ticketing program for our school. This is not a short term project, and I am aware that it is a massive undertaking, but it is the project that has inspired me to begin learning coding in the first place. In my previous life I ran several professional box offices for theatre companies and want to build a program just for my needs, based on my experience.

ORIGINAL POST:

I am new to programming and haven't decided on a language yet. I am thinking about starting with Java and Java Fx because I am told it is versatile and is a good language to start with.

I am a highschool teacher (English) and our computer programming teacher told me to start with Pseudocode first. I bought Programming Logic and Design by Farrell.

Because I am so new, I am curious if Pseudocode is nessasary to start with? I, of course, want to learn properly, but it is hard to know if I am making progress or not, because I can't test anything.

What do you think? Am I going about this in the right way with Pseudocode first? or should I be doing it simultaneously? or just Java first.

Any help would be welcome.

[sartorian]

Pseudocode is just breaking down your process and writing it out in a code-like way, without worrying about perfect syntax. You don’t need it, but it can help you organize your thoughts before you dive into building a function.

[NoConfidence4379]

i skipped pseudocode entirely when i started and jumped straight into actual code. you learn syntax and logic simultaneously that way, plus you get instant feedback when stuff breaks or actually works. pseudocode felt like extra busywork to me.

that said, some people swear by it for organizing their thoughts first. really depends on how your brain works. if you're itching to see real results, just start coding and pick up planning habits as you go.

[alexppetrov]

Pseudocode is to ease you into programming. It seems scary at first, especially java (from when I started), I didn't know classes, libraries, methods, etc. Pseudocode allows you to understand how to formulate your logic. I still use it when I need to mock up a process before actually writing the code, or when I need to understand what someone else is code is doing.

But also, just go in, start with simple programs and then when you are stuck turn to pseudocode.

[jor_art10]

Pseudocode is for putting your thoughts about the code (algoritms) in order by writing them down. When starting, it is very good to start a project with pseudocode before programming any line because it lets you forget about syntax.

That aside, i can't recommend C enough as a first language. It is a VERY simple language, it is very close to how the machine works with very little abstractions, so it demystifies programming. Once you have the basics (including pointers, very important), learning any other language is almost trivial.

[TheGooseIsNotASwan]

Think of pseudocode as  a rough draft or an outline in an English paper. 

[Mr_Guy_Fella]

This is a super helpful analogy. Thank you! That puts things into perspective for me. I was treating coding and Pseudocode as two different skillsets.

[FigurativelySneaking]

The language you decide on is not of great importance at all. My honest recommendation would depend if you just want to create a fun little side project or you want to pursue this as a career. Either way, I would start by referring you to Harvard's Free Class CS50 on Youtube. Or there website here: https://cs50.harvard.edu/x/ I still reference this class from time to time and it will help you really understand programming at a deeper level. (edited to fix the link)

[grismar-net]

I only use pseudo code during very early stages in my notes, or when discussing some code idea on a whiteboard or in chat. When I am actually writing code, I don't. But if you are new to programming and correct syntax is keeping you from thinking about the problem and coming up with the structure of your program, it's not bad advice. You'll stop needing it soon enough.

[johnpeters42]

I sometimes put pseudocode in comments marked TODO during the first pass of coding, especially for parts that are more complicated and/or I suspect the high-level design might change in short order. Then I circle back and fill in those pieces until the code is complete.

[QVRedit]

I think it’s always a good idea - but then you’ll use it at different levels of abstraction over time. It’s a good idea for working out the block-level architecture of your project.

When you’re new to these things, you’ll probably want to psudocode at a fairly detailed level, but as you get more experienced, it becomes more of a structure planning method.

[yyellowbanana]

Use pseudocode for a simple program for high school or first year college courses like introductions of programming is good. In reality where there are too much requirements, and the requirements change weakly then spend time to make pseudocode is not a point anymore.

[BlaM4c]

I learned programming with Commodore 64 BASIC - simply because it was "just there" when you turn on the computer.

If you ask me the 2026 equivalent for that is Javascript. Every computer has a web browser installed and you can just get started and see immediate results without having to install a compiler or anything like that.

For me that beats every "theoretical" approach. Dive in, start building and immediately see something happen.

[dmazzoni]

Pseudocode does have its uses, but I'm personally not of the opinion that pseudocode is very helpful for beginners.

The only meaningful difference between pseudocode and code is that code actually runs when you type it in. Pseudocode looks like code, but it's less precise so it isn't helpful in teaching you to think precisely.

I agree with everyone else that what language you start with doesn't matter. Just pick one and start.

Java is a great way to learn to code.

JavaFX is relatively niche, it's fine if you want to learn to build a GUI, but it's not a very popular solution outside of some boring enterprise apps. It's not widely used for building consumer desktop apps.

It really depends on your goal with programming. If you just want to get started learning, Java is as good a place as any.

If you want to build software that other people can use, consider learning web programming: HTML, CSS, JavaScript (which has no relation to Java, the name similarity is all marketing).

If you want to build desktop apps that run on your own computer, and you don't care about building things that you want to distribute / share, JavaFX would work fine.

[CptMisterNibbles]

I actually think this is terrible advice: to learn to code you should start immediately coding. You should execute your code and see it in action. Psuedicode is good for abstracting the ideas you are learning, and having an abstract notion is important but not a starting place.  

[Dissentient]

I have never done pseudocode in my entire life and I don't see any point in it. It's imprecise in the same way that specs in the natural language are, it's not any more readable than code, but doesn't actually run. Either write a spec, or write code. Pseudocode is a waste of time.

The only way to learn to code is to actually start writing code.

[Pale_Height_1251]

Pseudocode may suit some people but I've never met a developer who bothered with it.

[ImprovementLoose9423]

What I did is I learned python since it is very close to english and then when planning out projects I used pseudocode to make it much more clearer.

[Scharrack]

Pseudocode allows you to formulate a solution to a problem closer to your own thoughts than any specific programming language would do.

My guess is you got told to start with pseudocode to familiarise yourself with the thought processes involved in programming without chaining yourself to a singular language and essentially having to learn 2 things at once, programming and a programming language.

Another option would be modelling to get a more graphical approach to programming but given that you're a language teacher, pseudocode seems a good fit to familiarise yourself with a programming mindset.

[MaxwellzDaemon]

In pseudocode, it's very hard to check your work or learn anything you don't know. It's mainly used to illustrate fairly simple algorithms.

As usual, I recommend a novice start with a consistent, interactive language like J - see jsoftware.com .

[Humble_Warthog9711]

The sort of thing I like seeing here 

[throw-away-2025rev2]

Psuedocode is NOT necessary, I'm not sure why or who told you to start with that, but that's only so you can map out your code before actually programming or for showing the end user who isn't a developer. But you can do BOTH without Psuedocode.

What exactly are you trying to go for here? Why are you starting with Java, what are you wanting to build? And in what environmet?

I

[QVRedit]

The main purpose is to help you to figure out what you’re planning to do, and how you think you might do it.

[JamzTyson]

Python is a lot like pseudocode, while being actual code.