What language should I brush up on for a software engineering project?

November 12, 2026 4 answers
Asked by oops!another+tab

I have a group project course coming up, but I don't know what we'll build or which languages we'll use. I've studied some C++ and Java and will be learning Python soon. Is there one I should focus on, or a better way to prepare?

Answers

quite_the_opposite_

I'd hold off on picking a new language until you can get more details. The instructor or an old course syllabus may tell you whether the technology is assigned or whether each group gets to choose. A course taught in a particular language earlier in the program might continue with it, but that's not guaranteed.

Meanwhile, use whichever of C++, Java, or Python you're most comfortable with to build something small and complete. Reading, debugging, testing, and changing a working program will be useful even if the course uses a different language.

Reply to this answer
noted.with.sprinkles

For a big group project, I'd put Git near the top of the prep list. Practice making branches, committing changes, merging, and resolving a simple conflict. Knowing how to read someone else's code and explain your own changes will help too.

You don't need to be equally strong in all three languages before the course starts. Keep your strongest one reasonably fresh and follow along with Python as it's taught.

Reply to this answer
mildly-overcaffeinated

If the project turns out to be a web app, the concepts may matter more than guessing the language now. Get a basic picture of how a client talks to a server, what an API does, and how an application stores and retrieves data from a database.

A tiny app with one endpoint and some stored data would give you a chance to connect those pieces. You can pick a language you already know rather than learning a whole new stack just in case.

!no~assembly+required:

That prep is useful if it's a web project, but it could be a different kind of application. I'd treat it as an optional project until the course details are clearer.

Reply to this answer
MARGIN.note.9

Since you've covered language basics, try practicing the parts that come after writing the first version. Add a test, fix a bug without breaking the test, and write a short explanation of how to run the program. Those habits transfer across languages and are handy when several people share a codebase.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions