All content and news on InfoQ about Antipatterns
Latest featured content about Antipatterns

- SOA
- Topics
- Design
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them: tunneling everything through GET or POST, ignoring caching, response codes, misusing cookies, forgetting hypermedia and MIME types, and breaking self-descriptiveness.
-
By Stefan Tilkov
on Jul 02, 2008,
News about Antipatterns
- Architecture
- Topics
- Customers & Requirements,
- Enterprise Architecture,
- Design
As it gets more and more difficult to adapt software to new demands, the temptation to rebuild it in order to update the architecture grows stronger. For this risky undertaking it is essential to choose the right strategy. Several authors provide insights into advantages and disadvantages of different possible options in terms of cost, technical complexity and potential commercial risk.
-
By Sadek Drobi
on May 09, 2008,
- Agile
- Topics
- Leadership,
- Teamwork
Fiona Charles' recent StickyMinds article looked at leading troubled projects. Stressing that "this is not the time for rigid process over progress," she provided valuable insights to help a team turn around a troubled project. She also reminded us to watch out for improvement: if there is none it could be a Death March, and time to leave.
-
By Vikas Hazrati
on Feb 22, 2008,
- Architecture
- Topics
- Domain Specific Languages,
- Enterprise Architecture,
- Design
Often the necessity to rapidly adapt software projects to new clients’ needs results in adopting approaches focused on productivity. Reasons, implications and limitations of this were recently discussed in the blog sphere.
-
By Sadek Drobi
on Jan 04, 2008,
Articles about Antipatterns

- Agile
- Topics
- Delivering Value,
- Customers & Requirements
The role of the Scrum Product Owner is powerful, but challenging to implement. Success can bring a new and healthy relationship between customers/product management and development, even competitive advantage, but it comes at a price: organizational change is often required. In this article Roman Pichler looks at what it takes to succeed as a Product Owner.
-
By Roman Pichler
on May 14, 2008,

- Agile
- Topics
- Methodologies,
- Stories & Case Studies,
- Adopting Agile
This recent inquiry, by InfoQ China editor Jacky Li, picked 5 very different cases of Scrum adoption in China, which got different results, and asked: Why did you use Scrum? How did you adopt it? What problems did you encounter, and why did it succeed or fail? Despite the small sample size, it's an interesting comparison, pointing out that improvement doesn't ensure success.
-
By Jacky (Jian) Li
translated byJacky (Jian) Li
on Apr 16, 2008,

- Agile
- Topics
- Collaboration,
- Teamwork,
- Leadership
We miscommunicate every day, with results ranging from trivial to catastrophic. In this seasonally themed article, J. B. Rainsberger shares one of his secret weapons - the Satir Communication Model. It's a thinking tool to help us analyze troubling conversations, and to more deeply understand the people around us, building trust, the first step towards building an effective team.
-
By Joe Rainsberger
on Dec 23, 2007,
Interviews about Antipatterns

- Agile
- Topics
- Delivering Quality,
- Unit Testing,
- Agile Techniques
Debate sprang up at JAOO '07 around Bob Martin's assertion that "nowadays it is irresponsible for a developer to ship a line of code he has not executed in a unit test." In this InfoQ video, he debated with Jim Coplien on this and other topics, including Design by Contract vs. TDD and how much up-front architecture is needed to keep a system consistent with the business domain model.
-
By Jim Coplien and Bob Martin
on Feb 18, 2008,
Presentations about Antipatterns

- Agile
- Topics
- Delivering Quality,
- Delivering Value,
- Agile in the Enterprise
Scrum co-creator Ken Schwaber spoke at Agile2006 on code quality as a corporate asset. InfoQ presents video of his talk, The Canary in the Coalmine. Schwaber discussed how a degrading core codebase paralyses a team and negates any Agility gained through process improvement. He proposed strategies for management to identify, track and stop this downward spiral.
-
By Ken Schwaber
on Nov 13, 2006,