Skip to main content

Posts

Showing posts from October, 2011

The 10 Commandments of Efficient Coding.

I was recently asked for advise on how the manage a development project and decided to make it into a 10 commandments of efficient coding. This is ideal for any team size and if followed diligently leads to efficiently written code. Have any more that you would add to the list? Feel free to indicate yours in the comments below.
 Thou shalt spend at least 50% of ones time thinking about a problem before actually beginning any code. Conceptual design is critical to properly grounding the code in the ballpark of the problem being solved such that the solution spans the problem space as much as possible. Not attending to this stage could lead to spectacularly bad choices of solution for the scope of a problem. Thou shalt document everything. Every single thought on the development, ideas of implementation should be written down. I keep multiple "to do" lists in .txt files and as well in the memo field entries for my source control tool when I am checking in new code. Documentati…

The Return of the Space Cowboy, for Facebook

Because Facebook share widget refused to post this directly I had to "cheat". Apparently the video above contains a reference to the file sharing service "piratebay" in the video header and that prevented the Facebook link widget from allowing the share to embed. The reference is a solicitation to download the album at torrent bay and I agree such solication is wrong....but that is what the poster of the video intended...not what I intend. I just want my friends to listen to "Return of the Space Cowboy" the song I was humming this morning and thought...to find on youtube.

So, in a few seconds of being denied I figured I'd just embed the video in a blog post and link the post to facebook. My friends get to see the video as I intended and all is well with the world...of course I could have found another video reference to the song that didn't include any reference to PirateBay but then the question of "could it be done?" that sprang into …

Self Healing infrastructure means the end of a compensation requirement...

In a post I submitted to Facebook regarding the rise of automation and robotics and the fear of mounting unemployment a discussion occurred in the comments and the question below was asked by Bill Davidson:

"There will have to be a revolution in how we "compensate" people. "

In response I wrote the following hypothetical scenario in the vein of this post and this post that I've written that paint the possible future in a story. The gist being here that over time the *need* to compensate will become obsolete since the agents that we would be getting services from won't require payment. We like wise won't *need* to be performing work to get payment the self healing infrastructure that we construct would just provide it for us.

Imagine this scenario:

You go to bed at 11 pm and promptly at 7 am your robotic assistant raps at your door bidding you to wake. The assistant has already prepared breakfast which is waiting hot in your kitchen. You open the bedroom do…