A central presence, structured to adapt with a few fixtures from my sandbox.
What have you been up to?
The hunt is on... Looking for the next good gig.
Have been thinking about the synergies between BI and web development. So many (even smallish companies) have long been utilizing intranets for information delivery. Coupled with the biggest players in BI developing rich web delivery for dynamic graphical and tabular data - the history of these technology implementations has long been one of mutual dependence... Why? So much of today's customer inputs are accumulated from web applications. The purpose of interaction, who is interacting with an organization's website, was the experience successful? Understanding these traits is key to customer facing businesses.
Many times, questionable data can be linked back to poor behavior of the source web application. The mechanics of interacting with a corp site on the web define the sort of data the host makes available...
How are the kids?
We're headed into the school year home stretch. Most parents would agree (tho few want to think about it); Spring, and school year end, are more hectic than the holidays. Between school plays, recitals, final projects and the daily ball practice, scrimmages, games. This year i'm making a Spring project plan - we'll see how close we get on achieving our goals.
The Thirty Minute Task
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...
If you looked up aepdev to find out more about Tony, have a look at some of the writing or résumé. Cheers!