SOFT6008 Attendance Week 06

Attendance for Week 06 was 45%

SOFT6008 Class 06.2 & 06.3 B

Students worked on coding checksum calculations for the assignment

SOFT6008 Class 06.4

We looked at different ways to code the Luhn algorithm.

We looked at EAN, ISBN, and PPSN algorithms

Audio: SOFT6008-06-4-20151021.mp3

SOFT6008 Assessment 1 Results

The results of assessment 1 are here sorted by the last 4 digits of your ID number.

I was disappointed by the results. A number of students have not yet mastered be very basics.  These students need to go back to the very start of the course and work forwards from there.

SOFT6008 Class 06.3 A

Students worked on coding the checksums.

Only three students came to class

SOFT6008 Class 06.2 & 06.3

Students worked on coding checksum validations.  Most are still working on the credit card. We will look at that in the lecture today.

SOFT6008 Class 06.1 W

Students worked on coding the credit card checksum.  Many students are weak programmers and are struggling with the logic.

SOFT6008 Class 06.1 B

Students worked on coding various checksums.

Attendance was poor

SOFT6007 Class 06.1

We looked at how to do a three column layout in CSS.

It was very slow because the machine in the room was not cooperating. I will go over it again in the labs.

SOFT6008 Class 06.1 & 06.2 A

Students worked on coding various checksums.

Attendance was poor

SOFT6007 Class 05.4 W

We looked at using Google Fonts to add an interesting font to the page.

SOFT6007 Classes 05.2 05.3 05.4 N

05.2 I asked students to experiment with different CSS properties. We looked at the font property shorthand again and I asked students to experiment with that. I asked students to experiment with relative sizes using em

05.3 We looked at classes and IDs and I asked students to colour code their timetables using classes

05.4 We used Google Fonts to add an interesting font to the page

SOFT6007 Class 05.2 & 05.3 W

05.2 I asked students to experiment with different CSS properties.

We looked at the font property shorthand again and I asked students to experiment with that. 

I asked students to experiment with relative sizes using em

05.3

We looked at classes and IDs and I asked students to colour code their timetables using classes

SOFT6008 Class 05.2 &05.3 B

Students worked on coding the Luhn algorithm and some looked at some others too.

SOFT6008 Luhn Algorithm Patent

If you didn't like my explanation of the Luhn's Algorithm check out the original patent
http://www.google.com/patents/US2950048

SOFT6008 Class 05.4 Exam

We had an exam from 1230-1400.  I will send an email once I have the results organised.

The font for the code caused some confusions because l2 looked like 12.  I did my best to clear that up on the day, but it may not have been enough.  Here's a PDF of the exam and a version of it in a different font.  Please take a look at them both.

If you feel that you were disadvantaged by the typography of the exam, please send me an e-mail by noon on Wednesday (21st) and I will set aside your result.  I will get back to you with a time for a different exam, that will address the same learning outcomes.  However, before making this choice please be aware that the exam will likely be after 1800 some evening, will take less than an hour, and may not be open book.  Also it won't be a best-out-of-two scenario.  The mark you get for the second exam will be on only mark you will get.

I have no reason to believe that anyone was disadvantaged by the typography.  But if someone was I would like to try to redress it now while we have time rather than later.

SOFT6008 Class 05.3

Some students worked on the credit card check sum code, but other got ready for today's exam by reviewing code.

SOFT6008 The Google

I cannot stress enough the importance of trying to write code for yourself.  Googling for solutions is of limited value.  Students need to learn to write code from scratch.  That the the point of the programme they are enrolled on.  I've been doing this while now and in my experience obsessive Googlers tend not to be successful because they don't learn the skills they need.  Students are unlikely to learn much from other people's code.

If you try to write the code yourself I am happy to help you.  If your objective is to steal code and put all your efforts into covering your tracks, then you are wasting your time and mine.

No one is going to pay you Google code for a living.

SOFT6008 Class 05.2 & 05.3 W

Students continued working on the credit card validation.  Progress was slower than I had expected.  I think students are struggling with going from the problem definition to the algorithm.  The JavaScript code per se doesn't see to be an issue.

SOFT6008 Class 05.1 B

Stduenst worked on coding the Luhn algorithm in JavaScript