We wanna code!

Announcement, new Java 40000 came out, please update! An unusual post before our tonight's OOP Lecture - two things: 1) I won't be able to come today either (third time in a row!!), so if anyone was so kind and take notes of anything especially important and email it to me after, I'd really appreciate it. 2) The Assignment 1 is due today and if you are still struggling with it - make sure you visit my Assignment 1 page (last file - the main program - still need a video, but you can find a link to it at the very end of the page).  Cheers!

First assignment... phew! I think I can end with the picture above... But I won't! Let's capture our last night's lecture very quick. We had a couple of minutes of an actual lecture about how Unix works, how the prompt that we use to complite C or cd, ls, mkdir and so on... is just a program that uses fork()... I don't know guys, my head melts even when I write about it... So I guess a right thing to do would be checking all the youtube (I mean all of it!) in search for some answers. Search for: - how does Unix work - what is Unix prompt - what is Unix shell - what is bash - what is fork() (what the fork is fork()??!!) - how parent and child processes work etc...  I'm actually very excited about it as it means a lot of time on an Orbitrack youtubing sh*t... And the assignment! It was very simple / very hard depending on how comfortable you feel with C, pointers, stacks data types and reading compilation warnings and errors. S...

Hi, Yet again I missed the lecture last night... But our good colleague John was nice enough to inform us all on facebook about two things: Next week is the deadline for our Assignment 1. We have to send a soft copy to John Gilligan until next week's OOP lecture and hand over a hard copy next week or at least week after. We will also have a revision lecture next week, so I think it's a good idea to come in and get the knowledge to sink in. Btw, how's you Assignment 1 going? If you need any pointers, feel free to drop in to my OOP Assignment 1 page . Good luck! Problems with your Java IDE? Check out setting up for Java page for a refresher. See you all soon!

Get in a queue, we're about to stack! My puns become less and less funny... But anyway, we are already discussing Stack and Queue data structures that are fundamental to many concepts and functions in computers. We didn't really focus on what can they be used for, but it'll come later. If you would like to expand that knowledge on your own (and as I said before, it's always good to be prepared before the lectures), you can start googling such as 'what stack and queue is used for'. For example, that's what I found: Stacks and Queues It's good to know what we're learning about and try to comprehend how it works - and because we have very limited time during our lectures to cover it all, it's good to do some searching on our own. And when it comes to the mechanics of stacks and queues - the stuff that we covered this week on CT2 - it's crucial we all understand the concept of pointers. And then structs I suppose. And functions. ...

Still in Polska :D Hope everyone is having fun! Don't know what did we go through during the lecture, but feel free to check out my Assignment 1 videos if you need a kick starter or some hints. Setting up Java Assignment 1 Tutorial Cheers!

Away in Poland!

No notes for this week :( (and the next one)

Forgot to make notes! Will catch up :)

Did you know that Java is one of the Indonesian islands that was the first one to grow coffee? That's why some people colloquially called coffee java and that's where the programming language name came from. But back to reality, we have some Java learning to do... Week 3 of OOP brought up the following: - quick description of Object Oriented Programming, - explanation of how Java works (compiling and stuff), - what is Java Programming Language, Java Virtual Machine and Java Platform, - quick mentioning of what Java Application and Applet is, - and then we started looking at some basic Java codes. My usual recommendation is to go through the week3 lecture slides from Webcourses or Google Drive and make sure all the information sinks in. Also, you can copy and paste some of the codes from the slides, so you can look at how they work and play around with them. And btw, did you start looking at the assignment yet? Check the Google Drive OOP folder Here . Cheer...

Quick tea-time DIT update (good idea for a youtube channel). So that was quick... From "these are pointers, but don't worry about it" we went straight "so these are pointers and they work like this and I know it melts your brain, but we're just warming up...". Or something like that, can't remember exactly what Denis said, but that's the gist of it. The truth is - it's not as hard as it seems to be. It's just abstract and some stuff about pointers needs a bit of time to sink in. But as any other new information - once you get it - you get it! Anyways, here's what we went through last night: - what pointers are (just another variable - containing addresses in their case), - dereferencing pointers (and how * means two different things depends where it is), - why we use pointers (passing by reference), - functions in C and difference between passing by reference and by value. We went trough some of the programs that Denis...