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.
Posted by Abel Avram on Jul 29, 2008
In this presentation, Rebecca Wirfs-Brock presents some practical lessons she has learned from doing architectural reviews. Many times projects are not delivered in time, or have quality problems or have an incomplete set of features due to architectural flaws. The reviews are meant to highlight existing risks and strengths of the architecture, and to reveal issues initially neglected.
The hardest to do 5 things Rebecca learned from reviews are:
The entire presentation is 58 minutes long.
Agile Development: A Manager's Roadmap for Success
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!
Thanks rebecca for sharing these lessons with us. I have noted all of these and am going to consider these while I undertake reviews of architecture or present my own architecture designs for review. we have also experienced some of these things mentioned by you - especially the first one. Majority of people consider architecture review (audit) as a means of validating the technology choices.
it would be great if you can also share some of your experiences of design reviews of object oriented applications! This would be of great value considering majority of architects are regularly engaged in application designs using object oriened paradigm.
This is a very good presentation. I have been looking for something like this for quite some time. I would like to learn from your experience on how to effectively deal with the situations where cost becomes a barrier to architecture.
There was about 20 minutes of content in this presentation, if that. The presentation style was poor, with the speaker exuding tension and nervousness. If the unit test I was running had finished sooner, I wouldn't have watched the whole thing.
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.
3 comments
Watch Thread Reply