The hardest problem in computer science is people; the second hardest problem is designing systems that are able to evolve & adapt to new goals & constraints over a span of many years or even decades
-
I think both of those concerns are major reasons why it's hard to find the right abstraction. Deciding what choices to surface as being meaningful to end users, and what you'd like to be able to swap out later.
Yes. Abstraction is just a tool to achieve these goals. A good abstraction in CS is one that mirrors the mental models of the people who manipulate it, and that is also structured in a way that allows for future evolution (modular and hierarchical)
-
-
The purpose of finding the right data structs / layering / architecture is to enable collective development & maintenance in a way that can scale to larger teams and that can adapt to ever-changing goals & constraints. A static system no one touches doesn't need good architecture
-
Incidentally, this is one thing I've found useful about diving into the old Cybernetics literature, the emphasis on "Variety Engineering".https://harishsnotebook.wordpress.com/2019/04/28/exploring-the-ashby-space/ …
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.