For the past thirteen years I've been essentially self-employed in the software industry. First as a contractor, then as a consultant owning my own corporation; I’ve simultaneously had no bosses and a multitude of bosses. The freedom to take time off when I want to has been great, as has the chance to work from home and be around my kids as they grow up.
Starting June 9th I’ll be turning in my “screw-The-Man” badge and starting a full time gig at Microsoft. It seems like everyone is quitting the corporate world to strike out on their own, something I respect immensely – so why am I doing the opposite and becoming a cog in the machine?
- The siren song of a steady paycheck and benefits, benefits, benefits! Really great health insurance doesn’t seem like that big of a deal until you have a family.
- Working with people who understand building software (who get that you can’t expect a fixed bid when you don’t know what the product is supposed to do yet).
- Actually writing code instead of networking and constantly looking for the next job.
The new job will be writing code for OneCare. I won’t miss business programming – the SQL/SharePoint/Project Server/Office/Workflow/Reporting Services treadmill of Microsoft enterprise products I’ve fallen into working with recently. It’ll be fun to be writing a widely used consumer application again instead of the one-off stuff.
The blog has been paralyzed by worrying too much about what people think about what I write. I’ve been so concerned about writing stuff that seems pointless or trivial (or clueless) that I haven’t been writing at all. My blogging models have been all those frightfully smart writers who go on about language design and other stuff that makes my head hurt.
So it’s time to reboot the blog and quit overanalyzing. Writing makes me think critically and ultimately benefits me. If I’m lucky then something I write might prove useful or interesting to someone else. Poor misguided souls.