Editing Cobol and PostgreSQL (section)

=== The forgotten design ===
Standards are lacking, because of political issues, time constraints and a too rapid pace of developments. Of course, there should have been a design, lacking standards, accidents or laziness are another cause of missing, insufficient or outdated documentation. It can go as bad as programs running in production of which nobody has a clue of what they are doing exactly, the only certainty is that things go wrong whenever the program goes wrong.</br>
I wrote the non nonsensical primes programs set on top of my head as an example three tier oriented system system, just to demonstrate the working of such a system. The challenge was to have some documentation at least, which is in line with the running joke in so many organisations: 'The program source is the best and most reliable source of information'. This is true under the condition that the program source is available, which is not always the case. There are loads of programs running in production today of which no one has a clue of what the program is doing, but everybody knows the program has to run to avoid problems. I did not go to the extend of re-engineering cobol source from the running executable (yet).
Thanks to [https://claude.ai Claude.ai]there is at least some documentation now.
* The primes system design [[Primes system Design]].
* Design standards [[Design standards]].