Where I see this happen a lot: testing. Initially test automation people think about tests as stateless, and so don't design the framework to have any persiste

Where I see this happen a lot: testing. Initially test automation people think about tests as stateless, and so don't design the framework to have any persistence at all. Eventually, life proves that to be wrong, and test start needing some persistence between sessions... well, it usually starts between different cases, and that's where AQA start building ad hoc "databases". Unfortunately, it almost never downs on them that what they needed all along was a database, so the tests grow a weird slow and buggy persistence layer.