Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

What Developers Can Learn From the Past

DZone's Guide to

What Developers Can Learn From the Past

Most of the time we need to be reminded, not taught.

· Web Dev Zone
Free Resource

Add user login and MFA to your next project in minutes. Create a free Okta developer account, drop in one of our SDKs to your application and get back to building.

I was asked, amongst many others, "what can developers learn from the past" by .net magazine some months ago. Alas, my response was way, way over budget, so I've posted it here in it complete form.

DRY: Don't repeat yourself. But I don't mean DRY code, it's actually much simpler than that.

Recently there was a fun code search that revealed the reason why the next version of Windowswas going jump from 8 to 10: if (os.startsWith("Windows 9") ... a mass of code that showed hard-coded lines attempting to match Windows 95 and Windows 98.

This search shows a huge amount of legacy code that relies on a string matching that didn't consider at the time there might be another Windows 9x. Understandable the first time around I guess.

This is reminiscent of the browser sniffing days that aren't that long forgotten. Remember when Opera was the first browser to hit double digits in its version? They shipped with a user agent that had both Opera 9 and Opera 10! The reason behind this madness: browser sniffing (done poorly I might add).

We Repeated These Mistakes.

More recently (in 2012) there were concerns about vendor prefixes and non-WebKit browsers adopting WebKit prefixes because we developers kept including a single vendor prefix.

Bruce Lawson has an excellent 20 minute talk on lessons we (should have) learned from the days of "Works best in Internet Explorer." IE6 won the battle of the browsers because we refused to code for the "older" browsers. Similar to vendor prefixes, eh?

We Repeated These Mistakes.

If you notice the reoccurring themes at conferences and discussion around the future of websites on the web, it seems progressive enhancement is having a resurgence—as if it should! It should be baked into our development workflow.

There's been a recent surge of "blank page sites." And certainly, "You need Safari/Chrome to view this site properly." Poppycock.

We Repeated These Mistakes.

So, if we can learn anything, I'd say: if it feels easy, and has a stink of not being future friendly, then you should consider aborting your current path and start again. It'll be worth it. You won't repeat those small, but non-trivial mistakes.

Don't tell yourself that just because Google is able to crawl your JavaScript it's an excuse to get lazy. Google isn't the prevailing entity here; you, your work, and your legacy is.

What can developers learn from the past? Don't repeat these mistakes.

Launch your application faster with Okta’s user management API. Register today for the free forever developer edition!

Topics:
best practice ,learning

Published at DZone with permission of Remy Sharp, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}