BT

InfoQ Homepage Maintenance Content on InfoQ

Articles

RSS Feed
  • Correctness vs Change: Which Matters More?

    In ongoing software development, our core work is changing code. Jessica Kerr argues that by building changeable software on top of existing, well-understood components, and by improving delivery automations, teams will get better at their core work of delivering value and "changing reality".

  • The Ultimate Feedback Loop: Learning from Customer Reported Defects

    Investigating the root causes of customer reported defects will have a great impact on your organization. The best ways to ensure customer satisfaction, lower costs and increase employee engagement is to look inside — you already have the data. At the end, it’s all about continuous improvement.

  • Microservices in the Real World

    An interview with Alexander Heusingfeld and Tammo van Lessen about getting operations involved in architecture and dealing with "us vs. them" behavior when applying DevOps, how to use the Self-Contained Systems approach to modernize software systems, similarities and differences between Self-Contained Systems and microservices, improving deployment pipelines and using measurements in deployment.

  • Q&A on the Book Agile Impressions

    Gerald Weinberg shares his observations of the agile movement "where it came from, where it is now, and where it's going" in the book Agile Impressions. In the book he explores the agile basics and principles, discusses how he has seen them being violated, and offers ideas and examples for applying the agile principles.

  • Evo: The Agile Value Delivery Process, Where ‘Done’ Means Real Value Delivered; Not Code

    Current agile practices are far too narrowly focused on delivering code to users and customers. There is no systems-wide view of other stakeholders, of databases, and anything else except the code. This article describes what ‘Evo’ is at core, and how it is different from other Agile practices, and why ‘done’ should mean ‘value delivered to stakeholders’.

  • Implementation Decision Rationales – Program Comprehension in Agile

    Given the fact that the bulk of a developer's work is maintaining and enhancing existing code, Fabian Kiss makes the case for a lightweight approach to documenting the rationale and decision process behind design decisions to help later developers tie the source code syntax to its meaning in the application domain. Using simple tags and clearly thought out rationale to provide just-enough value.

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.