How Do We Get Oil

Posted on May 14, 2010 by Kamen

Oooooh! So that’s how it works…

But seriously, it’s a damn shame companies aren’t required to have some kind of fail safe in place in case, you know, a rig completely fails. It’s tragic what happened to the workers on that rig and it’s tragic what is happening to our environment.

(via Fake Science via RVA Mag)

Posted in Uncategorized | Tagged , , | Leave a comment

Spending Cuts and Bake Sales

Posted on April 28, 2010 by Kamen

This…

Reminds me of this…

Posted in Musing | Tagged , | Leave a comment

Baby Plus Netbook

Posted on April 24, 2010 by Kamen

Isaac managed to open favorites, open the page source, and then hit some magic series of keys that resulted in a black screen with a blinking cursor. Not bad for a baby.

Posted in Baby, Geekish | Tagged , , | Leave a comment

Twitter Commits Suicide – A Response

Posted on April 21, 2010 by Kamen

If you kinda know what Twitter is or just asked yourself “what’s Twitter?” this will bore you.

Twitter recently unloaded a bunch of changes that have already been rolled out or will be making an appearance in the near future. Here’s the highlight…

  • Twitter built and released their own BlackBerry app
  • Twitter bought Tweetie, which is a very popular Twitter client for the iPhone
  • Twitter is teasing us with the new version of the website that is said to make Twitter desktop clients useless (the last part is one person’s opinion)
  • Twitter launched a new ad system that FINALLY answers the question everyone has been asking…” What is Twitter’s business model?”
  • Twitter MAY have their own flavor of URL shortening and Picture sharing services planned

Lots of stuff for one single bound in time, but it honestly makes sense for it all to come together in one fell swoop. Yay Twitter.. right? Not so as some see it.

Neal Wiser of twitip.com posted an article titled “Twitter Commits Suicide (or Twipocalypse Now: Redux)“. Go read it and then come back if you want…

Basically it states that all of these changes will ultimately result in the demise of Twitter.  The reason? Twitter is now competing with it’s own 3rd party developers. Meaning Twitter could potentially run most 3rd party developers into the ground. This part is completely possible. In fact, it’s very likely that developing apps for Twitter will no longer be the gold mine it once was. What I don’t understand is how Neal leaps to this being the catalyst to the demise of Twitter. Will some turn their backs on Twitter as a response to being bitten? Probably. There are even groups looking to respond with a service that will knock Twitter off of it’s pedestal. But will Joe Public even notice or care? Not likely. There are already services out there trying to do what Twitter does… and they are all wildly less popular than Twitter.

3rd party developers got the short end of the stick when all of these announcements were released, but these developers were not signed into any kind of agreement or guarantee with Twitter. They were simply given tools that allowed them to build apps that would interface with Twitter. Everyone, including Tweetie, had access to the same tools. The idea that Twitter will now have “Twitter for iPhone” is not a comforting thought for these developers, but if EVERYONE is allowed the same access to the Twitter API, shouldn’t Twitter themselves be able to release apps using that very API? I think that kind of protection for 3rd party app developers would not only be unreasonable, but would also hold Twitter back since not having an official app causes confusion for many users and makes the trial and error experience of “finding the right app” frustrating. Honestly, for each good Twitter app available right now, there are ten crappy apps. How is the average consumer supposed to wade through all of that? Alternatives will remain, but the Twitter app gold rush has come to an end. For iPhone, Atebits won with Tweetie.  Everyone else is free to find their niche spot in the alternative section or find the next service to develop for.

Neal also made a point about innovation. Now it’s true that if many apps fall by the wayside, you won’t have nearly as many developers pushing the innovation of Twitter apps and services. This will ultimately result in a slower “innovation curve” for the service. Personally, I don’t see this as a problem though. I think there is an unreasonable expectation for applications and services to almost reinvent themselves continually to remain relevant and popular. Twitter “has made it”. The changes they are making are specifically geared to maintain the giant they have built. If they reinvent themselves 10 times in the next 10 years, it is likely they will change so much, there will be no REAL resemblance to the original service. If instead, they do EXACTLY what they have done in making these changes, they will be tightening and perfecting a service that millions already know and love. Building and innovating is an essential part of life, but it’s just that.. a PART. The vessel is complete and Twitter knows it. Now all they have to do is maintain it well.

Twitter suicide? Not even. Pissed off nerds? Well, yes… but this is business. Twitter made a business decision and it changed how things will operate, but unless you are one of the developers with an app in your hand that is headed for the trash, you will benefit from this.

That’s my take. And if Neal is reading this, dude, we just disagree. No harm, no foul, that is all.

Posted in Twitter | Tagged , , | 1 Comment

WordPress You Pig

Posted on April 6, 2010 by Kamen

I know it’s been a while… been busy preparing to have / caring for and raising an infant child whilst freaking out about how to make my business thrive. So not much downtime. I do have to take a moment to talk WordPress however.

This is completely subjective. If you want a more technical “observation” of the software you may get nothing out of this.

I have been developing sites with WordPress since 2007 ish. Before then, I toyed with Drupal and Joomla, but settled on WordPress and have actually managed to money developing with WordPress. Let start with the things that I like…

  • Continually maintained – core updates are made regularly and the software itself continues to grow and mature. WordPress is vastly different than when I started with it and all of the changes are improvements that make my life easier and make using WordPress more enjoyable.
  • Huge community – this, again, is a constantly growing and maturing mass. Even if I confine myself to Richmond, VA I have a huge network of users and developers that are willing to lend a hand or give input. You can’t find that kind of support when a package of software has no community.
  • End user ease of use – this is VERY key to what I do. I am able to build and support sites that are mostly tended to by the end user. If it’s a more static site we’re talking simple page and widget updates. If it’s a larger site, we’re talking multiple posts a day. All of this is done SANS ME! Not to say I don’t want to get paid to do this stuff, but it’s important to let the end user do as much as they are capable/interested in doing. This keeps them from having to pay me for simple work that I have a hard time charging for in the first place.

And now the things I don’t like so much…

  • Add-On cat and mouse – this is not necessarily specific to WordPress, but keeping the core of WordPress up to date while maintaining ones needed plugins and themes can be a challenge at times. Generally everything is fine, but once in a while there’s that one plugin that totally eats it after an upgrade. The worst is when a developer discontinues support of their software and it is neither tested or proven on any current WordPress release. This is where having a giant community is not all that good. Lots of code sitting dormant and is likely useless.
  • Automatic Upgrade – if it worked with less pain, it would be great, but for every site on my dedicated servers, the FTP info seems to NEVER work. The result? I must pass ownership of WordPress to the webserver to allow for this functionality. I do know the FTP option works, but it’s not bulletproof and I have always had trouble with it. Also, end users that know enough will get into this and try to update everything. Great idea in theory, but when I hardcode ***DO NOT UPDATE*** in to the plugin description… it’s for a reason.
  • Ads!? – where is the native support for ad integration!? This is why I constantly look for other options and end up with other bloated open source software to serve up ads. I feel it is likely ads could be served within WordPress more elegantly and more quickly if the ability was built in. Instead, I must maintain a completely separate package of software dedicated to ads. The solution works, it just seems to me it would be a nice thing to have in the core.
  • WordPress is kind of a pig – this is the big one. Even a default, no plugin, no theme installation of WordPress runs painfully slow out of the box. I have a handful of small sites running WordPress for the positive reasons above. Some are on shared hosted services like GoDaddy and some are on my dedicated boxes. These small sites run terribly considering the small amount of info and graphics being served up. Crank it up to a big site and you are in for a frustrating treat. Seriously… an installation of WordPress serving up a static page with a few small graphics and some text should load instantly, but instead it takes a little too long making the whole site feel sluggish. Now, my main problem is on the larger scale of things. Running a big site that is graphics heavy (ish) with dynamic content added on a daily basis with WordPress is a task. Throw a busy day at this setup and there is little one can do to keep things from completely falling apart. When I say busy… I mean maybe 3000-4000 pageviews in an hour. This is not terribly huge in the grand scheme of things, but no doubt it’s pretty busy. WordPress does not have native static caching built in, so one must bang their head long enough to coax WP-SuperCache working. WP-SuperCache works well, but again, it seems to me this should be handled within the core to allow for much cleaner setup and handling of caching.

I have run WordPress on everything… shared hosting, VPS, random box at my house, and on dedicated servers. It never really changes the experience though. It takes an awful lot of work to make WordPress run well in my experience and the most unfortunate part about that is when I go to research solutions, 90% of what I find is information about WP-SuperCache. WP-SuperCache is fine, but it’s not the definitive solution. I see it patching a problem, not adding a feature. Stability under load should come in the box, not as an add-on. I guess I have reached “the next level” and maybe, possibly, I am on that bridge between hardcore coder and WordPress tinkerer, which is why I find this such a challenge. At the end of the day… I see my servers cringe when the loads are high and after throwing a ton of hardware at it, I see improvements, but can’t help but to think that the content should be able to run with much less hardware. So even though I continue to make it over the hurdles, I keep thinking it shouldn’t be THAT hard. I love WordPress… but only because I overlook the faults. I just hope I am not the only one that thinks this. Maybe WordPress is still approaching greatness and I am just being an impatient nerd, complaining on my blog.

Posted in Wordpress | Tagged , , , | 6 Comments