This x 1000. As an additional perspective, I used to be on the board of trustees of my church when we were picking new bookkeeping software (for a church whose

This x 1000. As an additional perspective, I used to be on the board of trustees of my church when we were picking new bookkeeping software (for a church whose annual budget was less than $100K). We kept getting shown software that "handles everything for you" and eventually got strongarmed into Quickbooks (which the treasurer set up wrong) and nobody listened to me when I told them that unless they knew the finances well enough to run them with a paper spreadsheet, a checkbook and a calculator they had no business picking software. The point of that story is that it takes a long time to properly understand a problem domain well enough to start solving problems in it at the right level of abstraction. A framework can "understand things for you" and just work if you set it up right, but the cost is that you lose the freedom to replace that framework with something smaller and lighter.