All posts in “Article”

AOTD: Predictions for 2012

The link:

Predictions for 2012

The meat:

I have none to offer.

People who really know what is going on are not going to prognosticate in public. Secrets will be held, profits will be made.

AOTD: The Internet of Things

The link:

Amazing Kickstarter Project Twine: Cheap and Easy Internet of Things

The meat:

The sensors, so far, include an temperature sensor and an accelerometer – with external sensors planned, including magnetic and moisture sensors.

I had imagined nano-particle magic dust… but we’ll have to wait until IPv6 for that. This is a great concept, but the devices are a bit bigger than I’d like. The day is coming and this is a great start.

AOTD: PHP Framework Bloat

The article:

The MicroPHP Manifesto

The meat:

Finding lightweight libraries that don’t pull in lots of additional code dependencies is much harder than it should be. Mostly I think that’s attributable to PHP devs being more interested in framework-specific development.

I’m seeing more and more of this “framework-specific development” out there. There are job listings for Symfony coders, Cake coders, Drupal coders (hah), but in the end, isn’t it all PHP with the occasional template engine thrown in? Don’t get me started on template engines for PHP, I think Smarty and the others have left the building with js engines kicking ass and taking names.. More on that later.

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.