InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Ruby x Agile: Matz explores the relationships between Ruby and Agile

Posted by Sam Aaron on Jun 12, 2007

Sections
Process & Practices,
Development
Topics
Ruby ,
Agile ,
Agile Techniques
Tags
LISP ,
Python
Ruby creator Yukihiro Matsumoto recently starred in the first of six short videos exploring the relationship between Ruby and Agile methodologies. Matz features along with Kenji Hiranabe and Shintaro Kakutani. Kenji is a self confessed ‘Agile agitator’ and Japanese translator of multiple XP/Agile books. Shintaro is a strong Ruby proponent.

This first video explores the relationships between Java, Ruby and Agile. There is a particular focus on why they feel that Ruby and Agile are a good combination, and aims to illustrate how they both offer a more human, and less rigid approach to software development. It ends with a discussion describing how they feel that in five years time, Ruby will used heavily in real business:

“I’m from C++ and I first wondered whether Java would really work in business applications because it has too much indirection [such as the] virtual machine, but the CPU specs and the internet speed increased very fast and they exceeded the overheads of the indirection. And Java really worked. I’m pretty sure that the same thing happens again and it will make Ruby work for business applications in the very near future”

It starts by contrasting the timelines of Java, Ruby and Agile, making some interesting comparisons between the static nature of Java and non-agile development methodologies. As an example they describe Entity Java Beans:

“EJB is, in a sense, a huge legacy wrapper between old relational databases, its configuration is complicated and redundant.”

The timeline comparison sets the context of the conversation, and provides a platform with which they explore the social relationship between Ruby and Agile. They discuss the role of key figures such as Dave Thomas and Kent Beck, such as the introduction of the pick-axe book in 2000, and the Agile initial ‘bubble era’ of 2001/2002. They then discuss the apparent synchronisation of ‘booms’ between Ruby and Agile. These booms are indicated with a large increase of usage, exposure and associated literature.

When asked about the meaning of the title, Kenji explained:

“The title was originally Ruby + Agile, but recently in Japan, ‘x’ is [a] more cool saying, and it means ‘versus’ sometimes used for discussion and of course [it] makes more than [the] sum.”

This is not the first time that such a comparison has been explored. At the recent RailsConf Alan Francis explored the similarities between the Rails and XP movements. According to DHH, he explored the similarities “on a higher plane of approach, angry teenager-tendencies, and peaks.”

Part 2 and 3 of this video series break down as follows:

  • Part 2: Resonance of Business-Process-Framework-Language, why?
    • 2-1: Focus on the shift from CPU power to Human power
    • 2-2: Agile and Market meet
  • Part 3: Rubyishness
    • 3-1: What makes Ruby Rubyish ?
    • 3-2: What Ruby does and doesn’t inherit from Lisp
    • 3-3: Lisp, Python, and Ruby

They are currently working on parts 4-6. The first video is available here

Related Sponsor

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!

No comments

Watch Thread Reply

Educational Content

10 tips on how to prevent business value risk

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.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

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.

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.

Architecting Visa for Massive Scale and Continuous Innovation

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.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

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.

Questions for an Enterprise Architect

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?

Wrap Your SQL Head Around Riak MapReduce

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.