Month: March 2014

The Death of Agile

The death of agile?

  • The skills and talents of individual programmers are the main determinant of software quality. No amount of management, methodology, or high-level architecture astronautism can compensate for a poor quality team.
  • The motivation and empowerment of programmers has a direct and strong relationship to the quality of  the software.
  • Hard deadlines, especially micro-deadlines will result in poor quality software that will take longer to deliver.
  • The consequences of poor design decisions multiply rapidly.
  • It will usually take multiple attempts to arrive at a viable design.
  • You  should make it easy to throw away code and start again.
  • Latency kills. Short feedback loops to measurable outcomes create good software.
  • Estimates are guess-timates; they are mostly useless. There is a geometric relationship between the length of an estimate and its inaccuracy.
  • Software does not scale. Software teams do not scale. Architecture should be as much about enabling small teams to work on small components as the technical requirements of the software.
    Coconut Headphones: Why Agile Has Failed

The Rest of the Story

My Babe Ruth

I did a demo of an ad-served mobile application-to-application deep link from a NASCAR app to a CNN app.

I pondered how to harness this new power.   Babe Ruth pointed to the stands before he hit that famous home run.  Here’s mine.

I want to get NASCAR to run a house ad that clicks thru to some CNN article that NASCAR values, via deep linking.

Like maybe this one.

Maybe CNN does a special page to highlight some NASCAR technology, so its a barter ad.  Maybe

NASCAR and CNN? I can hear your questions.  Yeah, it’s my destiny, and one day I’ll ping back to this post to prove it.  🙂