How further developed software protects us in a world full of tensions

Blog  — Thu 6 Jun 2024

We live in a time of global tensions and societies that are highly dependent on technology. This can cause friction.

An often undervalued aspect of software development is finishing. Often, when custom software is created, it is done through a method that consists of short development cycles. As soon as the functional goal is achieved, work stops.

However, software development can be well compared to painters and inventors. To achieve a result, a rough sketch or a prototype is first made. Concretely, this means that shortcuts may be taken in the code or remnants may be left behind to test the functionality. Since wishes and feedback can still have an impact, options in the code are often left open that later turn out to be unnecessary.

This code, however, is generally not further developed for financial reasons. At most, during a complaint, the cause of a bug will be investigated again.

It is conceivable that this approach is attractive from a commercial point of view. However, this way of thinking hinders in the following areas: security, maintenance & updates, and performance. In a world with tensions, security is increasingly coming to light, sometimes in very embarrassing situations. And later again.

The motto "prevention is better than cure" also applies here. Break-ins, vandalism, data hijacking, and data leaks have major consequences for the security of users, staff, and even the continuity of the entire organization.

A new way of thinking that accepts and provides room for software developers to further develop code is therefore desirable and wise. Maintaining software is more than just performing the bare essentials. It can also involve further optimizing, cleaning up, improving, and securing existing software.

These activities may seem like investments that yield little or no return on investment. However, the opposite is true. Further developed code can be cheaper, faster, and easier to maintain. Security can also be better guaranteed, as efficient, short code inherently has fewer attack surfaces and is easier to pentest. This can prevent many costs and embarrassing situations in the near or distant future.