Session type:


Presented by:

Gerald Benischke

Ooredoo FinTech

Session time:

15 May 11:30 12:15

Session duration:

45 minutes

About the session

"This tech stack is outdated, it's a legacy system and oh my goodness just look at metaphorical gaffer tape that's being used in code" - sound familiar? How about "We can’t recruit for this position, because nobody wants this legacy tech anymore"?

Why? So-called legacy code is the backbone of so much software engineering. How many banks, insurances or government departments would just stop working if the mainframes were switched off?

Far from something to outsource to the lowest bidder, looking after legacy is a job for experienced engineers.  Far from being the short straw, brownfield development is just as exciting - if not more - than working in a feature factory knocking out microservices with the latest shiny patterns.

Participant takeaways:

  • Legacy code is then one that makes money
  • How can we make maintenance "desirable" again?
  • How does the ‘You build it, you run it’ approach fit in with software maintenance
  • Why is it so important that the engineers looking after your legacy software are not a revolving door of burnt-out engineers
  • The importance of autonomy and sticking with the agile mantra of "people over processes and tools"


Legacy, Maintenance Mode, Thought-Provoking

About the speaker(s)