Yeah. Luckily the work I am doing is to fix some really bad work that the entire company has been complaining about. So once it’s fixed it will hopefully be a little bit more recognition than that. Plus my boss is pretty level headed.
But who fucking knows? There is always the likelihood that people will say things along those lines. And it ain’t my job to fight them on that.
No, we have worse. Dates sometimes stored as strings, sometimes as datetimes, and sometimes as integers. There is no consistency, logic, or forethought to the schema.
It’s rough.
At work, I am currently dealing with a table that has no primary key, no foreign key, duplicate (almost) serial numbers, booleans stored as strings, and so on. It’s a nightmare of a table.
Entity framework is acting like I’m on meth for using such a table.
[Spoilers]
Act 3? The game bugged out in act 1 when Shadowheart tried to kill Lae’zel. It straight up didn’t show us the cut screen of them fighting, and defaulted to Lae’zel dying when we failed to stop it in a cutscene we didn’t get.
The end result being that Lae’zel just didn’t interact with the party for a month, and then suddenly drop dead, bloody on the floor after a patch.