A little over a year ago our local .Net User Group shut down (Maine Bytes).  The guy who had been running it for 10+ years decided he didn’t want to continue the work, and rather than find someone to fill his shoes he just shut it down (if you want to hear a rant ask me what I think about that decision).

Maine Bytes seemed to encourage passive attendance, not participation.  I’m not sure if was intentional or if it was the space (rows of tables facing the speaker) or just a vibe the group developed, but I frequently went and rarely talked with anyone. 

We all know the importance of being on time for meetings, and since scrum is designed to be a short meeting, if you’re 5 minutes late for scrum you can miss a third to half of it.

I’m a morning person, so I find myself most focused and most productive before lunch.  That often means that when scrum rolls around at 9:30 I can be totally lost in thought with no concept of time. 

This is my annual post where I publicly declare a few goals for the coming year.  Next year around this time I will take a look back to see how I did.  Looking back at last year I noticed that some of my resolutions didn’t have objective measurements, so I’m trying to include those this year.

It’s time for my annual resolutions blog post, but first I wanted to do a little retrospective to see how I did on last year’s resolutions.

This is a multipart series on how to share code between .Net platforms.  All the examples will be showing how to share between Windows 8 Store applications and Windows Phone 8 application, but the techniques are useful for sharing code between any .Net/Xamarin platforms.

1. Linked Files
2. Conditional Compilation
3. Partial Classes
4. Inheritance
5. Dependency Injection

What is Dependency Injection?

Dependency Injection is a form of inversion of control where the consumer of a service passes some of the objects on which that service is dependent to the service, rather than having the service create them.