Skip to content

Some photos of the White-checked Gibbons at Adelaide Zoo.

Yesterday the family and I visited Adelaide Zoo. Not the best day to go as it rained in the early afternoon. Before it rained I had the opportunity to get some good photos.This gallery is of photos of a White-checked Gibbon and what I assume is one of her offspring. The female is a lovely golden colour, and the male offspring has black colouring.

Brush Tailed Rock Wallabies at Adelaide Zoo.

Yesterday the family and I visited Adelaide Zoo. Not the best day to go as it rained in the early afternoon. Before it rained I had the opportunity to get some good photos.This gallery is of photos of Brush Tailed Rock Wallabies.

My brief reflections on "Workshop Wednesdays" and all staff meetings.
Image by: Gerd Altmann.
Image by: Gerd Altmann.

Brief Reflections on Workshop Wednesdays

Ever since I saw a link to this article in the Twitter feed of my friend Kahiwa Sebire a few weeks ago, I've had this post percolating in the back of my mind.

The article is a humorous piece about the evils of all staff meetings. The article was particularly amusing because I was, and still am, reflecting on a regular meeting that I'm advocating, and organising within my team at Flinders University.

With the support of senior management, I started an initiative early this year which I called Workshop Wednesdays. The purpose of the meetings, as I outlined in my original proposal, is to try to foster a culture of collaboration, cooperation and knowledge sharing.

I can't go into too much detail, as I don't have the permission of the team. The one hour, fortnightly meetings, are divided into three main sections.

First, is any administrivia that needs to be shared with the team, as well as an update on any issues raised in the previous meeting. In this section we have also covered updates on mini projects that the group has started. I was particularly excited by our first few meetings where we identified changes to the login process to the student information system that we believe has improved the student experience.

Second, is the standups. We've adapted the concept of standup meetings from the agile software development methodology. Each team member focusses on the following three questions:

  1. What did I accomplish in the past two weeks?
  2. What will I do in the next two weeks?
  3. What obstacles are impeding my progress?

Each team member has two minutes to work through the above questions. To help us focus, I developed the Workshop Wednesday standup helper webpage.

I feel that these two minute overviews by each staff member are very important. And some very valuable, and sometimes robust, discussions have been sparked  by them. A constant challenge is striking the right balance between the need to keep people to time, and to give people the opportunity to contribute and feel they've been heard.

The third and final section is a discussion section. During these sessions we've reflected on this such as ways to improve the student experience, and what the team needs from a possible change in issue tracking and project management systems.

These workshops are challenging, and it is a challenge that I take seriously. I am always seeking feedback, and looking for ways to improve.

In June this year the workshops will have been going for a little under six months. During that time we will have a formal review. The goal of the review is to identify ways to improve the workshops, outside the regular requests for feedback. Additionally the team, in conjunction with senior management, will decide if we continue to have these sessions.

While I can appreciate the sentiment of the article that Kahiwa tweeted about. I also feel that some all staff meetings can be beneficial. A sentiment that I hope is shared by the rest of my team.

I had a great time volunteering to help the graduations team at Flinders University on Friday. As someone with an introverted personality it was also a growth opportunity for me.
Two doctors at the empty graduation desk.
Two doctors at the empty graduation desk.

Last Friday I had the privilege to volunteer and help with two graduation ceremonies at Flinders University. I've been to three graduation ceremonies, as a graduand, this was the first time I was at a graduation ceremony as a staff member.

As someone with an introverted personality, I tend to avoid social situations, especially those with large crowds. I'm terrible at small talk and chit chat. I have no idea what to say.

However when the invitation to volunteer to help at the graduation ceremonies came out I jumped at the chance. This is because I've realised that I'm at a point in my career where I need to grow my professional network. I felt that volunteering would be a small, but significant step towards this goal.

I'm so glad that I got over my trepidation that morning and went up to the registration desk for the first ceremony of the day. There were so many happy, excited and nervous people. Young and old, from all walks of life. I couldn't help but be swept up in the excitement.

Working on the registration desk is a critical part of the preparation of the ceremony. This is because we check off the graduands who have arrived for the ceremony and give them their seat numbers. It is critical that they sit in their allocated seat, so that they are in the right order for when their name is called to cross the stage and receive their parchment.

Having graduands out of order is a nightmare scenario. It would be embarrassing for us, the graduand, and the academics on stage. We take many precautions to ensure this doesn't happen, and it starts with the registration desk.

It's critical to be accurate and make sure the graduands know how important it is. I keenly felt the pressure to be accurate, and yet fast, to ensure everyone could register in a timely fashion.

The time flew by and there were many happy people. It took the pressure off, and it was with a sense of accomplishment that I crossed off the last name and handed over the last seat number sticker.

For the second ceremony I was stationed out the front of the registration tent. I had to ask each graduand which degree they were graduating from that day, to ensure they went to the right registration desk. I believe I spoke to more people that day than I have in months.

It was exhilarating to help people get to the right registration desk, answer questions, and generally try to be as useful as possible. One of the many highlights was helping a family by taking some photos of their group, making sure they could all be in the photo together. They all had smiles on their faces, and I couldn't help but smile back.

Reflecting on my experiences over the weekend , I became convinced that sometimes it is good to get out of my shell and experience new things. It also gave me an appreciation for what my friend Mark Drechsler went through at the start of semester at Flinders Connect. I had to interact with lots of people for one day, and it left me exhausted. I have no idea how he did it at the start of semester with many more people each day for two whole weeks.

This is a long way of saying that volunteering not only helped the graduations team, it was a growth opportunity for me. I look forward volunteering again next time.


A brief overview of the story behind the John Smith photos that have started appearing on my site.
A collage of some of the first john smith photos
A collage of some of the first john smith photos

As you may already know, I work as a business analyst at Flinders University. The main campus is a really nice place to work, and there are lots of walking paths to provide some exercise at lunch time. Which is fortunate because, like many office workers, I need to get out and walk more.

Sometimes it can be hard to find the motivation to go for a walk, especially when the pressure of a deadline is looming. With this in mind, I wanted to add something extra to my walks.

I also have an interest in photography, and a burgeoning interest in social media. So the other day I reactivated my Instagram account. I also found a little figurine of the Tenth Doctor from Dr Who. I wanted to avoid any trademark related issues, so I use the tag 'johnsmith' for the photos. In reference to one of the many pseudonyms that The Doctor has used over the years.

Taking photos of the little guy around the Flinders University campus adds something to my walks, and puts a smile on my face. It also opens my eyes to things around campus that I may not have seen before, as I'm always on the lookout for a potentially good shot.

The photos are posted to my Instagram account. An IFTTT recipe automatically makes a post here on my website, and the JetPack sends that post to all of my other social media accounts.

I hope others find my photos interesting.

I needed a way to automatically keep track of changes to the SQL files that I develop as part of my work at Flinders University. This post explains how I did that.
Photo by: House of Geekdom.
Photo by: House of Geekdom.

As I mentioned in an earlier post, now that I'm working as a business analyst at Flinders University I don't do as much development as I used to. I'm still keeping busy with the development of a new web app, which I hope to write more about soon.

A large part of my job is writing SQL queries that are run either in an Oracle or MariaDB database. Some of the queries, especially those run in the Oracle database, can be quite epic in terms of size and complexity.

For this reason I needed a way, with as least amount of input from me as possible, to keep a history of each SQL script. So that as the script was developed I could easily go back to a previous version if I needed to.

Additionally I use OS X as my primary workstation, but I need to be able to quickly and easily access the SQL scripts that I develop on my secondary Windows workstation as well. As such, I needed a way to manage line endings in a sensible fashion between to the two platforms.

For these reasons I developed a solution that is based on Watchman and a Git repository hosted on Bitbucket. Although any Git hosting provider, including self hosting, would work just as well.

Installing Watchman is easy using Homebrew, my package manager of choice on OS X, and I had it up and running really quickly.

I then created a Git repository for my SQL scripts which used a repository hosted on Bitbucket as a remote.

To manage the the process of committing changes to the repository I wrote the following short and simple shell script.

#!/bin/bash -e
# Script to automatically commit and push changes...
# Called via Watchman so it knows when to do stuff.
NOW=$(date +"%m-%d-%Y %T")
GIT_PATH=`which git`
REPO_PATH="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
OSA_PATH=`which osascript`
# Make sure we're in the right directory
# Run the git commands.
$GIT_PATH pull
$GIT_PATH add -A .
$GIT_PATH commit -m "Scripted update on $NOW"
$GIT_PATH push
# Show a notification.
$OSA_PATH -e 'display notification "SQL script repository updated" with title "SQL Script Auto commit"'

I am not the best shell script programmer, and I'm sure this script could be improved upon to make it more elegant and fault tolerant. But at the moment it is doing the job.

What it essentially does is pull down any new changes, which will be very rare, adds new local changes, commits them and then pushes the change up to Bitbucket.

The last line of the script shows a notification so I know that the process worked. This is important as I don't want the process to fail silently. Seeing a brief notification when the process completes helps in knowing everything is OK.

The last piece of the puzzle was to get Watchman to automatically call my script when changes to the SQL files had been detected. I configured a trigger in Watchman using a command like this:

watchman -- trigger /full/path/to/the/repo autoupdate '*.sql' -- full/path/to/the/rep/

What this command essentially does is add a new trigger called 'autoupdate' which monitors for changes to '*.sql' files in the repository. When a change is detected the shell script from earlier is called.

In this way, each time I save my SQL file, which I do habitually just prior to running them, a new version of the file is automatically added to the repository and pushed up to the server.

This not only gives me a full history of any changes, it also gives me a backup copy. Additionally when I need to use the SQL file on my Windows workstation, all I need to do is pull the new changes down to the copy of the repository on the workstation. What's really nice is that Git manages the line endings for me, which is another thing I don't need to worry about.

So far this process has worked really well for me. If you have any thoughts about this approach, contact me on Twitter.

Today after many years I've succumbed and created at Facebook account. This post explains why.
Photo By: tookapic.
Photo By: tookapic.

Earlier today I joined Facebook. I feel like I've crossed over to the dark side. My Facebook profile is available here.

I've resisted joining Facebook for many years, in fact I resisted joining social networks for more years than I care to count. I was happy with my blog and using Twitter. My Twitter profile is available here.

Earlier this year my friend Mark Drechsler convinced me to set up a LinkedIn profile, which is available here. That was the start of the slippery slope into social media.

After I completed the signup process I tweeted about it.

My friend Kahiwa Sebire wanted to know why after all this time, I've succumbed to the lure of Facebook. Essentially it comes down to the following three reasons.

First, I've been noticing that there is more and more content that is exclusively available on the Facebook platform, which I'm missing out on. Including the pages of some of my favourite podcasts including:

Perhaps now that I have an account, I'll be able to contribute to the vibrant communities around these podcasts and other content.

I've also noticed that some of the activities that my little girl is involved in, are promoted on Facebook. I increasingly feel like I'm missing out on that aspect of her life.

Second, many of my friends use Facebook to communicate and keep in touch with each other. In the past I've been very bad at using email, and especially the phone, to keep in touch with friends. My hope is that through Facebook we can keep in contact easier and with more success.

This third thing is what tipped me over the edge.

My little girl, who is four, loves to talk to her Granny and Pa in Queensland on the phone. The trouble is that she hasn't quite grasped the idea that they can hear her, but they can't see her. So she spends time trying to show them her favourite toy, latest craft masterpiece, or lego construction.

We've tried various video chat services in the past, such as Google Hangouts and Skype, with limited success. We even tried 3G video calling, but as they have an Android based phone, and I have an Apple iPhone, it wasn't possible.

I want her to have a close relationship with her grand parents, and video calling seems like the best alternative to actually being with them.

Granny is already on Facebook, and is familiar with using Facebook to chat. My understanding is that Facebook Video calling is super easy to use. My hope is that we can use this service, where other services have failed.

So in essence the main reason for having an account, the thing that pushed me over the edge, is video calling between my little girl and her grandparents.

It's an experiment, and I'll post here on my blog about the results.

Having to add my mobile phone number to my account on an online service to enable two-factor authentication got me thinking. Is the rise of 2FA a grab for more personal information first, and an improvement in online security second?
Photo by: succo.
Photo by: succo.

The other day I signed up for a new online service, which one isn't relevant to this post.

When signing up for new online services I try to provide as little information as possible. This is because I am a firm believer in the tenet that 'If you’re not paying for the product, you are the product', as outlined in this post by Charles Stross.

I worry about what  my personal information is being used for, outside what is strictly required to provide me with the service that I'm signing up for. So when I signed up for this online service, I didn't add my mobile phone number to my account information. It was optional field on the account settings page, and isn't required to provide me with the service that I required.

Once my account was set up, I went looking for the two-factor authentication settings. I always enable two-factor authentication, also known as 2FA, because it improves the security of my account.

Using a username and password to access an online service is an example of one-factor authentication. You're proving that you are the registered user by providing the username, and something that only you know, your password.

Two-factor authentication uses a second factor, which is something you have. Typically this is your mobile phone. The basic premise that only you should know your password, and have your mobile phone.

Asserting that your mobile phone is with you is achieved through one of two main means:

  1. Sending a code to your phone via SMS.
  2. Using an app on your phone to generate a code.

One of the most popular applications used to generate codes is Google Authenticator. There are others, including apps specific to online services, and popular password managers such as 1Password.

To enable two-factor authentication for the online service I needed to provide my mobile phone number. The service used it to send me a code to confirm the phone was mine. Once they had done that, I was able to configure two-factor authentication using their app on my phone.

What bothered me was that I needed to set up SMS authentication first, before I could use their app on my phone. Additionally I can't delete my mobile phone number from the account, because to do so would turn off two-factor authentication.

There is no need for this service to have my mobile phone number, it isn't required for two-factor authentication because I can use their app. It isn't even required as a backup option, for example if the app breaks on my phone, or I replace my phone and keep the same number, as I have backup codes stored securely in my password manager.

In essence it is personal information that I was forced to provide to ostensibly enhance the security of my account, when it isn't required. That annoys me, and got me thinking.

The rise of two-factor authentication is a good thing. Anything that increases the security of our online accounts is a step in the right direction. Especially if it is easy to setup and maintain.

Wearing my cynical hat on, which may or may not be made of tinfoil, I can't help but wonder if the collection of more personal information is viewed as more important than improving account security by some online service providers.

I'm interested to hear what you think, let me know via Twitter if you feel so inclined.

My reflections on open source, security and trust. Sparked by an off hand comment by a tech news podcast guest.
Photo by: succo.
Photo by: succo.

Last week I was listening to a tech news podcast. They were discussing the recent Patreon data breach. In light of the breach, and the need to change passwords, the topic of password managers was discussed. The two main benefits of password managers are they:

  1. Make it easy to generate long complex passwords.
  2. Store the long complex passwords securely so that you don't have to remember them.

The question was raised, how do you choose which password manager to use? In response the guest that day suggested that using an open source application from GitHub would be best because 'you can read the source code', and can therefore know that it is OK.

This got me thinking. Just because, as a user, I can download the source code for an application, does that make it any more secure?

My career to date, has involved writing web applications in a variety of languages, on a number of platforms, for many different use cases. Almost always I have used open source software, and in some cases released the code that I've written as open source as well.

While working at Blackboard, where I worked for a little over two years, I needed to review the source code of Moodle plugins for inclusions in the Enterprise Moodle or Joule platforms. This was to ensure that the code contained in the plugin met the high standards necessary for an enterprise class system. The security of the code was an aspect of the review.

Things get 'interesting' when a plugin written with the assumption that a typical course contains 10-100 enrolments, is used with a course with 1000 enrolments. Especially if there is a need to keep page generation times to a minimum... but I digress.

One thing which I have learnt in doing this type of work, is that reviewing software code is a skill which is difficult to master. In my opinion, it is harder than writing code, and uses a different skill set. Additionally code varies greatly in quality and clarity, which makes the task of reviewing code even harder.

I would go further and argue that reviewing code for security related issues is a specialisation that goes deeper than a standard code review. In short, writing code is one thing, reviewing it is another, and reviewing it for security related issues is an entirely different thing again.

I believe that the point the guest was making was an extension of Linus's Law, which states:

given enough eyeballs, all bugs are shallow

The premise is that the more developers that look at the code, the more bugs are found and resolved. As a result the software improves. In the context of my reflections, it also means that the software is more secure. However this may not be the case, as the Heartbleed and Shellshock bugs have shown. A security related bug can exist in open source code for a significant amount of time.

Pondering this issue further, I came to the conclusion that open source software is not inherently more secure than proprietary software, just because the source code can be read by anyone.

This lead to me wonder, why open source software is considered more secure than proprietary software. After all, both types of software contain bugs, including security related issues, and both are patched regularly.

The answer I've come up with, is that open source operates on a different trust model than proprietary software. By virtue of being open, the developers of the software are implying that they have nothing to hide. By refusing to provide the source code, proprietary developers could be seen as having something to hide. Indeed, an argument could be made they are practicing security through obscurity, which never ends well.

Ultimately, whether the source is open or closed, there are still going to be bugs. Some of which will put the users security and privacy at risk.

Having gone through this thought exercise, I can summarise my conclusions as follows:

  1. Open source software is seen as more secure, because it is more trustworthy, as the source is available for all to see.
  2. Closed source software is seen as less secure, because it is not trustworthy, as the source is closed and access to it is restricted.

I believe this to be flawed logic. As I mentioned earlier, not every developer is going to be good at reviewing code, and not every developer undertaking code reviews is going to be good at spotting security issues.

Perhaps there is an opportunity here for developers of closed source software to undertake an independent third party code review of their proprietary systems. And more importantly, publish the results. For example such reviews are taken into account by the EFF in their Secure Messaging Scorecard.

This has been an interesting thought exercise, kicked off by a somewhat off hand comment by a contributor to a tech news podcast. I wonder why my next reflection will be about. I'm interested in hearing your thoughts, especially if you disagree with me. You can contact me via various means as listed on my about page.


Fork in the Road. By: Bs0u10e0.
Fork in the Road.
By: Bs0u10e0".

Friday, October 9, 2015 was my last day at Blackboard. I started with Blackboard in July 2013, working in the Adelaide, Australia office1.

I was employed as a Senior Software Engineer, and worked as part of the client development team. I supported clients in their use of the Enterprise Moodle platform. As the name suggests, this was an enterprise class system which is built on top of the open source Moodle, Learning Management System (LMS).

Earlier this year I made the transition to the product development team at Moodlerooms, which is also part of Blackboard. I worked as a software engineer in the product development team for Joule. The Moodlerooms Joule platform is also built on top of Moodle. The focus of my role was on defect resolution, and enhancements related to the core product.

In the nearly two and a half years that I was at Blackboard I saw a lot of change, and grew both professionally and personally. I enjoyed working on open source code, and helping clients meet their needs through customisations to Moodle.

Reflecting on my career in the past few months, it became clear to me that I am happiest working in the higher education sector. The corporate culture necessary to sustain a commercial enterprise, is not for me.

Additionally I came to realise that I am not the typical software developer or software engineer. The aspect of my work which I found the most fulfilling is working directly with users. Whereas many people who work in this type of role prefer not to deal with end users, and possibly people in general2.

To that end I am starting as a Business Analyst at Flinders University on Monday, October 19, 2015. I'll be working in the Student Systems area, supporting users of the universities Student Information System (SIS).

I'm looking forward to, with great anticipation, returning to the higher education sector, where I have worked for most of my career. I'm also excited about the new challenges that await me, and the new things that I will learn.

The topics that I will post about here on my blog will change, although I have a few posts rattling around in the back of my mind already.

I'm excited to see where this new change in direction for my career will take me.

1At the time I started, the company was known as NetSpot, which had been acquired by Blackboard in March 2012.

2I'm over generalising in jest.