COMP1005: Fundamentals of Programming

Yes, the unit is difficult for those who have never done coding before. You essentially start from 0 and are expected to simulate a full 'game' or 'scenario' for your assessment. However, if you actually take the time to attend the Pracs, comp labs and make an effort to understand why the code language (Python) works that way, you will be fine. The problem with those that have previously taken this unit is using AI as shortcuts instead of trying to understand why the code is structured the way it is. Markers for assessments aren't looking for something crazy - they're just looking to know you understand what you're doing - which a lot of people don't take the time to learn. The Prac tests will help with the lead up to the assessment. I will say, the assessment is painfully difficult. There are a bunch of things you need to simulate through Python code which you have to write all on your own. Just know that it's not just the code being marked but a report about the code. - so it's okay if you're not 100% accurate with all the requirements for your simulation - the report can carry your assessment mark. [and ask for a lot of help from tutors in the comp labs] Final exam is similar to the practice ones - if you've been intentionally learning and trying to understand the code throughout semester, you will be fine. Yes the final exam is in-person and you have to write all the code down on paper to answer questions.

I loved this unit, granted learning a new language is not easy, the introduction to python was well structured and requires independent exploration and practice. The assignment was super fun and I highly rated the monty python references throughout. Easy to do well if you keep up with the content. Skills learnt from this unit apply to many areas of engineering and research moving forward. I used lots of the skills here in my internship at the Desert Fireball Networking processing and characterising light curve data.

This unit gets a lot of backlash in the Curtin student community, and while I don't outright disagree with it, I do think that it is made to seem more daunting than it actually is. For people without any prior coding skills or knowledge, some of the ideas presented might seem a bit abstract and difficult to remember, but this unit is most easily worked through by keeping up with the weekly practicals and asking questions. The unit itself is run...sub-par...but so long as you keep up you will do fine. The top mistake I see literally everyone make for this unit is waiting until 3 days before the final assignment is due before starting, thinking they can finish it in time. Do NOT underestimate how much time it will take from you. Start it as soon as it is released and keep chipping away at it. No one I know that has left it late has gotten a decent score in it.

The unit covers all the basics you need to know for programming in just about any STEM course, especially research. It will be harder for those who have never programmed before, but it is 100% possible to get through with a bit of extra effort. The assignment gets a lot of hate, as well as the unit in general, but I have found that the people who have this perspective have all left the 1-2 week long assignment until a few days before the due date. They also missed lectures, labs, etc. If you pay attention, keep up-to-date, and actually do the work, it's a pretty chill unit. The content is very transferrable to other languages as well.

Extremely difficult unit for non-computing students to take. The unit covers basic Python programming, charting, and data analysis. The mid-semester assignment is HUGE, and always too difficult (on purpose). Tutors are quite useless, and Valorie does not respond to her emails. Best way to learn this unit is through self-study (practice, YouTube, etc). Do not use AI for assignments, they will catch you. All assignments must be demo'd in front of a tutor, and you must explain how your program works.