As someone who has made a good life over the years by taking advantage of the security bugs (either to build my embedded empires--aka, jailbreaking--or to direc

As someone who has made a good life over the years by taking advantage of the security bugs (either to build my embedded empires--aka, jailbreaking--or to directly collect bounties) caused by all of the people who hate abstraction so much (or are merely so bad at doing it that they don't know how to do it well) that they vehemently argue that duplication is not merely a temporary pragmatic decision to incur potentially-dangerous architectural debt which you intend to come back and fix later but is somehow better than even trying to address it, I guess I find this discussion thread of people almost 100% tearing into this article's fundamental premise... kind of fun? ;P So, yes, yes: please do continue to ensure you have so much boilerplate in your "flat and easy to understand" code that you eventually make a fatal mistake (potentially simply while doing a merge commit), refuse to factor your safety checks out into abstractions that prevent you from making the same mistake twice due to your refusal to "obfuscate the underlying API everyone knows how to use", and (my true favorite) litter your code with multiple implementations of the same algorithms that have very subtle differences in them (so called "parser differentials") as you insist on every single programming language in use having its own copy of the algorithm "for ergonomic reasons, as IPC/FFI would be crazy when I can just import a second one off-the-shelf".