Got a new mac... what now?

A few of my friends have recently got their first mac... so what things would I recommend for anyone switching from PC to Mac?

Realise that it will take some time to get started with a new platform... and switching to mac is the same. You will need to spend some time really getting used to using the Mac, but the effort will be worth it.

1: What can I do with my PC data and apps I need to use?

I think the key to switching is to immerse yourself in the new platform and avoid using the old one for a few weeks... otherwise the temptation will always be to revert back to using Windows and you will never really get the benefits a Mac has to offer.

However, for somethings you do need Windows... Visual Studio for example. I use Parallels Desktop for Mac. Its a virtual machine, and allows you to run Windows, or other operating systems, under Mac OS. I have found this has worked really well for me. If you are moving from an existing PC, you can also make use of Parallels Transporter. It can be used to create a Virtual Machine image of your existing PC. You can then use this as a full backup, ensuring you don't lose any of those important settings or data from your PC.

An alternative to Parallels is Virtual Box. I know a few people who have used this, but I haven't tried it myself. The benefit of this is that it is free...

I don't think it has an equivalent to Parallels Transporter, but you cant argue with the price.

2: What general things should I know about?

Well there are many but here are a few important points:

• Clicking the Red x on the top left corner only closes the window, in many cases the program is still running. You need to use the Quit link from the program's menu.
• Running programs appear in the Dock with a small light blue ball under it.
• You can quit a program by right clicking on the program in the Dock.
• System Preferences is the equivalent to Control Panel.
• Learn to use Expose.
• Command replaces control for many shortcuts - Command Q quits for example.

Things you need to configure:

• Make sure you turn on two finger scrolling, and secondary clicks with two fingers in Trackpad settings in System Preferences.
• Set the right button on the mouse to secondary click.

3: What Mac programs should I look at using?

If you use any form of chat, you'll want to get Adium, a free chat client that can be used to chat with MSN, Yahoo, Google, Facebook, and others... There are heaps of extras that really make it an impressive application. The duck image is really cute, and the many replacement dock images are worth looking at.

Textmate is a fantastic text editor for developers. Its not free, but it is well worth the price. It comes with many extensions, such as Project Plus that integrates SVN flags into the project draw. The extensions for different code formats are also worth looking at.

Office for Mac is likely to be another program that you need. It is mostly compatible with the Windows version, though the 2008 edition is missing VBA support. I have both the 2008 and the 2004 version installed.

There are some alternatives to Office such as NeoOffice, and Apple's iWork. I have been using iWork for a number of tasks, and it is great at creating presentations (in Keynote) and documents (in Pages). It is not as full featured as Office, but I have found it easier to get the layout I want in many cases.

 

Well that should be enough to get started with... 

Plans for APS

Next year I will be teaching Algorithmic Problem Solving (APS) in first semester, a subject that I have developed and worked on over a few years. At the start of this year I trialled portfolio assessment with some success in this subject, though I improved on this in semester 2 with Object Oriented Programming. So what am I going to do differently next year?

Greater focus on the portfolio assessment: The portfolio assessment was good in this subject last year, but the focus can be even better. I found that this helped the students focus on what was important in OOP, the intended learning outcomes. My plan is to provide assessed learning activities during the semester, the resulting work will then be included in the students' portfolios. 

Simpler book: The first few times I ran this subject we used the language manual that comes with the language we are using. Its very dry, and not presented in an order that is useful for learning. This year I tried providing my own details, but didn't really get that right. So next year I will be providing a new book.

The book is what I am focusing on now. This will use a syntax based approach to learning the language, along with clear descriptions and illustrations to help students understand the programming abstractions. At this stage I have the following sections for the book:

1. Programs - introduces the Program abstraction and a large number of new "programming language" terms such as identifier, keyword, procedure, procedure call, expression, literal, etc.
2. Creating Procedures - focuses on creating your own procedures. 
3. Storing and Using data - variables, and the assignment statement.
4. Passing Data Around - introduces parameters (both in, out, and in/out).
5. Calculating Values - covers functions and function calls.
6. External Libraries - introduces units, shows how to use external units, and provides an example function from the SysUtils unit.
7. User Input - Up to this stage we will have been using literal values, but now all of the framework is in place to understand user input. This includes ReadLn, as well as reading command line arguments.
8. Branching - Indicates the change from programming "infrastructure" to control flow, and algorithm design.
9. Looping - For, while, repeat, etc...
10. Data abstractions - now the focus changes to the programming abstractions for data. This will include arrays, records and pointers.
11. Creating Libraries - Lastly onto creating your own programming libraries

My idea for this is to have each section as self contained as possible. Knowledge will be built up without the need for any "magic". This is the reason for delaying user input... this requires functions and out parameters, with library use being necessary if you want to convert values from strings to integers for example.

These 11 chapters will be covered in the first five weeks of the semester. Week one will cover 1 & 2, week two will be 3 & 4, week three on 5, 6 & 7, week four on 8 & 9, and week five on 10 & 11. This leaves seven weeks of the semester to learn about how these abstractions are used to create programs. 

Along with this I am aiming to keep the explanation of each concept or part of the syntax down to a single page, where possible. This is enough room to convey the important aspects, but not too much that the end result is overwhelming. It should also help to create a useful reference, where each idea has its own page. So far I am up to chapter 5 which start at page 39, so there isn't too may pages per chapter.

Let me know what you think. I'll post up some chapters later...

2008 Retrospective

Well the semester is over, and I'm starting to reflect upon a year with many experiments. The big things for me this year has been trying to put into practice many of the things that I have been reading about in the education area. The main focus has been on helping students to develop a greater understanding of software development and programming in general.

Background & the idea:
Software development is challenging, something that is easy to forget (once you get it). We have taught this through extended practice, in many cases without addressing or even discussing the associated principles. One of my frustrations with this has been the way many people subsequently approach their programming, usually with little thought or understanding. The classic symptom here is observed when the student makes random changes in the hope of fixing a bug, rather than thinking through their program and reasoning about its structure and implementation.

Is this a symptom of a lack of experience, or a greater problem related to the students understanding of the abstractions they are working with.

I am of the opinion that it is largely the latter, and that by refocusing on principles and core concepts we can teach people to better understand what they are doing when they create their own programs.

The idea, for this year, has been to refocus my teaching around the core principles. Teaching the principles of structured programming in first semester, and object oriented principles in second semester.

The method:
My teaching method aimed to get students engaged with the material, it is what the student does that counts...

Along with this I wanted students to be able to be adventurous, without risking losing marks. It was more important to have good quality, that a fixed time line. I moved to an extreme "Theory Y" position, with the perceived benefits of greater flexibility for the students along with greater responsibility.

I also wanted to make better use of the lectures, by distributing weekly reading and creating podcasts and using the lectures to discuss issues students were having with the concepts.

The results:
Now that semester 2 is over I am reflecting on the results of this approach. For me it has been a real roller coaster of highs and lows. Some aspects have worked well, others need improvement.

There was a marked difference between the introductory and advanced programming subjects. In general this approach has worked well with the more advanced students (Enterprise .NET), but how about the introductory subjects?

Releasing control of the system was definitely a different experience, though not an overly positive one in the introductory subjects. During the semester it was obvious that many of these students had failed to take responsibility for their learning. This was seen through missed deadlines, lack of attendance, and few questions on challenging areas. Flexible due dates meant leaving work until the last minute, rather than a chance to do quality work. The marking then reflected this situation, with many of those who "relaxed" failing to submit anything as the workload exceeded their time remaining.

On the positive side, there were some truly brilliant portfolios submitted. Those students who did take responsibility for their learning were able to demonstrate far more than I could have wished for. I hope that these students appreciated the flexibility, and the chance to explore areas they were interested in. But how can I adjust the process to better suite the larger majority of students.

Another positive was the portfolio assessment. This was time consuming and while course grained it has given very "accurate" grades, with no students being awarded a grade higher than they deserved due to a poor testing or marking scheme. On the other hand there were some students who's result I believe could have been better if they applied themselves more to the task, and demonstrating their learning.

The lecture method worked Ok with the advanced students, but need some tweaking. With the introductory subjects it really failed, which was disappointing. I think the problems were many... The text books were really 500% of what was "really" needed. As a result many students didn't do the required reading and subsequently blundered along trying to learn details from "lectures" without any real depth to their understanding. The method was significantly different and I failed to engage them in the process. Not providing my own large design early was not a great idea. Some of the lab exercises were incorrectly focused. Some of the portfolio pieces I suggested were overly large and time consuming, without the intended benefits.

Some bad points:

• Not enough focus on programming (overcompensation)
  
• Only few truly engaged with the method
  
• In general students did a poor job of managing their learning
  
• Some students didn't end up understanding the portfolio idea
  

Some good points:

• Large responsibility on students to manage their own learning.
  
• Mature students are better equipped for this method
  
• Portfolios were able to capture student learning
  
• Assessment was "fair"
  
• No penalties for those who learn during the semester, and can communicate their learning by the end.
  
• English communication skills can be enhanced, and communication issues are less severe then with exams (which require time compressed communication)
  

Reflections & Plans:
In summary this year has been a huge disappointment, and I'll need to try and reinvigorate myself before next year. I think the approach can work, and if I can get it right there should be some great benefits for the students. Reading back over this has, however, provided me with some hope.

"Once more unto the breach, dear friends, once more;"

My plans are to focus on teaching the learning process... as well as teaching about programming :). The method is different and I dont think I spent enough time on what was expected, and how to take advantage of the environment. I also have some more practical ideas related to using more "traditional" practices alongside this to help ease students into the experience. I am also more experienced now on what I need them to focus on in this approach. It has been a long time since I really engaged with these principles, and I'll be better equipped next year.

So to my introductory programming students from this year... sorry...

I would love to know what you thought of this experience and any suggestions you have... what do you think could be done to better next time.

I also promise to blog more... if you are interested in my plans and progress stay in touch! I need all the help I can get :)

Automator Postscript Actions & Leopard

Back in February 2007 I developed some Automator actions to manipulate Postscript files. I used these actions in the past to convert my presentation slides into multi-page PDFs. By creating these as scripts it became easy to quickly convert a large number of presentations into "lecture notes" that I could upload for the students.

Today I went back to test is they worked... and they didn't! The problem was that Leopard is now unix2003 compatible, and my script wasn't. The issue was my use of the file -i {} command which worked in the legacy mode, but fails when using the updated version. The fix was simple, when I found it, use file --mime {}...

For those who are interested... download the automator actions...

Python is intriguing...

I share an office with Clinton who has lately become somewhat of a Python convert. Today I started to play with Python for the first time. Unlike "normal" people I didn't start with Python in Python... I started by embedding it within a Pascal program. Embedding Python within Pascal was really simple - I am totally amazed! With less than 20 lines of Pascal code you can embed a Python interpreter and have it load and run python modules.

The code for this will be placed on Google Code once I have it a little farther along.

Why am I doing this? We are looking at providing the ability to run Scripts within SwinGame, its looking like we should have something interesting soon!

Portfolio Assessment

Well semester 1 has started... I can where did all that time go? This semester I am teaching HIT1301 Algorithmic Problem Solving again, and as always there are improvements to be made. This semester most of the changes revolve around the assessment, with some minor changes to the lectures and resources available.

On the assessment side of things the assessment will be much more flexible than in the past. Basically for APS there will be some core assignments and tests, each quite short but covering all the basics. Passing these means you pass the subject, in most cases you need to get them working to pass so dont think 50% = pass for these! To get anything greater than this students will need to submit a portfolio that shows their capabilities and depth of understanding of software development. This means students can choose what they want to focus on, while still ensuring they cover all bases. The focus of this assessment is on depth of understanding and quality of work, rather than quantity.

I'll keep you informed of how this goes... Let me know what you think of the idea.

In other news we are (well Clinton really) making progress with the new python port of SwinGame. This will mean that you will be able to call the SwinGame API from Python... the next step is to embed Python within SwinGame :)

SwinGame Excitement

The swingame project has gone through some very exciting developments. Over the last few weeks we have managed to develop a new edition of SwinGame (version 1.1) and is now available for download. Have a look at the game promo videos that we have created for this of YouTube they have been great fun to create.

Let us know what you think.