2 ms·
The problem is, at the end of the day, business logic needs to get encoded in the program. So all the abstractions cant abstract away the domain specific "if el
by ldjkfkdsjnv 5y ago
The problem is, at the end of the day, business logic needs to get encoded in the program. So all the abstractions cant abstract away the domain specific "if else" statements. Infrastructure itself will be a solved problem, and we will implement interfaces like serverless lambas, but it still remains, the logic of the business needs to go in the code. OOP itself is meant for building relationships between sets of business logic, and coding that, as has been discussed, always ends in complexity and needs thought
- sakoht 5y agoFred Brooks' classic "No Silver Bullet" outlines this fundamental principle of software engineering physics. Written in 1986, the paper has its own wikipedia page: https://en.wikipedia.org/wiki/No_Silver_Bullet https://en.wikipedia.org/wiki/No_Silver_Bullet
- galaxyLogic 5y agoIt's not only that we need to code the business logic in a programming language. To a degree we must also design those business processes. That is programming too, programming your people.