For future convenience, here's a reusable design pattern for these articles:
* Part 1: Have you considered <thing that is unlikely to be relevant>? You should, and BDUF will save you from it!
* Part 2: What if <totally foundational thing> needed to be swapped out? Add a jillion lines of boilerplate and indirection, JUST IN CASE!
* Part 3: Could somebody new come into your codebase with a general understanding of the tools & libraries you're using and immediately be productive? Fk that, make up your own custom APIs to hide anything familiar!
* Part 4: FAST TESTING FAST TESTING FAST TESTING FAST TESTING
* Part 5: Reuse is very important. For the content in this section, find a chunk of prose about reuse from a '90s C++ book and paste it in. See how easy that was?
* Part 1: Have you considered <thing that is unlikely to be relevant>? You should, and BDUF will save you from it!
* Part 2: What if <totally foundational thing> needed to be swapped out? Add a jillion lines of boilerplate and indirection, JUST IN CASE!
* Part 3: Could somebody new come into your codebase with a general understanding of the tools & libraries you're using and immediately be productive? Fk that, make up your own custom APIs to hide anything familiar!
* Part 4: FAST TESTING FAST TESTING FAST TESTING FAST TESTING
* Part 5: Reuse is very important. For the content in this section, find a chunk of prose about reuse from a '90s C++ book and paste it in. See how easy that was?