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.
Presentation
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
Lessons Learned from Architecture Reviews
Presented by
Rebecca Wirfs-Brock
on
Jul 29, 2008
Length 00:57:31
How would you like to view the presentation?
In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
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.
Bio
Rebecca Wirfs-Brock invented the way of thinking about objects known as Responsibility-Driven Design. She is lead author of the classic Designing Object-Oriented Software, and Object Design: Roles, Responsibilities and Collaborations. She is the design columnist for IEEE Software and past board member of the Agile Alliance.
About the conference
JAOO is the premier European developer conference on software technology, methods and best practices. The conference presents in-depth presentations and tutorials by researchers, engineers and trend-setters in software engineering and technology.
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.
Bio
Rebecca Wirfs-Brock invented the way of thinking about objects known as Responsibility-Driven Design. She is lead author of the classic Designing Object-Oriented Software, and Object Design: Roles, Responsibilities and Collaborations. She is the design columnist for IEEE Software and past board member of the Agile Alliance.
About the conference
JAOO is the premier European developer conference on software technology, methods and best practices. The conference presents in-depth presentations and tutorials by researchers, engineers and trend-setters in software engineering and technology.
RelatedVendorContent
Transforming Software Delivery: An IBM Rational Case Study
18 agile and lean practices for effective software development governance
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!
Thanks for sharing the experiences
by
Dinkar Gupta
Posted
Cost versus good architecture
by
Prasanna Nippani
Posted
Painful
by
Randall Cook
Posted
-
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.
3 comments
Watch Thread Reply