Business logic is real programming.
What you described (non business-logic problems) is just "coding" level where you might integrate/compose libraries together at the boundaries of the system.
What you described (non business-logic problems) is just "coding" level where you might integrate/compose libraries together at the boundaries of the system.
But we also need a better way to empower and serve business teams by letting them control and manage the business logic. Keep in mind, we slow down the business teams if we cannot implement fast enough.
Carrying the mindset that devs must own everything can be harmful and counterproductive. In this case, there seems to be a mutual benefit to both sides. If you don't believe so, let me know.
Business systems need to be architected around core business needs, e.g. ledgers, journals, client records, inventory. The "transactions" implementing business rules need to perform the necessary information transformations and maintain any auxiliary information as required.