Issue of inheritance and runtime polymorphism : it is possible to avoid runtime polymorphism in many cases
Table driven : encode structure of problems as table (either an array of structs or two dimensional array)
Switch case driven : as seen in FP with known case statements
Don't repeat yourself : overuse causes fragmentation and bad abstractions
The example he uses is a compute heavy domain with high degree of presentation. If we then start to look at the fundamental question he is asking: performance. For a business system with 5000 users and high amount of business modelling done similar as SQL tables and columns or Java style objects, does the same reasoning apply?
https://www.youtube.com/watch?v=tD5NrevFtbU
The example he uses is a compute heavy domain with high degree of presentation. If we then start to look at the fundamental question he is asking: performance. For a business system with 5000 users and high amount of business modelling done similar as SQL tables and columns or Java style objects, does the same reasoning apply?
https://github.com/unclebob/cmuratori-discussion/blob/main/cleancodeqa.md
https://qntm.org/clean