← All articles
misc

I’ve Moved to WordPress

Why a die-hard .NET developer moved his blog to WordPress -- BlogEngine.NET kept breaking on RackSpace Cloud, and it was time to use what works.

Donn Felker

Donn Felker

2010.01.28 · 1 min read

I’ve moved my blog engine once again. I started with DasBlog, then went to BlogEngine.NET and now I’m finally on WordPress.

Why WordPress? You’re a .NET guy …

Plain and simple. What I had, didn’t work and I need my blog to work, and work quickly. I don’t have time to write plug-ins, hacks to fix something I didn’t write simply so I can communicate with everyone via my blog. I need a solution that allows me to fire up my blog or Live Writer and create an entry very quickly.  I need a solution that allows me to add the new whiz-bang widget created by Developer X. I don’t want to be a blog widget developer,  I am an entrepreneur. My time is better spent figuring out business problems with code.

Secondly – My Host, RackSpace Cloud didn’t work well with Blog Engine .NET. I spent 3 hours trying to figure it out with their support team and they said the problem was my fault, I said it was their fault and we went back and forth. When it comes down to it, the problem was that when I created a new post, a new xml file was created in APP_Data and it was not being propagated across the cloud. Some users would see my post, others would not. A royal PITA.

Long story short. Yes. It’s WordPress. Yes. Its PHP. Yeah, I’m running this on Apache. Yes, I write .NET software for a living. But as I said in my last post, go with what solves the problem. Use what gets the job done. WordPress does that for me right now. Who knows, that could change in the upcoming years.

Donn Felker

Written by Donn Felker

I've spent 25+ years shipping software, writing books, and running my own companies. I write about thinking clearly, working for yourself, and doing real work while AI rewrites the rules. New essays land here every week.

Get the newsletter

Keep reading