|
|
|
|
|
|
by m0ther
2261 days ago
|
|
|
Re. ontology: If that's not it, it's close. Business logic is certainly a reflection of a programmer's understanding of the business, as well as their skill in applying object oriented concepts (or whatever) and occam's razor to express it in a manner that doesn't balloon in complexity and isn't cognitively wasteful. There's an art component, and a science component; and if they're both right it will make a solid foundation for everything else, and for communication with the business. |
|
|
Judging by your influences as an architect, I think you would enjoy these books:
- Ronald Ross, Principles of the Business Rule Approach.
- David B. Black, Wartime Software. If you like this, you'd probably like his other books as well. They each cover a different facet of software development, including QA and "project management" (which Black refers to as a disease).
You might also enjoy the essay by David Black in which he proposes "Occamlity" as the metric of software "goodness" (https://www.blackliszt.com/2020/03/william-occam-inventor-me...):
> I propose that a piece of software can be measured by its “Occamality.” The more “Occamal” it is, the better it is. And I propose that Occamality is strictly correlated with the extent to which there is no redundancy of any kind in a program...