Beauty Is in the Eye of the Beholder
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Case Study: IBM's Agile Transformation
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
If there was a point I didn’t get it! The evil side of metrics is neither new nor specific to software development. For instance, measuring students’ performance through exams can make some of them study towards assessment not learning. Does that mean schools should stop trying to measure student’s performance?
The title led me to believe that the presentation is about the metrics that fit well in agile mindset and how to use them. Did I expect too much?
You did not expect too much, and I think it's a fair criticism that we didn't spend as much time on the possible solutions to the metrics dysfunctions as we would have liked. Jim summarized the approach nicely, but we would have enjoyed examining many of the metrics that the audience brought up, and looking for ways to find alternatives, or to use the "measure up" approach to mitigate dysfunction.
Moving performance metrics up to the level where individuals (or the teams measured) cannot directly alter the measure is the basic approach. Anonymous reporting, and aggregating the values, prevents that dysfunction, and turns a motivational metric into informational. It can still be used to measure performance, but it's at a higher level, and resembles something that we would really prefer to optimize, rather than setting up an opportunity for local optimization (gaming the system).
We're still exploring these techniques, and I'm hoping to shift the balance of the talk from so many examples of dysfunction into examples of practical techniques to remove the dysfunction.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
Chris Richardson shows how he ported a relational database to three NoSQL data stores: Redis, Cassandra and MongoDB.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
2 comments
Watch Thread Reply