> This is why I aggressively avoid use of non-vanilla technology stacks I was with you until this line. I've never seen a codebase where Not Invented Here Synd

> This is why I aggressively avoid use of non-vanilla technology stacks I was with you until this line. I've never seen a codebase where Not Invented Here Syndrome resulted in a stack that "antagonizes root cause analysis" in any way. I once worked at a C++ shop that had NIH'ed a supposedly thread safe string class, and it wasn't pretty. There's plenty mature robust tech out there, and the chance that your own inventions are equally free of quirks and edge cases as battle-tested frameworks/libraries/databases that have had 1000s of eyeballs on them sounds quite unlikely to me, regardless of your programming skill.