Moved to

After much thought and (a little) hand wringing, I have decided to move to the dedicated WordPress hosting platform. So far, it has been a difficult process to extract it from my Bitnami managed Amazon Web Services (AWS) account. But now that the process is complete, I look forward to a (much) faster website and perhaps fewer problems for me to manage.

I don’t like paying for something I can do myself, but time is also money in my world. Between a wife, three kids and 1 1/2 full time jobs, I will take the help at this point. I will update periodically with my experiences and overall thoughts. So far, it was easy(ish) to move my things over. The real problem was the ridiculously hard process of exporting my database from AWS. Bitnami makes the default phpMyAdmin secure by allowing only localhost access. Great. I love it. But, even after gaining “local” access for my laptop, it would not accept my password. After many attempts and an hour later, I just entered my WP database credentials and moved on.

I wish I could have that hour back.

I then followed the copious WP Engine steps for setting up my new install. Overall, it was fairly easy. The devs and product managers at WP Engine should be proud of their setup. From start to finish, it took me less than thirty (30) minutes. I have moved WP installs with iTheme’s Backup Buddy and they also took thirty minutes. The main difference is that iTheme will change your URLs for the new site while WP Engine assumes you are using the same one. It’s a safe guess, but not in my case. The Bitnami WordPress install script has everything under and I had to edit my database to gain admin access. Once that was accomplished, everything fell into place. Oh yeah, I already changed my DNS so it propogated more quickly. WP Engine tells you to test it out, but hey, I went for it.

Here’s to my first hour on WP Engine. I hope there are many more to come.

Flickr is Dead?

This is a developer’s worst nightmare. Spending your time to get an application to talk with another one just for the sake of it is hard to swallow. I understand it’s part of the development cycle. However, while you are working on the integration, who is iterating new updates to users?

And so when Flickr hit the ground at Yahoo it was crushed with engineering and service requirements it had to meet as per demands of the acquisition integration team. Those were a drain on resources, human and financial. Even though many of the resources came from Yahoo, they were debited against Flickr. This created an untenable cycle that actively hampered innovation.

How Yahoo Killed Flickr and Lost the Internet

Is Oracle Killing the Web?

Should this come to pass, numerous products will suddenly find themselves on an uncertain legal standing in which the previously benign but now newly empowered copyright holders might assert punitive copyright claims. Chief among these would be any re-implementation of an existing language. So, Jython, IronPython, and PyPy for Python; JRuby, IronRuby, and Rubinius for Ruby; Mono for C# and VB; possibly C for C, GCC for C and C and Objective-C; and so forth. And of course, all the various browsers that use JavaScript might owe royalties to the acquirers of Netscape’s intellectual property.

Oracle and the End of Programming As We Know It | Dr Dobb’s

This is certainly something to keep watching. If Oracle wins this fight, derivative works will dry up. Few volunteer efforts would risk a hefty legal bill for something that may/may not pan out.

Really sad.