Eric Lippert taught me that if you see a bug in some tricky code, rewrite the code with a simpler approach, rather than put in a fix which will make the code ev

Eric Lippert taught me that if you see a bug in some tricky code, rewrite the code with a simpler approach, rather than put in a fix which will make the code even trickier and quite possibly create new bugs. More specifically, if you have a bunch of bugs related to storing data in an inconvenient way, convert the data to a simpler format rather than write a bunch of complex logic around the bad data format. Article here: https://docs.microsoft.com/en-us/archive/blogs/ericlippert/bug-psychology https://docs.microsoft.com/en-us/archive/blogs/ericlippert/b... As a tangent, this article took me ages to find, even though I remembered the author, most of the details, and the string "SensibleDate". I'm not sure if the lesson is that MS is at fault for moving old content and having a lousy internal search tool, or Google is getting worse because it couldn't find it anyway, or I've gotten worse at finding stuff. But a few years ago I would've been shocked to not quickly find an article where I remembered a few relevant details, and now it seems like the norm.