We maintain an internal java framework, and one of its components requires a configuration file with a simple field: "Timestamp = 09112025000001".

Because this timestamp is persisted in a central database for state management, the developer is forced to manually increment the value after every single test run to avoid collisions. (I know... legacy systems...)

Anyway, a developer called us because they were running into a strange issue with the framework. We jumped on a debugging session, and I asked them to pull up their configuration file.

I fully expected to see a slightly incremented number, maybe 09112025000002, or at worst, a random number to ensure uniqueness. You know, anything numeric.

Instead, the timestamp they had been using was:
Timestamp = 091120250000K

A letter. A single, non-numeric character sitting right there in a field clearly named "Timestamp." I had to blink a few times. I mean, what is the thought process here? Did they hit the wrong key and just decide to commit to it?

The worst part: That wasn't even the root cause of the bug they called us about. But after seeing that config, I had to step away for a mental health break.

We desperately need better input validation, because our "robust" framework apparently accepts a letter as a valid time marker...

Just out of curiosity: Have you ever thought of learning COBOL?

I am fairly new to "enterprise" programming, but have some experience with self-study and open source. I'm getting more frustrated by the day because the code quality of our software is appallingly bad: functionality that should be centralised isn't, assumptions about internal structures and functionality of objects are made throughout the code, concerns are not separated, and so on. In my current team, we explicitly disabled SonarQube because "someone would have to fix it and our software wouldn't pass even after a month of work".
While I understand the concerns that companies would rather see new features than "quality improvements", so what? Every time we want to add something, we either have to restructure half the source code or add it in a really horrible way (and get pressured to do it that way).

Is it normal that code quality in companies is so bad?