BT

InfoQ Homepage Antipatterns Content on InfoQ

  • Adoption of Cloud Native Architecture, Part 2: Stabilization Gaps and Anti-Patterns

    In this second part of cloud native adoption article series, the authors discuss the anti-patterns to watch out for when using microservices architecture in your applications. They also discuss how to balance between architecture and technology stability by not reinventing the wheel in every new application and at the same time, avoiding arbitrary reuse of technologies.

  • How to Avoid Cascading Failures in Distributed Systems

    Cascading failures are failures that involve some kind of feedback mechanism. In distributed software systems they generally involve a feedback loop where some event causes either a reduction in capacity, an increase in latency, or a spike of errors.  Laura Nolan explores them using public accounts of real production incidents.

  • Liberating Structures - an Antidote to Zombie Scrum

    Although many organizations use Scrum, the majority struggle to grasp both the purpose of Scrum as well as its benefits. They do Zombie Scrum; it looks like Scrum from a distance, but you see that things are amiss when moving closer. This article describes what Zombie Scrum is about and gives you tangible examples of how to recognize, treat and prevent Zombie Scrum by using Liberating Structures.

  • Agile Anti-Patterns: A Systems Thinking Approach

    Agile anti-patterns can disguise themselves as "solutions" or "workarounds". This article discusses the importance of recognising and classifying a new generation of agile anti-pattern with a systems thinking approach. It shows how to create and promote a shared language using value streams as an effective means of creating a systems thinking culture amongst agile teams and the wider business.

  • Scrum@Scale: An Interview with Agile Manifesto Co-Author and Scrum Co-Founder Jeff Sutherland

    Jeff Sutherland founded Scrum@Scale to help organizations address critical scaling challenges. Leaders form an Executive Action Team and are responsible for addressing organizational impediments.

  • Q&A on The Rise and Fall of Software Recipes

    Darius Blasband has written a book which challenges the conventional wisdom of software engineering: he protests against the adoption of recipes and standards-based approaches and rails against the status-quo. He calls himself a codeaholic who advocates for careful consideration of the specific context and the use of domain specific languages wherever possible.

  • Seven Microservices Anti-patterns

    In this article Vijay Algarasan, a Principal Architect at Asurion, discusses how he and his teams have encountered microservices at various engagements and some lessons they have learned as a result. This has resulted in them building up a series of anti-patterns and some associated patterns, which Vijay believes are more widely applicable to all practitioners of microservices

  • Q&A about the book Common System and Software Testing Pitfalls

    The book Common System and Software Testing Pitfalls by Donald Firesmith provides descriptions of 92 pitfalls that make testing less efficient and effective. The descriptions explain what testers and stakeholders can do to avoid falling into the pitfalls and how to deal with the consequences when they have fallen into them.

  • Modern Enterprise Performance Analysis Antipatterns

    In this article we present some of the most common performance analysis antipatterns in the enterprise platform, expressed in terms of their basic causes along with remediation strategies.

  • Ruby's Open Classes - Or: How Not To Patch Like A Monkey

    Ruby's Open Classes are powerful - but can easily be misused. This article looks at how to minimize the risk of opening classes, alternatives, and how other languages provide similar capabilities.

  • REST Anti-Patterns

    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.

  • Creating Product Owner Success

    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.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.