I’ve had luck with job postings for Questionmark in the past, so I wanted to mention that we’re looking for a web developer to join our team:
We are looking for a talented senior C# developer to join our development team in designing and creating the next generation of on-line assessment delivery software. The senior C# developer will work closely with a Product Owner and other team members (C# developers and QA) in a SCRUM (Agile) environment. They will be responsible for delivering potentially shippable functionality each Sprint using the latest technologies (ASP.NET MVC, WCF, .NET 4.0, etc.).
Our development teams are cross-functional and work in two week iterations. We use Visual Studio Team System 2010 to manage source code and other artifacts, and Visual Studio Lab Management to facilitate automated testing and deployment.
Our Edmonton office is located downtown in the Empire Building on Jasper Avenue at 101 Street, right above Central LRT Station.
You can view the job posting on Monster, or email me directly if you have questions or are interested in applying!
Since January I’ve been using a library called TweetSharp in my various Twitter-related programming projects (including my monthly stats posts). Not only has it saved me from all of the effort that would have gone into writing my own Twitter library for .NET, but it has also taught me a few things about fluent interfaces, OAuth, and other topics. Here’s the description from the relatively new official website:
TweetSharp is a complete .NET library for microblogging platforms that allows you to write short and sweet expressions that convert automatically to web queries and fly to Twitter on your behalf.
Maybe this is a generalization but I often feel that .NET developers get the short end of the stick when the “cool kids” release sample code for their APIs. Or more accurately, C# developers get the short end of the stick (because you can run Python, Ruby, and other languages on .NET if you really want to). Thus I’m grateful that Dimebrain (Daniel Crenna) has developed such a useful library.
TweetSharp is open source and under active development (hosted on Google Code), with a growing base of users reporting and fixing issues (I helped with the Twitter Search functionality initially). If you’re writing any kind of software for Twitter using .NET, you should be using TweetSharp.