Great job on finishing COMP1531 for T1! I want to first congratulate our top 5 achieving students. In order, they are: Miloris Xu, Lachlan Scott, Kyle Phabmixay, Carl Buchanan, Nikki Fang. Congratulations!!
For those who have emailed me in the last 24 hours, I will get back to you in the next day or two. If I don't get back to you by Sunday night then I have accidentally lost an email. But I will get back to you :) There are just a few things I have to do in order to get back to you.
Thanks so much for the positive and less-positive feedback that people shared. Some of you really put a huge smile on your tutors' face when they read it. And for the improvement feedback, it's really good to understand you all and how you felt about the course.
I wanted to take a moment to share some information on things that we are going to be taking onboard (because I want you to know we're both listening and always trying to improve), and then I just want to address some feedback that is maybe more complicated to address, and just give some background on it.
One thing I wanted to address first is a piece of feedback "Learning python in this course is too much work" . Now I firstly want to say that I generally agree with you and have made that clear. In fact, the people who lead education in CSE also agree with me, and we've both agreed that the school would benefit from another course that actually teaches something like Python + a lot more. I wish we didn't teach python in COMP1531, however, even if it feels a little burdensome, without an extra course, COMP1531 is the most efficient place to teach it. We also work around this by making things like the project & labs much less hard than they would be in a course where we assume you know Python. So is it ideal? Maybe not. Is it manageable? Absolutely. And we'll be going forward for the short term future focusing not on "cutting things out", but rather by asking the question "How can we help you more?". Some of the points below address this - because the tutors & I have a huge interest in making things easier for you, without removing what is really quite a lot of core content we wouldn't want to skip over!
Some of the things below are direct quotes, others are paraphrased.
I''m not really sure what you're referring to here, so please feel free to email me to explain :)
Overall it was such a pleasure to have you all this term. I really can't describe the excitement and fun that I experience watching you all go from programmers to the beginning of software engineers - and seeing all the skills that people collect along the way.
Go find me and add me on LinkedIn so we can stay in touch :) Genuinely, I always miss each cohort of this course - and all of you will be no exception!
I'll see you all around.
Today we have released a number of marks, including your overall class mark, your final participation mark, your iteration 3 marks, and your overall project mark.
These are in your grades section :
If there has been a mistake with your
, please email your lab assistant.
If there has been a mistake with your
iteration3, project, or participation marks
, please email your tutor.
Some updates for you mid-week 10 :) Short story is that people overall did really well in iteration 3 automarking.
33% of people have completed MyExperience for COMP1531 already! That's amazing - you've done better than any cohort I've ever taught. But there are still two thirds of people who haven't filled it out. Please fill it out sometime in this next week! :)
Please complete your final peer review on Moodle now. Once you log into Moodle and go to COMP1531, click on End-of term Peer Review (COMPULSORY). This must be completed by Monday 26th of April at 12pm. Failure to complete the peer review may result in penalties to your marks.
Iteration 3 automarking is complete, and we've released the marks! YOU CAN FIND MORE INFORMATION HERE .
Please note that for fixes to improve your iteration 3 automark, we will generally be less lenient, and fixes are to be sent to firstname.lastname@example.org instead of your tutor (more instructions in the link above).
Overall the marks were genuinely quite impressive - a tonne of groups improved between iteration 2 and iteration 3 and I think many of you should be absolutely proud of yourselves. Great work.
Your tutors are obviously marking iteration 3 right now, and will need a week to consolidate marks. You will get an update at the
of week 11 (another notice) with info about the iteration 3 manual marks as well as your final and overall project mark.
Please note that Lab10 is due on SUNDAY 5PM THIS WEEK . This is earlier than the usual time. UNSW does not like things being due in week 11. In fact, technically I shouldn't be allowed to make it due after this Friday. However, I'm sure most of you would appreciate the extra two days. But just be cautious that it's due on Sunday @ 5pm .
Please take the time to read this. If you read it to the bottom you'll find two extensions.
What a week! Feels like we're hitting the business end of term and everyone is certainly under the pump. Not long to go until your major COMP1531 assessments are all finished and complete. Myself & some tutors will support you through the next days to get everything together.
While things have overall run pretty smoothly the last couple of weeks, I'd also like to thank everyone for being patient amidst the odd little hiccup that some of you have encountered. Whenever we run into little issues we do our best to compensate for things wherever possible :) And honestly, having an engaged and mature group of students like yourself helps a tonne.
If you've checked your Inbox, you will have seen an email from Andrew Taylor about some account issues. A very small number of CSE students experienced a large issue in the last 24 hours where their account files went missing on VLAB. In some of these cases, they can be restored, and in some rare cases, they haven't been.
If you experience any major file losses you can always email email@example.com AFTER you've completed the steps above. Remember that I cannot fix any of your file issues!! (I wish I could).
Because of this there are some minor extensions
. Sadly, we can't extend anything any later than Tuesday 1pm in week 10 because that's when your classes are! :( But that's OK, the impacts were quite small and because many of you work in groups if you have some file losses in one afternoon your group can help make up the difference :)
MyExperience is now ready to be completed! I will send you a couple of reminders over the next week or two :) Some comments I'll make are: Please distinguish between myself & the course when providing feedback. Don't be negative about the course if your issue is with my teaching style, and don't be negative about my teaching style if your issue is with the course. I really do read the comments and feedback so don't feel it's wasted effort!
Due to the CSE account issues people were facing, I am
extending the due date of all lab09 activities from Monday @ 10am to Tuesday @ 1pm (27 hour extension).
This has been reflected on the lab page .
A reminder that:
Your iteration2_manual mark (/50) is now available on the grades page .
If you want to discuss this with your tutor, chat about it with them in your last project check-in next week (though in general, most of you should have already gotten feedback from them!).
If your mark is ~0, it's likely an input error from the tutor so just email them :)
we will have re-run the
tests for your iteration 2. When we release these
I will update the text at the top of this page to specify when the latest update was
Largely speaking, the iteration 2 course server & course tests were fairly accurate. However, students have pointed out a couple of issues with our testing and our server (pertaining to owner permissions, stats calls, logout returns). We've fixed some tests/features and removed some others.
If your NEW mark is LOWER (for god knows what reason) than your current mark, we will not reduce your mark. In most cases student's marks will stay in the same, and in some cases this may improve it. It will only improve if your marks were.
Another key update: For students that made the mistake of NOT using `request.args.get()` for GET requests, we have established a course wide penalty of only 10% of the automarks (rather than 33%!)
Because of the CSE issues, we are extending the iteration 3 due date back 3 hours so that the new due date is Tuesday April 20th @ 1pm .
Iteration 3 has had very few changes to the spec (woohoo!), however, there is one subtle and critical change we had to push yesterday - please check out your merge requests.
"16/04: Removed duplicates of
data type. To be clear, in iteration 2
has had properties
added to it, and
has had properties
added to it."
I am confident that many of you noticed this duplication in the data types table and didn't have any issue - though for those that didn't or are confused, you will want to make the small and necessary changes to add those extra elements.
See you next week :)
Congrats to people for making it through iteration 2 last week! Only 2 more weeks to go! And in less than 2 weeks you'll have basically finished 70% of your coursework. COMP1531 can feel a little bit heavy at times, but thankfully that makes the tail end of the course a little bit lighter.
There appears to have been some confusion about whether getting your backend working with the frontend was required for iteration 2. The simple truth is - we originally planned to have it required for iteration 2, but it wasn't communicated well enough to you in the specification and in lectures.
For this reason, whether or not you got it working for iteration 2 will have no impact on your iteration 2 mark.
For those who did invest the time getting it working, don't fret! That's just less time you'll have to spend on it now :)
The original front-end bonus lecture was meant to happen on Tuesday afternoon in week 8 - but only 2 people turned up! So I have instead reschedule the lecture to be for the hour before the Monday lecture. The new bonus lecture time is:
See you on Monday!!
Very straightforward updates this week! The main one is
good luck with your iteration 2 due on Tuesday morning
. It's due right before the lecture, so looking forward to seeing your tired faces :)
I know that some of you might be feeling stressed around this time of term, but rest assured whichever way the dice roles for you in the coming weeks you'll figure things out. You'd be amazed how many times in your life the feeling of impending doom are just feelings that fade away after a few months.
A big thanks to your tutors for always being so caring and supportive of you. I genuinely think we have great staff in this course.
Because of the public holiday, the Monday lecture will now be done at Tuesday 4pm-6pm (Week 8) . This lecture will be a bonus (non-compulsory) lecture on the very basics of front-end web development. This content will have NO bearing on the course, so you should feel absolutely free to skip it. We include it in the course because students request wanting to learn the content :)
To confirm, that means on Tuesday there will be two live streams for week 8:
It is absolutely going to be recorded, so the majority of you will just end up watching the recording.
Happy Easter. I know you have an iteration due on Tuesday, though I do hope if nothing else you've managed to spend a short moment with people you care about and take a breath. Always look after yourselves.
See you on Tuesday!!
Really short notice this week, since the last week was flex week! I hope you all had at least one day to recharge. And for those who've had a horrible week, the teaching staff & myself will do our best to help make these last 4 weeks of term as manageable as possible.
Try and work hard on your project this week!! We've made iteration 2 due a week later than previous terms, which while mostly good, will have the downside this term of being due immediately after a long weekend. The more work you get done this week, the less you'll have to do on the weekend. Not to mention, it can be
hard to coordinate people over a long weekend.
To take the load off in week 7, remember that this week:
This teaching structure is a strategy to give everyone an extended chance to catch their breath and manage their workloads.
COMP1010 is running an experiment to see if people can distinguish genuine between Elon Musk tweets and naively generated fake tweets. See if you can tell the difference.
subscribe to my youtube channel
if you want to be notified ASAP when new lectures are uploaded.
I'll see you tomorrow!
I hope you have an amazing flex week. Whether you're doubling down on university, or kicking back and enjoying some down-time, I wish you well! I have a fun flex week suggestion for you: Sleep!
Also, I believe CSE is undergoing some software maintenance from Fri 26th March (evening) to Sat 27th March (evening). So be aware you may not have access to a large number of CSE systems during that time - and plan around that. It will not be grounds for special consideration.
subscribe to my youtube channel
if you want to be notified ASAP when new lectures are uploaded.
I'll see you in week 7!
We have released:
Many classes struggled with the time constraints during the marking of lab02 questions. We've made two adjustments going forward from lab05 (as others have been released) that will help:
Yes, marking might feel a bit time constrained in COMP1531 compared to other courses. We could always remove project check-ins and have the tutor marking too - though we genuinely feel (and have seen from experience) that using time to mentor students about their projects leads to better overall learning outcomes then putting more time into marking a series of small lab activities.
Also, your tutors keep telling me how great you all are!
We have released:
Help sessions started in week 2 and will continue in week 3.
There was some miss-communication between myself and tutors that meant that Hopper (queue manager) wasn't used in some help sessions in week 2, which meant some students weren't sure when they were going to get help. This has been fixed up for week 3, so help sessions should run more smoothly for some of you.
Some students have messaged me saying that they want
per help session. We can do that, though it means that there would be fewer help sessions overall, and my experience is students would prefer better distributed help sessions.
There were some students confused about the lab marking this week, so I thought I would just re-iterate how the system works.
Every week, you have a handful of lab exercises (separate repositories) that you can complete. Each exercise is worth some
X number of points
For any given week, there is a specified number of points (in the lab README.md) that you need to reach (from completing specific exercises) to get the full 2/2 marks for a given week of labs. What this means is that you don't have to complete every exercise to get the full 2/2 in a given week.
This system is setup to give YOU a choice about what activities or exercises you think are best to spend your time on.
Congrats to everyone for making a big effort on iteration 1 this week. With a bit over 1 week until the first iteration is due, try and make the most of this week. I know that some of you are going to be feeling slightly confused or overwhelmed by some aspects. That's OK! It's designed to have a bit of a steep learning curve - so use your project check-ins and other team members to work through problems this week. Your tutors are here to help!
I will pass on a few critical hints, though:
Don't stress if you don't get everything perfect - the point of these assignments is to make mistakes and learn from them :)
I hope you've had a great week meeting your tutors and classmates. I've been talking to so many of your tutors and they've all been thrilled to have the chance to get to chat to you this week. It was also great to meet 200~ of you in the lectures on Monday/Tuesday. Here are some updates!
This week, some students felt a little bit overwhelmed by the tools or environments they had to familiarise themselves with. For this struggling with this even at the end of the first week, we've added a guide that should help put information people need about getting started in one place . It is also linked in the sidebar.
This week your tutors confirmed your project groups with you in your tutorials. After some further adjustments and late enrollments from me this evening, the groups seem relatively stable at the moment.
As of Saturday morning, our systems should have added everyone to their correct gitlab group repositories. You can find your group repository (if you haven't already) on the homepage of gitlab.cse.unsw.edu.au. Your MS teams chats should be mostly fine, though your tutor will help stabilise that between now and the end of your class in week 2.
If you are uncertain what group you are in as of Saturday morning (today), you are able to check on
. If anything seems wildly wrong to you please email me on firstname.lastname@example.org.
There may continue to be slight changes over the coming weeks as students continue to drop the course before census date, but this usually has any material impact on less than 5% of groups. Your tutors will always support you.
Have a great weekend everyone, I hope you have at least one fun adventure. Sometimes on Sundays I like to find any random green-looking space on a map of Sydney (that I haven't been to) and just go work there for a couple of hours. Never stop exploring!
Welcome to COMP1531 21T1 :) The fundamental aim of COMP1531 is help you on your transition from being a solo programmer into being a collaborative software engineer . We have a teaching staff team of about 36 (including myself) and we're all super excited to get to know you. The term will be over in a flash but we're here to help you through it.
If you don't lack the time or attention span right now, let me give you the most important things:
I would encourage you all to take a moment to read the
, because it highlights virtually everything. I will also go through this a little bit on Monday.
In terms of assessment, the course has 3 major components:
A reminder that preferences for major project groups will close at 5pm today. You can fill out THIS FORM to preference to be in groups with other people. If you'd like to get to know other students in the course (either generally, or to find like-minded people in your tutorial), you can join the CSESoc Discord Server via this link .
Later tonight I'll be finalising the groups, and then early next week you'll have a Microsoft Teams group created for your team (we will talk more about this in week 1). So if you haven't already, would suggest downloading or logging in to Microsoft Teams so that when your group is created you can say to your group members and
For other questions about your group, we will talk about this in lectures and tutorials this week.
Please remember - it's extremely normal to be slotted into groups with people you don't know, and things have a very high chance of going fine. And for those that inevitably have some difficulties with groupwork, we've spent a lot of time structuring and designing 1531 to be both supportive and fair.
To those studying remotely or trapped overseas, our aim is to make sure you feel no less connected and involved with things.
I'll see you all on Monday :)
I will spare you my more formal welcome and information for later in the week - for now I am hoping to leave you mostly alone to enjoy your last week of holidays :)
We do need to talk about one thing early, though...
As specified in the course outline , COMP1531 has a major project component that is a 4-5 person 9 week group project that constitutes 50% of the course.
It's a requirement that your group will consist of only people enrolled in your tute-lab (yes, as in you are all enrolled in the same class on MyUNSW).
Because we understand many people do this course with friends or colleagues they know, we want to give you an opportunity to
who you want to be in a group with.
To do that,
please fill out this form for each person you want to preference
. You must make the preference by
Saturday 13th February @ 5pm
. We sadly aren't in a position to accept late preferences. Preferences are not guarantees that you will be in a group with those people.
If you don't have anyone to preference, don't even worry! That's very normal. You'll hear murmurs in the CSE community that you're going to end up with a "horror group" for COMP1531. I can assure you that while groups that struggle do exist, they only make up between 5-15% of groups from what we've seen. If you can function effectively with a group of strangers, that's actually relatively normal . We have structured the course very intentionally to have processes in place to ensure that if you work hard and follow the rules that your input should reflect your mark even if you end up with a struggling group.
I'll email you all later in the week :) You can also
pop on the forum
and say hi too, if you want. Until then, enjoy your week!