Careful buddy, you know how they get when we make wise and logical assertions based on our professional experiences in similar endeavors, that essentially get gas-lighted as "negativity" or "whining". I'll bring you a castigation trauma kit though, no smart man should be left on the battlefield alone. I've had just this sort of conversation with @inertia, over such things as the last breakdown, which looks like a dev left a local workbench test param in the code that made it all the way live. This is what #comments in code are for - "#following param should be reverted before deploy" and co-programming or peer review before typing git update and git commit, and git shit like that. But hey, basic entry level programming things like that were met with "peer reviews? that's the witnesses job." Okay, and I concede that ... to a point... but when there are dozens of undocumented changes (repeat need for comments in code) in a gazillion lines of code, I'd say it's kinda up to the code changing dev to at least make sure the changes can even be noticed for review.

So there's that.

To @inertia's credit though, my conversations with him, and his direct involvement in an improved test net, give me more confidence than I ever had in a steemit inc dev before his involvement there. He's wicked smaht.