Content here is by Michael Still mikal@stillhq.com. All opinions are my own.
See recent comments. RSS feed of all comments.


I'm paid to work as a Windows developer, which means that we've started to care a lot more about Microsoft .NET and languages like C#. I also play with mono on Linux when the mood comes upon me.


Sun, 16 Apr 2006



Tech talk blogs

posted at: 21:00 | path: /dotnet | permanent link to this entry


Tue, 14 Mar 2006



TechTalkBlogs

posted at: 10:15 | path: /dotnet | permanent link to this entry


Thu, 29 Sep 2005



Robert Scoble is right, Microsoft has abandoned a lot of their developers

posted at: 15:15 | path: /dotnet | permanent link to this entry


Tue, 23 Aug 2005



Unjustified fun making

posted at: 17:58 | path: /dotnet | permanent link to this entry


Sun, 21 Aug 2005



Clarke, you need to look into things a little before mouthing off

    Clarke Scott (who once applied for a job as a Microsoft evangelist, although we should note that I don't hold the Microsoft job application moral high ground) blogs about repeats verbatim without verification a post from a Microsoft evangelist based in New Zealand about Linux Australia's support for Linus' trademarking of the Linux trademark in Australia. He ignores of course that Linux Australia has been running one of the most successful Linux community events in the world for the last four or five years, or that Linus is genuinely behind the trademarking effort. He doesn't look into how the Linux Mark Institute (the international body behind the trademark) is structured. Or what their goals are.

    He just comments that the community is less free as a result.

    Windows is a trade mark too. How does having Linux trademarked any more restrictive that Microsoft owning the Windows mark?

    Update: Clarke commented on this post to mention that I had missed that this was a quote from another site, which I am happy to concede. He also suggests the post was tongue in cheek, despite the fact that I can see no indication of that having re-read the post.

    Update: Fixed broken link

    Tags for this post: dotnet linux trademark
    Related posts: Trademarking colours

posted at: 22:57 | path: /dotnet | permanent link to this entry


Wed, 17 Aug 2005



Getting ASP.NET working on Windows XP Tablet PC edition

posted at: 23:34 | path: /dotnet | permanent link to this entry


Thu, 11 Aug 2005



I didn't get my shirt!

posted at: 01:09 | path: /dotnet | permanent link to this entry


Mon, 08 Aug 2005



Funny

posted at: 14:14 | path: /dotnet | permanent link to this entry


Tue, 19 Jul 2005



Microsoft TechEd flair

posted at: 21:17 | path: /dotnet | permanent link to this entry


Mon, 18 Jul 2005



The state of Microsoft certification

posted at: 15:20 | path: /dotnet | permanent link to this entry


Names for longhorn

posted at: 15:15 | path: /dotnet | permanent link to this entry


Sat, 02 Jul 2005



On caching of websites

posted at: 23:46 | path: /dotnet | permanent link to this entry


Wed, 29 Jun 2005



Exceptions in Web Services

posted at: 00:31 | path: /dotnet | permanent link to this entry


Hiring good people and FinalBuilder

    Mitch comments on hiring the right people and the process that Readify uses. He mentions that it's important to have a balance between the points on Tate's hit list, which is of course right. Based on my two Microsoft interviews now, I must say that they focus a little too much on the theoretical problem solving skills, instead of looking for raw talent, or an ability to talk to customers, or read existing code. They've really focused on one of the things on that list.

    It's kind of a self fulfilling prophecy, in that people seem to assume that the process that hired them is by definition the best process to use to hire a new person (presumably who will be like them).

    Oh, is there a way in FinalBuilder to send an email when a build step fails but has "ignore failures" checked?

    Tags for this post: dotnet hiring finalbuilder microsoft
    Related posts: Collect the whole set; Calling Tate Needham, or, Hiring in Canberra; Troubles hiring people

posted at: 00:24 | path: /dotnet | permanent link to this entry


Tue, 28 Jun 2005



Microsoft TechEd 2005 flair

    In a blast from that restaurant in Office Space, Microsoft has been providing "flair" for peoples blogs when they attend their events for some time. For example, here's the proposed flair for the TechEd 2005 conference:



    Apart from the fact that flair seems like a good idea and perhaps should happen more often, I thought it might be time to do some re-mixes of the TechEd flair. Here's the one for my Windows based workplace:



    And here's the one so that my nerdy friends don't make fun of me:



    Tags for this post: dotnet microsoft teched conference flair
    Related posts: Microsoft TechEd flair; Funny; I didn't get my shirt!; That's one way of doing it...

posted at: 17:58 | path: /dotnet | permanent link to this entry


Wed, 08 Jun 2005



Wrapping a COM IStream into a .NET Stream

posted at: 01:05 | path: /dotnet | permanent link to this entry


Mon, 30 May 2005



Prior art needed: Microsoft patents XML Serialisation

posted at: 21:36 | path: /dotnet | permanent link to this entry


Fri, 27 May 2005



Microsoft not rewriting their products in .NET?

    "Of course I still find this incredibly ironic. Microsoft insists on re-using it's own source code, and even given the ease with which they can step into Managed C++, they still preserve their existing code rather than go through the time and expense of shifting to .NET. Yet for their customers, millions of VB developers, they abandon them and leave them no choice. Funny how there's one rule for Microsoft's source code and yet another for their customers."
    Quoting Bill.

    I see the same push from Microsoft to port for us C programmers as well. As best as I can determine Microsoft has no intention of porting their own code away from unmanaged C / C++, but they are certainly applying a lot of pressure onto ISVs to do just this. The other thing that an ISV has to bear in mind is that a port makes you inherently less competitive -- you end up spending a bunch of engineering effort to recreate your current product, instead of adding those new features that the customers have been asking for.

    Tags for this post: dotnet microsoft unmanaged managed .net port
    Related posts: Getting ASP.NET working on Windows XP Tablet PC edition; Profiling your code in mono; SQL Down under; Open sourcing WinForms code?; A small example of how to find all the properties on an object using .NET reflection

posted at: 01:22 | path: /dotnet | permanent link to this entry


Fri, 20 May 2005



Product feedback center

posted at: 21:52 | path: /dotnet | permanent link to this entry


Wed, 11 May 2005



Profiling your code in mono

posted at: 03:00 | path: /dotnet | permanent link to this entry