Old Fucking Punk
Follow

Abstraction should never introduce more resource usage. Poorly thought out OOPLs have violated this rule for too long. The difference between functional and non-functional requirements is the key. Separation of concerns shows the problem spaces are orthogonal.
"Learn to think" should always outweigh "Learn to code".

· Librem Social · 0 · 0 · 0
Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml