2 ms·
I worked with that guy too, he left the company 4 years ago, and I am still maintaining his homebrew ORM that has no documentation or working tests.
by tmaly 11y ago
I worked with that guy too, he left the company 4 years ago, and I am still maintaining his homebrew ORM that has no documentation or working tests.
- krisdol 11y agoWhy didn't you rewrite it?
- zilean 11y agoWriting documentation and tests would be a better way to address the pain point.
- pm24601 11y agoThis is victim-blaming. It would have been better yet if the person hadn't created work for others with this homebrewed ORM.
- sqldba 11y agoReplacing a home brew ORM in an application of any scale is a massive time and bug investment. It will be tied into every single aspect of everything, and even into the build and database deploy processes. It often has its own classes with their own internal behaviour which get passed around raw - so you can't just upgrade one price of code and test and move on, you'll have to rewrite the entire product at once. Having seen it done I can understand very easily how someone could not just remove it.
- tmaly 11y agoI have no choice but to replace it as the databases it accesses are changing. But as you said, it is a massive sink of time to change a core part of your system that some many other parts depend on.