A Person, Artist, Software Engineer, Geologist.

I'm Lazy. I don't want to write more code than I need to. I don't want to create a design that is too complex. I don't want to write "the next big thing", I just want to get the project done and make it a success. More code = more complexity = more debugging = more testing Even though I'll create bugs, I want them to be easy to fix, so I architect the design for each correction.  I don't want to be asked questions from other engineers on how things work so I make sure the class names, object hierarchy is clean and the operational processes are simple to understand. I don't want to have to hunt all over the code for related behavior so I group them by name or packages. I don't want to have to work late so I under promise and over deliver. I don't want to be confused so I ask stupid questions so that even I can understand what I need to do. I don't get too involved with shiny new objects because 1) too shiny and they distra

I've been revisiting HTML5 developing of late.  What I've found is three broad categories (I group by nature and habit), of current HTML5 development methods. They are: The tried and true, create your HTML page, add JavaScript and sprinkle with CSS.   Use "heavy weight" framework like Sencha's Ext-JS.  Heavy weight in sense of complexity and understanding.  Even for me it's a bit over whelming. Find a middle ground method that is in between the "build everything from the ground up" approach and the "kitchen sink" toolkits and libraries. I think I have found my "porridge that's just right" development method in the form of Enyo.js.  This is the framework that was born out of WebOS and is now in it's 2.0 release.  It's refreshing not to work in an all too common 0.999 release of a project and with the simplicity and clarity of design and implementation that eludes a project like Sencha EXT-JS. The Enyo.js co