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
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Not a critic but to me it seems the other way around, that an issue for people is computer science.
-
Check back after you work on something outside of academia
- Show replies
New conversation -
-
-
3) Caching
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
These things are connected: people are the adaptive capacity of highly interconnected software systems.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Hey Francois (
@fchollet), genuine question: where does abstraction fit in here? I ask because I’ve often thought of (automated) abstraction as being the hardest problem for CS. -
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.
- Show replies
New conversation -
-
-
This is exactly the reason I moved from 35 year software product developer into
#AI.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Just as comp arch goes from transistors, logic gates, functional units etc, organizations can be modeled with ppl as func. units, etc. Then, building a organization becomes a comp arch design problem. Comp arch is already hard, so building future proof teams is next level
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Yep, good thoughts to have when starting to build things online
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.