Cool Code
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Mike Bria on Oct 15, 2008
Talk about agile can often tend toward the tangible things that people do day-to-day, toward the "process of agile", but true agility is really less about process and more about principle. Travis Birch presents his perspective about some of these more intangible aspects of agile, namely "truthfulness".
At it's heart not a revolutionary statement, but Birch presents a refreshing and succinct reminder about a fundamental undercurrent of effective agility, truthfulness:
Agile methods are made of processes, principles and tools. But most importantly they are concerned with people. Therefore, Truthfulness is the foundation of success in an Agile organization.
Although Agile cannot force people to be truthful, it reveals the direct consequences of opacity in an organization, confronts it and challenges it to change.
...
Agile exposes the true character of an organization’s culture and forces visibility on all levels.
...
Agile can be implemented anywhere people do work together. Visibility of work, openness of consultation and a strong collaborative spirit feeds an overall feeling of excitement and optimism in an Agile team. [...] But of course, in order for a team to build up these capabilities, it must establish, maintain and defend a firm and immovable foundation of truthfulness.
Surrounding this central point, Birch presents a quick-hitting description of some of the other intangible fundamentals of Agile. A few highlights of these points:
Take a moment to check out Birch's take on what really makes agile special, you may find it to be a refreshing reminder for yourself or for someone you know.
Case Study: IBM's Agile Transformation
SCM best practices for multiple processes, releases & distributed teams
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!
Sounds interesting... was there supposed to be a link to Travis' original work?
Dave Rooney
Mayford Technologies
Duh me!!! Yes, that's the link. Thanks Dave!
Mishkin Berteig (also of agileadvice) has done some thinking on the subject. See: www.infoq.com/news/2008/07/truthfulness-agile-v....
Therefore, Truthfulness is the foundation of success in an Agile organization.
This does appear to follow the whole "agile = good" train of thought.
I hate to be the cynic, but it turns out that truthfulness is the foundation of success in any functional organization.
Peace,
Cameron Purdy | Oracle
www.oracle.com/technology/products/coherence/in...
Cameron, your point is completely accurate.
I suppose my take is that, frankly, agile methods place a much more real emphasis on doing things in a way that optimize an orgz awareness of the truth, and moreso then a greater emphasis on requiring people acknowledge and react to it.
No doubt, "truthfulness" is critical to success (or failure) of any organization - so is "quality" and "customer value", among other things. The (admittedly subjective) case is that agile places a higher value on acknowledging that.
(BTW, I appreciate your sense of humor!)
Cheers
MB
With Mike in response to Cameron... it is funny to think about how truthfulness is critical in any functional organization or process, but many of us have seen how untruthfulness can survive for quite a while in a gamed system. I spent two years in a global 50 company where managers remained in power using untruthfulness to survive before the real issues were exposed and some of them were removed.
Agile provides much more to keep this from happening.
Kevin E. Schlabach
agile-commentary.blogspot.com/
.. yup, there is quote a bit of dysfunction in the world of business, and it always amazes me how dysfunction can exist for years in a company without killing that company!
Peace,
Cameron Purdy
Oracle Coherence: The only Real-Time Data Grid
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
8 comments
Watch Thread Reply