10
Jun

When is a Technology Dead?

Previous logo of Microsoft Internet Explorer u...
Image via Wikipedia

I wish I could call IE6 dead.

I’ve spent hundreds of man-hours doing CSS fixes for it, and every day, I check Google Analytics to see how close we are to its death… and every day, I’m disappointed.

Technically, it is dead. Most standards say the latest 2 versions (of course, that got really big when IE8 came out, excellent excuse to drop it), and it’s 6 years old by now, well past the average lifespan of any technology. But, the problem is, for all of my idealism and complaints and loss of efficiency, we still have over 30% of our users on the ancient mind-breaker. So, unfortunately, for all of my complaints, for all of my IE6 specific cde and CSS fixes.. it’s not dead. It’s not defined by age, but by users. So until the time comes when IE updates become mandatory, or our users finally move on… it’s still very alive, in my nightmares and in my everyday coding experiences.

Reblog this post [with Zemanta]
05
Jun

APIs and Extensibility

Image representing Flickr as depicted in Crunc...
Image via CrunchBase

More and more often, it becomes obvious to me how important an external API is. What better way is there to share your product, then to let people build on top of your service layer and customize their own interface? If someone doesn’t like the look of your program, or how it feels, they may leave; but a missed opportunity can quickly turn into another user when they find someone else’s implementation of your application. Or, other applications may pull your data into their product, giving you another revenue stream (or just more users), more popularity, your name thrown around more; it’s free advertising and a great testimony to your product that someone liked it so much that they included it in their product.

I recently looked into Flickr’s API, for integration into a project I was working on, which spawned this thought. It is absolutely fantastic that I can call a URL with some credentials, and bam, I have the file I need. The user doesn’t have to upload (or worse, download from Flickr and reupload) to another photo-sharing application; they can just point out a url, and I can display it. It’s really awesome. Twitter has feeds, that I can pull into my blog; even my blog has an API that will allow other sites to post comments to me without ever loading my site. That’s pretty cool stuff.

For an information-hosting web app, this is one of the best things you can do to increase views and popularity. If you have a good service layer, expose some of it (with the right security, of course), let other people use your app. More users is never a bad thing.

Reblog this post [with Zemanta]
30
May

On Agility

...structures and vehicles of all sizes...
Image via Wikipedia

The most important quality of any IT company- web-based or otherwise- is the ability to quickly change, to turn on a dime. The openness and ability to foster innovation is absolutely critical, even expanding past IT companies; without change, you fall behind. And when you fall behind, it is only a matter of time before the inevitable collapse.

I read an interesting article in Wired yesterday about car companies. It suggested they become more like the computer industry, setting standards for components and allowing hundreds of parts manufacturers develop these sort of plug-in devices. These manufacturers would be smaller and agile, developing new, efficient parts, which not only helps the company sell more, but also gives consumers the chance to purchase better products. The big car companies would be like Dell, offering a sort of base upon which to customize and put together these parts.

The key here is that in a vertical company, where all processes are overseen by a massive beauracracy, is unable to change, while the hundreds of small parts manufacturers, overseen by a standards commitee, are each able to introduce breakthroughs in their respective areas. It is the same way with any IT company; one who is overseen by a large beauracracy is never going to stay with modern times. They are the ones still using IE6, to support their apps and unwillingness to change, while small 5-man companies are able to revolutionize the web with things like Youtube, Flickr, Twitter. When was the last time a large company built an app like that?

A lot of this requires upfront planning. The huge company is reluctant to change after investing millions in a system that is rigid; a properly planned system is one that is flexible; one should never think that you can build the perfect long-lasting solution. You can get close, but five years down the road, something will inevatably be superior and your app must be rewritten. Modularize your development and make this possible, because it is a matter of when, not if.

It is imperative that innovation is prized, that a company does demand absolute, 100% control, because when this happens, a company loses its character and becomes dead in the water.

Reblog this post [with Zemanta]
26
May

When Does a Framework Become a Language?

Unfolded tissue below a Kleenex pack. The Velt...
Image via Wikipedia

A friend of mine posed this question a few days ago: at what point does a framework become ubiquitous enough to be a language on its own?

This came after a brief discussion about jQuery, where the point was made that we hardly ever use traditional, raw Javascript anymore. We use jQuery to fix things,  jQuery to do UI effects, jQuery for validation. We hardly ever use the word Javascript. But, the question is, is jQuery the same thing as Javascript? Is it different enough to be considered something else, or should it just be considered a framework – the same way .NET is a framework to C#, or Rails is a framework to Ruby?

Our conversation came down to semantics. The same way we (or at least I) call tissues not by tissues, but by Kleenex, or the way Texans call soda “Coke”, and although jQuery does not (in a technical sense) replace  Javascript (rather, extending it), perhaps it is simply cognitive recognition that presses us to call anything Javascript related jQuery. Someday, will everyone call Javascript by jQuery? It very well could be.  We’re still not calling it ECMAScript.

Reblog this post [with Zemanta]
30
Apr

Zemanta is Awesome

Image representing Zemanta as depicted in Crun...
Image via CrunchBase

I wanted to make a quick plug for Zemanta; a utility that- I think, anyway- has helped me rapidly improve the quality of my blog posts. Yeah, the awful writing style’s still the same, but it allows me to throw in pictures, and pictures make everything better! It also has tools that link up key words to Wikipedia articles and other websites (all I did was select which words I wanted linked; I didn’t actually make the links on this post links manually), help you tag your posts, and give you a list of other blog posts that are related to the one you’re currently writing. It integrates perfectly seamlessly into WordPress, and gives you “reblog” links on other people’s blogs to quickly jump in and respond. I love the program; I highly suggest it to anyone.

A shameless plug, yes; but a worthy one.

Reblog this post [with Zemanta]