Yeah fair enough. Having had plenty of experience dealing with what code looks like when you take the opposing philosophy (this is not My First Project™), where one instead writes the minimum amount of code required to work for the current situation, I find that it's frighteningly easy to end up with compounded spaghetti code that is impossible to decipher, contains hundreds of lines of duplicated logic, and is generally riddled with bugs and unspoken edge cases. It's not so much a distrust of fellow programmers so much as an understanding that we're almost all inherently lazy and, especially when dealing with someone else's code, will tend to implement only the minimum viable solution whenever possible. I generally prefer to write well-organized, sufficiently-abstracted-and-DRY code that is easy to maintain in the long haul, because the small cost in productivity in this defensive coding is worth making it easy on yourself or others months down the line, when you're tasked with enhancing a feature and have long since forgotten how your code works.

I digress. I'll try to keep things as simple as possible going forward.