Sorted by category:

Legacy software

Many organizations rely on computational or scientific software that was written long ago. In the daily rush, no-one stops and thinks about this code; the risks that are inherent to such legacy code remain unaddressed. In this blog, we highlight the most important risks in legacy code and what to do about them.

This is the second blog in our series where we show that our mathematical strengths are an important complement to our programming skills. Using a mathematical approach, we achieve solutions that programming alone couldn't. This time, we speak with Thea, who, along with Bas and then-colleague Alouette, worked on a fantastic project for Boskalis. Their mathematical insights led to a tremendous reduction in computing time, making a previously unusable computation feasible.

We're seeing increasing attention to environmental concerns and CO2 emissions in the world of computing software. This is not without reason: according to the International Energy Agency (IEA), data centers are already responsible for approximately 1-1.5% of global electricity consumption. Writing elegant code can make a difference.

We would like to share some of the experiences we've had over the past 15 years working on critical software with a complex legacy component. It dates back to the 1980s and has evolved into a powerful system packed with domain knowledge and smart algorithms. Its "killer feature" is its ability to handle complex geometries. Over the years, the program has more than proven its value.

Do you recognize this: software that was developed long ago, has been extended and adapted for years, but no longer meets today’s standards? If so, then our lunch lecture on modernizing software on September 24 is for you.

In our practice as scientific software engineers at VORtech, we work for organizations that have computational software as an essential part of their intellectual capital. If successful, a computational software package can exist for many years and even decades. At the same time however, the code base grows and becomes more and more difficult to manage. This is part 3 of a series of blogs in which we discuss how to deal with legacy code.

In our practice as scientific software engineers at VORtech, we work for organizations that have computational software as an essential part of their intellectual capital. If successful, a computational software package can exist for many years and even decades. At the same time however, the code base grows and becomes more and more difficult to manage. This is part 2 of a series of blogs in which we discuss how to deal with legacy code.

In our practice as scientific software engineers at VORtech, we work for organizations that have computational software as an essential part of their intellectual capital. If successful, a computational software package can exist for many years and even decades. At the same time however, the code base grows and becomes more and more difficult to manage. This is part 1 of a series of blogs in which we discuss how to deal with legacy code.

At VORtech we mostly work on extending and improving existing code. Let us explain why this is so important and how it works.