Posts archived in IT

For the last three years (give or take a month or so) I’ve been working with the great folks at Massive.
Time has come for me to move on and find other great opportunities.

If you know of any interesting .NET Jobs opening up in Sydney (or Melbourne), please let me know.
I’ll be available to start from about the 16th of November. Update: I’m no longer looking for work, thanks.

Things I’m currently interested in:

  • Playing with cool gadgets: Android & Windows Phone 7
  • Multithreading & Parallel Processing in .NET 3.5 and 4.0. (ParallelFx, Rx, etc)
  • IPTV / Streaming Media Delivery

Things I’ve been working with most recently:

  • ASP.NET Web Apps (.NET 3.5/WebForms)
  • RESTful WCF Services
  • Building Custom Serialisation/Deserialistion Adaptors &¬†APIs for third party services.
  • Build Management

To all the folks at Massive: It’s been a great ride; Working with some of the smartest folks I know. Thanks for all the fish.

(Originally posted by me on AuTechHeads, April 26th 2010, and preserved here)

Why a fancy resume is useless if you have no enthusiasm for technology.

One of the things rarely discussed in guides on how to get a job in IT is enthusiasm for technology. I am of the opinion that first and foremost, you need to be a technology geek if you want to work in IT.

Don’t confuse being a technology geek with being the stereotypical pimply-faced, pale skinned, greasy haired dweeb. I talk simply of people who have an innate understanding of some area of IT. The kind of person that hears about some new thing and gets a little (or lot) excited.

Personally, I can’t understand why would anyone choose a job in IT if they didn’t like tech.
It would be like me choosing a career in marketing or interior design. Areas in which I really have zero interest.

Yet when interviewing candidates for software development positions, I find far too many of these people. They tend to express no particular interest in any part of software development in particular, or technology in general.
My only conclusion is that they are in IT because it’s a reasonably well paying job.

The not-so-funny thing about it is that these people have fantastic resumes, with years of experience across all sorts of tehnologies. Often they’ve worked for big name companies.

Perhaps these people work well in development teams where there’s a large corporate structure that treats developers like cogs. But for smaller development shops – you really need your wits about you.
Situations inevitably arise where nobody on the team has experience with some particular technology.

A technology geek will be able to solve the problem (either on their own, or with the assistance of the team) and draw on their own experiences gained while reading about or experimenting with other related technology.

That, in my opinion is why you must be a technology geek to work in IT.

So, readers: What is your opinion – is there a role for non-tech-geek folks in IT?

Edit: This post was linked from Stack Overflow – you might want to check back there for more/better discussion about the topic.

Recently Jeff Attwood wrote about how they are using ELMAH to get more information about the types of errors occurring in Stack Overflow.

Effectively ELMAH is designed as a ‘drop in’ fault capturing system for ASP.NET. It works really well there, and for many situations you can get along just fine without even needing to recompile your application (it does need some editing of the web.config though).

I wanted a way to capture more detail about the faults occurring in our dev and production environments, especially when working with WCF – since a lot of error detail tends to be hidden, or is difficult to reproduce.

Dropping in ELMAH into a WCF application will by default mean you miss the vast majority of errors – WCF swallows the error, and doesn’t let it get back up to ASP.NET.

There’s two ways you can go about fixing this:
Side Note: If you’re not hosting WCF in ASP.NET, then Option 2 may not be directly possible for you without some modification.

#1 – Wrap everything in try/catch blocks (if you didn’t already) and sprinkle this line around everywhere:


#2 Add a HttpHandler, and Decorate your Service(s) with an Error Handling attribute.

I borrowed the ServiceErrorBehaviourAttribute code from somewhere else, and I can’t find the source of it at the moment. Effectively this was so I could manipulate the HTTP Status Codes going back to the client when there was an error. It just so happens that this is a great way of capturing Exceptions and sending them to ELMAH at the same time.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.ServiceModel;
using System.ServiceModel.Dispatcher;
using System.ServiceModel.Channels;
using System.ServiceModel.Description;
using System.Collections.ObjectModel;
using System.Net;
using System.Web;
using System.IO;
using Elmah;
namespace YourApplication
	/// <summary>
	/// Your handler to actually tell ELMAH about the problem.
	/// </summary>
    public class HttpErrorHandler : IErrorHandler
        public bool HandleError(Exception error)
            return false;

        public void ProvideFault(Exception error, MessageVersion version, ref Message fault)
            if (error != null ) // Notify ELMAH of the exception.
	/// <summary>
	/// So we can decorate Services with the [ServiceErrorBehaviour(typeof(HttpErrorHandler))]
	/// ...and errors reported to ELMAH
	/// </summary>
	public class ServiceErrorBehaviourAttribute : Attribute, IServiceBehavior
        Type errorHandlerType;

        public ServiceErrorBehaviourAttribute(Type errorHandlerType)
            this.errorHandlerType = errorHandlerType;

        public void Validate(ServiceDescription description, ServiceHostBase serviceHostBase)

        public void AddBindingParameters(ServiceDescription description, ServiceHostBase serviceHostBase, Collection endpoints, BindingParameterCollection parameters)

        public void ApplyDispatchBehavior(ServiceDescription description, ServiceHostBase serviceHostBase)
            IErrorHandler errorHandler;
            errorHandler = (IErrorHandler)Activator.CreateInstance(errorHandlerType);
            foreach (ChannelDispatcherBase channelDispatcherBase in serviceHostBase.ChannelDispatchers)
                ChannelDispatcher channelDispatcher = channelDispatcherBase as ChannelDispatcher;

Once you’ve added that, then it’s just a matter of decorating your Service like so:

    [ServiceContract(Namespace = "")]
    public class MyServiceService
      // ...

…and then making sure ELMAH is added as a reference, and adding it’s entries to your web.config.

Then you’ll be getting a whole stack of errors you otherwise may not have seen.

It’s also possible to log exceptions from higher up the chain (eg Databases, Files, etc) by using the line of code from Option 1.


Whilst ELMAH is great for capturing information about the request, I havn’t yet found any way to capture the original HTTP Request – this would be the ultimate goal for me.

It’s also not particularly easy to capture additional information (such as database records, or objects in cache, etc) without rolling your own copy of ELMAH.

All in all though – for a few minutes work, it’s one additional way to capture errors that your existing code may not be able to.

Yes, ELMAH even captures errors (in most situations) when your WCF services can’t start up (eg your fubar’ed some attributes).

Hope that helps.

NB: Use this code at your own risk, don’t blame me if it brings down your multi-million-dollar-per-hour application and causes you to go bankrupt.

Here’s two things that caused me a bit of pain when working with WCF. Hopefully these pointers should help you get back to more productive things.

No Output when returning Serialized / Serialised objects.

I had been working on adding a significant number of methods and properties to a series of classes, and when I went to test the service I got literally no output.

Debug points indicated that all properties were there, and valid – but still WCF wasn’t returning anything. There was no exceptions  being returned to the client.

The best tool for debugging these sorts of solutions is to first of all enable Tracing and MessageLogging.  This is done via the WCF Service Configuration Editor, on the Diagnostics tab. 

Once you’ve done that, and re-run the projects – you can open up Service Trace Viewer.  For me under Visual Studio 2008, this was under Microsoft Windows SDK v6.0A > Tools.


This tool then lets you open up the trace log generated in your solution directory, and see all the activity that’s been happening.


From here, it was just a matter of scrolling down to the activity entry that had the yellow hilighting (indicating a warning), selecting it – then clicking on the Errors.

For me, the first time this happened to me, it was because I had stuffed up the DataMember Name values. It has also occurred for other reasons, such as a property not being populated, when I had specified that it was both required, and also that it could not emit a default value.

Can’t get mex to work

No, this isn’t a misguided racial slur. I was having issues setting up the mexHttpBinding on an ASP.NET AJAX WCF Service.

The solutions all point towards the same thing, that you need to set up an endpoint, and set the contract to IMetaDataExchange, then set the behaviour to have <serviceMetadata />. Except that it just wouldn’t let me add that property to my endpoint behaviour, and whenever I changed it to a service behaviour it would then not allow me  to set the other properties I needed for that.

Well, perhaps I’m particularly slow – but hopefully this pointer will help someone else.

1: Create a NEW service behaviour:

  <behavior name="MyServiceBehavior">

2: Add a new endpoint to your  existing service

   contract="IMetadataExchange" />

3: Add the behaviorConfiguration you added in Step 1 to the Service (NOT the endpoint).


I kept trying to add it to the endpoint, and failing miserably. So much time spent back-and-forth on this!


That’s it for this instalment of “WCF is great, but I wish the config was a bit easier to understand”. Stay tuned for more exciting episodes!

Today I spent about half an hour banging my head against this problem:
Whenever I would try and return a business object, I’d simply get no response from my WCF Service. Litterally nothing.

The problem turned out to be that I had accidentally specified the DataMember Name of a property in a sub object twice.

So, I had my broken class set up like:

[DataContract(Name = "MyClass", Namespace = "Example")]
public partial class MyClass
[DataMember(Name = "property1")] public int Property1 { get; set; }
[DataMember(Name = "property1")] public string Property2{ get; set; }

An instance of this class was used as a property in another object, which was being returned from WCF.

.NET didn’t throw any sort of error unless I tried to return just “MyClass”.

Sure, it was my fault, but if you have a complex data structure, this could get awefully difficult to find without some sort of message from WCF.

Yes, this is part of that ultra nifty WCF JSON .NET 3.5 Flex project at work. :)

(A note to readers: This is all pure geek/coder content – Please skip this if nothing in the subject line makes sense)

I started on a new project at work for a client a bit over a week ago, by virtue of the requirements, we decided to investigate the use of new version of Microsoft’s  .NET Framework, Version 3.5, for all of the server-side services.

Microsoft have been quite strongly pushing the benefits of the new features of .NET 3.5. There’s been a few key features which are particularly interesting, and if all goes according to the marketing hype, should end up saving a huge amount of time and effort, whilst ensuring that we use well known and standardised interfaces.

What features?

Windows Communications Foundation (WCF) is particularly interesting because it promises to let you (mostly) remove the whole ‘how’ and ‘where’ portion of communications between tiers, and let you focus on the ‘what’ and ‘when’.

In essence, WCF should let me state that I want to create (say) a Web Service, that accepts information in format X, and outputs responses in some other format. It doesn’t have to be a Web Service either, it could be a Peer to Peer network speaking in straight binary streams.

For this project the client-functionality is all in Flex, so we need to ensure that the Flex guys can quickly decode all the responses and turn them into Action Script objects. Through a bit of experimenting and application prior experience – Web Services speaking JSON appeared to be the easiest and most light weight method of doing this.

Language Integrated Queries (LINQ) is another particularly interesting technology, particularly because it lets me focus on what I want to do with the data I have, rather than spending time transforming it from the Database tables, rows, and procedures, into .NET objects and methods.

There are a number of implementations of LINQ, which enables you to query a variety of sources – the one that I’m most likely to use is LINQ to SQL (talking to SQL Server). Regardless of what I’m accessing however, the syntax is identical – again, removing the need to modify my code if I need to query an XML file, Oracle or MySQL Database, or even native .NET objects.

You can probably see a common theme here – WCF lets me focus on communication with the outside world without needing to write that interface or conversion functionality, and LINQ lets me access and manipulate data, without needing to write that interface either.

So, it’s all plug and play?

Well, that depends entirely on what you’re doing with your data. If you’ve got something like a CRM application where the client is responsible for managing (most of) the data, then yes it can quite possibly be almost plug and play if you’re going with a “CRUD” interface.

If your data structure is more complex, then you need to determine exactly where the split is. In this specific project, I’m presenting an abstracted view of the data that the client needs, and doing all of the business logic to manage data management in the SQL and Web Services Layer.

So far, the whole WCF and LINQ combination looks good. I’m hoping to post some more detailed posts later on.

Further Reading

I highly recommend Scott Guthrie’s LINQ to SQL series of posts. Start with Part 1: Introduction to LINQ to SQL

These resources have also been of a great help in getting my head around the whole LINQ thing:

Last week I got made an offer that I couldn’t refuse. 

Massive – the company that I’ve been working for as a contractor through the nice folks at Happener since November – offered me a full time position. I accepted, and I’m now a Senior Developer for Massive Interactive

That title sounds strange to me. Senior developer? Does that mean I’m over the hill now?
I suppose it’s somewhat similar to when I say I’m a .NET Developer, non-tech people generally go “Oh, you build websites”… not quite. (Hint: It’s a speciality in a certain set of technologies. Like saying you’re a Pediatric Nurse.)

Part of the role as a senior developer is to help provide direction to the more junior staff, so, that should be interesting to see how it works out.

Not much else has been happening – I’ve been busy with work for the most part. I’m still enjoying it, obviously.  It’s nothing like working for Telstra, which for me. is a really good thing.

What’s news with you folks?

Because people seem to be asking the same five or so questions about my new job, I thought I’d put up a FAQ.
I’m sure it won’t stop people asking anyway though :P

Who is the new job with?
It’s a contract position through an agency. Who their client is (where I’ll be working) I’m not saying yet – I’ll wait until I get to know the guys first. They’re located right in the centre of Sydney – 10 minutes from Central Station.

When do you leave / have you left Telstra yet?
My last day at Telstra is Friday the 26th of October (so, this week is my last).

When do you start at the new job?
Monday 5th November.

Are you commuting from Toronto?
Nope – I’m moving down to Sydney. A 3 hour commute *each way* really isn’t anyone’s idea of a good time.

Have you got a place in Sydney yet? / When are you moving?
Not yet. I’m staying with one of my Uncle’s first – he’s got a place about 15 minutes walk from the new job.
I’m looking for my own place at the moment, again somewhere near the centre of Sydney.

For over five years, I’ve held a bit of an open secret: I’m an alien from fluidic space.

Err, wait, let me start that again.

For over five years, I’ve been working for Telstra. I started off “on the phones”, working in a service call centre. Due to me being a smart-ass (and critical of some very inefficient systems) I was taken off the phones after about two weeks, to write some reporting tools.

From that first app in Excel 97 using VBA to generate charts, I converted to a full-time employee, and went on to bigger and better things. When I wrote that there’s a reasonably good chance of my code having touched your life in some subtle way, I wasn’t joking. The software I wrote helps people in Telstra do their jobs: Routing messages, generating reports, storing data, and keeping an eye on other applications.
I’m proud of the work I’ve done, despite it not being world changing or highly visible. Sure there’s some icky bits (VBA, Oracle, MS Access, Classic ASP), but overall I hope that it’s made people’s lives better, and/or their jobs easier, in some small way.

Today, I resigned from my position at Telstra. It’s not something I did lightly, but, after consideration I’ve decided I need to move on.

For those that are curious, I’m not going to be unemployed – Today I’ve also accepted a contract role to a digital media company in Sydney. I won’t say who, yet, until I’ve had a chance to speak with them some more, but suffice to say it looks like a great company to work for, doing interesting things and meeting interesting people.

Oh, and yes, this means that I’ll be moving from Newcastle / Toronto. I’m still at Telstra until the 26th of October and then I’ll be off to Sydney and new things.

I’d also like to throw a quick shout-out to Nick Hodge for putting in a good word for me, and listening to me rant a little about work; Jack Greenrich for plenty of coding advice and guidance; Ian Ward for getting me hired at Telstra and started down the software development path; and both Markus Hafner and Greg Dwyer of Happener Recruitment for helping me to get this new position.

Exciting times ahead, for sure…

The Gold Coast has put on some great weather – nice and cool at night, warm and sunny during the day.
I’ve taken a bunch of photos during Tech.Ed, I’ll upload them soon. In the mean time – Nick Hodge has heaps of photos on his photo stream.

I’ve attended a bunch of interesting sessions – but there’s a heap of information on offer, so it’s easy to overload.

Next year I think MSFT needs to organise a few more social-networking things around the events. For example, get attendees to put ‘teched07au’ tags on photos on Flickr, and blog posts, etc. Use SMS-broadcasts (possibly through twitter) to inform people of session changes and things like that (link it back to their commnet subcription).
I’ll probably think of a bunch of other small improvements as time goes on.

Overall, it’s been good fun the last few days, and I have learnt things which are relevant to my job, and which will help a little further on too.

I’ve also successfully avoided the vendors who want to steal my information so they can sell me stuff.

Updates – LOLCode.NET, Movieworld, Bye-Bye Developer Guy

_MG_6791 Nick gave his LOLCode presentation, to much incredulity by some people who attended.

Yes, LOLCode is a proper Turing complete language. And LOLCode.NET compiles into MSIL as well.

_MG_6936 Movie world was… interesting. About 3,000 people were packed into busses and trundled up to movie world for dinner and some rides.   There was the BatWing, Superman and a few others – we didn’t have access to the full park, but there was a large area open.












 _MG_6961 Homeward Bound



_MG_6990Frank’s “Catch Up with Frank” talk was interrupted so he could be serenaded to a version of Don McLean’s “American Pie” called “Developer Guy”.