> I’d rather have a messy bit of code that has a bug in it than an empty file. There's at least a third scenario that busts this dichotomy and also isn't the o

> I’d rather have a messy bit of code that has a bug in it than an empty file. There's at least a third scenario that busts this dichotomy and also isn't the overconfident junior dev nonsense in some of the other comments. I've seen enough of those messy bugs and worked on similar enough projects that are far better put together. I just want to replicate their success. I'll be shamelessly stealing ideas under the guise of "best practices" and I won't worry about the outcome because I already know. The code from me will be easy to read and well documented and nobody will notice apart from the suspicious lack of drama, as it should be.