BT

InfoQ Homepage Legacy Code Content on InfoQ

  • Creating a Multi-Team Test Automation Solution

    A solid test framework with automated tests can increase the confidence to release. Cross-team pairing on the framework made it possible for a team to build quality in from the start; it also brought the teams together and upskilled the testers in test automation.

  • Michael Feathers Wants Error Elimination to Be a Design Driver

    Michael Feathers finds errors fascinating, but acknowledges that most developers don't spend a lot of time focusing on them. He also thinks most error handling is kind of giving up. Although best known for his books about working with legacy code, Feathers used his keynote presentation at Explore DDD 2018 to discuss how eliminating errors can be a design driver for software systems.

  • Why Software Developers Should Take Ethics into Consideration

    Most of the software that influences the behavior of human beings wasn’t created with strong ethical constructs around it. Software developers should ask themselves ethical questions like “who does this affect?”, “who could get hurt by this?”, and “who does this disadvantage or advantage?”, try to answer them, and be comfortable with questions they can’t answer yet.

  • Bridging the Gap between Legacy Systems and Modern Techniques

    Aging platforms that are managed with manual, time consuming processes can be costly. Teams can make a business case to management based on hours lost by repetitive work or re-work caused by human error for introducing modern techniques like automation tools and containers. The result is a predictable and repeatable process with minimal human interaction to deploy more often and more confidently.

  • Refocusing e-Commerce with Lean

    Auchan:Direct, the online grocery delivery service of Auchan France, decided to apply lean to develop a new e-Commerce website. Their CEO was the first customer and they used continuous and fast feedback from their clients on the new experience to improve website quality using continuous delivery.

  • Continuous Delivery at Klaverblad Insurance

    Continuous delivery should be treated as an agile project as it is about automating your deployment. You have to speed up in small steps and gain trust by doing small deliveries and solve problems fast. The story about how Klaverblad insurance has implemented Agile, DevOps, continuous delivery, and microservices.

  • Understanding Large Codebases with Software Evolution

    InfoQ interviewed Adam Tornhill, author of Your Code as a Crime Scene, about software evolution and mining social information from code and how to use this to increase the understanding of large codebases, how to create a geographical profile of code, and the benefits that can be gained from techniques like mining social information and geographical profiling.

  • Technical Debt and Team Morale when Maintaining a Large System

    Thomas Bradford talked about his experience with maintaining a monolith Java based system with zero test coverage and large technical debt at the Agile Testing Days 2015. InfoQ interviewed him about the problems that they had maintaining the system and the technical debt that had been build up, why they decided to take a different approach and how they improved team morale.

  • Rebuild or Refactor?

    Should you rebuilding or refactoring software?An interview with Wouter Lagerweij about what it is that makes refactoring so difficult, if rebuilding software is less risky than refactoring, and how continuous delivery fits with rebuilding software.

  • Directing complex IT-landscapes with Agile

    Where many organizations use agile to develop IT products, agile principles and practices can also be applied for maintaining landscapes of commercial products. Gert Florijn and Eelco Rommes will talk about directing complex IT-landscapes in public sectors such as healthcare and local and national government organizations at the Agile and Software Architecture Symposium 2015.

  • Scaled Scrum at Swiss Postal Services

    Swiss Postal Services has used scaled Scrum with seven teams to replace a legacy system. InfoQ interviewed Ralph Jocham about how they scaled Scrum and dealt with legacy issues, using a definition of done, how they managed to deliver their system three months earlier than planned, and the main learnings from the project.

  • Challenges When Implementing Microservices and Why Programming Style Matters

    Fred George talked about the Challenges in Implementing MicroServices and The Secret Assumption of Agile at the GOTO Amsterdam 2015 conference. InfoQ interviewed him about how make microservices as small as possible, challenges when implementing microservices and how to deal with them, why programming style matters, and what developers can do to develop their code writing skills.

  • New Developments in Model Driven Software Engineering

    An interview with Rob Howe, host of the MDSE session at the software engineering conference and CEO of Verum, about the state of practice and recent developments in model driven software engineering, the usage of this technology, whether he considers model driven software engineering to be a proven mature technology, and what the future will bring us in model driven software engineering.

  • Model-based Migration Approach for Maintenance of Legacy Software

    Hans van Wezep, software architect at Philips Healthcare, talked about model-based migration at the Bits&Chips Software Engineering conference. InfoQ did an interview with van Wezep about the challenges in maintaining legacy software, why manual refactoring is error prone, using models to refactor and migrate a codebase, and the benefits of using models when maintaining legacy software.

  • Managing Technical Debt Using Total Cost of Ownership

    Total Cost of Ownership (TCO) can be used for investment decisions and financial benefit analysis. When applied to software it covers the initial development costs and subsequent maintenance costs until phase out of a product. TCO can support architectural decisions and management of technical debt.

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.