Archive for December, 2011

AOTD: Cyclical Code Quality?

The link:

Quality Coding Takes A Break For The Holidays. But Why?

The meat:

For the time period I looked at (the last 24 months), January through September is relatively flat and in line with the average flaw density. Then, there is a big bump in flaw density in October and November. Things begin to settle down once we go into December. The jump in application flaws is easy enough to spot. But what could cause this?

As a commenter points out, this probably has to do with deliveries schedule for Jan. 1. Seems like October and November are big push months with a lot of testing/debugging. December is polish and deployment.

AOTD: Compiling into another language

The link:

A Case Against Using CoffeeScript

The gist:

I make far greater use of the debugging tools in pure JavaScript because my brain can stay in the exact context it’s been in the whole time, in the code I wrote–not to mention I can copy/paste my code into the console to see if it works better right then.

Beautifying a language to make it more readable only to suffer the consequences of obfuscated output that is nearly impossible to debug is a recipe for disaster. I’ve been down this road too many times and it amazes me that people just don’t get it. Bytecode is a different story without the leaky abstraction.

AOTD: LinkedIn and dust.js

The link:

Leaving JSPs in the dust: moving LinkedIn to dust.js client-side templates

The story:

Javascript templating using dust.js. The server only serves up JSON and the CDN-loaded template engine (dust.js) pulls apart the data to fill in data for the browser to render. Moving more towards thick clients. I like it.

Article of the Day

I’ll start posting links to the single most interesting thing I read per day. So expect this to peter out in a couple weeks as all my other blogging efforts have…

So for today, check this out:

A Missive on Native Client

And here is the money paragraph:

At that stage, what they have is a fixed platform that they own (NaCl), which is sufficiently powerful enough for regular developers to target and migrate any old code to (e.g. just rebuild your desktop Qt app), and access to the local machine is suddenly gated through them entirely (e.g. they become the new Microsoft, except multi-platform). In such a strong position, the usefulness and overall purpose of the otherwise seemingly lingering Chrome OS[7] should now be clear.

Wow. Suddenly a lot of things start to make sense. I doubt Google could pull a fast one like this over the entire developer community, but look how far they’ve already come. Wow.