transiting to node - aka under construction, seeking purpose...

Thank you for dropping in...


Links here will begin leading to work product exemplifining expertise in data capture, transformation, security and aggregate reporting.

What's happening?

Readying the children for back-to-school while honing node, spark and tableau chops. Having a blast putting a private team together with the oldest boy. He's working on an image processor parsing grocery reciepts for dissimination as food intake. Key strut to our budding health app.
Watch these pages for more soon!

What's Cooking?

Peppers in everything.

updated by Tony July 31, 2017
Tags: intro

The Thirty Minute Task

the clock is ticking

There's lot's of thought around efficiency in coding. The actual writing of code, as well as its structure and content.

"extreme" programming, pair programming, lean, agile, "scrum" for efficency and close control of developers... C, java, ruby. Python, struts, rails - these attempt to force structure and frame content by limiting syntax, promoting "convention", rudimentary functionality is generally provided for along an mvc line; sill you write the rest to serve whatever business need.

Enter the Task

All of these particular methodologies and programming languages have more similarities than differences when viewed from orbit. They are all shiny marbles that may be shot in any direction. So how to take the shot? We build diagrams, define individual actions and state transitions, map how things are to be hooked together. Lot's of stuff to do. So we break the project down into tasks and start writing.

Lately, friends have been talking about limiting individual tasks to 30 minutes. Only take on what can be completed in 30 minutes. Seems a bit idealistic to put everything we're ever going to build into a string of sitcoms with commercials.

Ahh; the TV metaphor - perfect. How about "drama" tasks (60 minutes), sitcoms (30), news bulletins (15), commercial break (3) and for the rare headphone on code cranking session, a movie of the week (120 minutes)? By definition, movies of the week would be rare for the team...

I'm an adherent to the 20 minute task, but most problems require three or four of 'em to resolve. Will think on this some more and get back...

updated by Tony April 3, 2010
Tags: development, questions, comments