Collaboration: At the Extremities of Extreme
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.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
What a joke.
Its a shame that the economy is so bad, that unknowledgeable persons like the one above have to talk a few buzzwords and make their living.
Thumbs down. Worst slides and presentation.
I am agree 100%.
SOA has lost all hope of reincarnation (a good thing). Whoever attended that conference session got ripped off. My full thoughts, here: www.benjaminbooth.com/tableorbooth/2010/02/soa-...
The maxim of "SOA does not add value if you blindly go out and buy SOA technology stacks" was already beaten to death "ages ago" by Martin Fowler, James Webber and the like. This presentation could have been extended to some extent with some of the general best practices of successful SOA architectures, conversation patterns, schema designs and the like.
Also it could have been extended with how some SOA stacks have added business value to clients (in what problem domains and what environments). These could have been really interesting.
Without that, all that I seem to be hearing is motherhood and apple pie. :(.
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.
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.
5 comments
Watch Thread Reply