Similar Posts

Subscribe
Notify of
4 Answers
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Erzesel
7 months ago

I’m afraid I’m one of the people who produced legacy software. Of course, this was not aware of me at that time. (In conclusion, I was not a clairvoy to find out what will be the state of the art 20 years later).

Due to the way in which the software had to influence the control of ongoing production processes, a lot was knitted with hot needle. (If certain sensors/actuators were not available, the software was adjusted to other components on the fly. And some change remained “undocumented” because it was said that it was only a provisional.)

My successors seem to have handled this very well. In recent years, there have always been a rare question about some “littles in the cellar” and the company’s production is still running without any devastating explosions.

I think just as I and my colleagues had to deal with the then acute problems, this also applies to today’s team. …and also today’s “Programmer” will leave a mountain of Legacy-Leichen in a few years.

Erzesel
7 months ago
Reply to  jarko3

Legacy software is currently one of the biggest problems in the industry and there are plenty of people who are busy with it.

However, most people who are concerned with this simply have no interest or time to deal with more general questions in forums.

As far as GF itself is concerned, the interest in software development/programming has been extremely neglected since restructuring and is still attractive for the few remaining “specialists”.

I still know times, there were still some very tricky problems. Today it’s just about bearded AI wash.