Thinking Outside the Synchronisation Quadrant

Thinking Outside the Synchronisation Quadrant

code::dive conference via YouTube Direct link

Kevlin Henney Thinking Outside the Synchronisation Quadrant

1 of 14

1 of 14

Kevlin Henney Thinking Outside the Synchronisation Quadrant

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Thinking Outside the Synchronisation Quadrant

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Kevlin Henney Thinking Outside the Synchronisation Quadrant
  2. 2 that shape a system, where significant is measured by cost of change.
  3. 3 Concurrency
  4. 4 Architecture is the art of how to waste space.
  5. 5 Systems have properties
  6. 6 and the execution confined; that the desire is boundless, and the act a slave to limit.
  7. 7 template void map reduce TaskIterator begin, TaskIterator end
  8. 8 A large fraction of the flaws in software development are due to programmers not fully understanding all the possible states their code may execute in.
  9. 9 Prevention - change the rules.
  10. 10 sequential
  11. 11 Immediately return a 'virtual' data object- called a future—to the client when it invokes a service. This future /... only provides a value to clients when the computation is complete.
  12. 12 Lambda-calculus was the first
  13. 13 To keep our C++ API boundary simple, we [...] adopted one-way data flow. The API consists of methods to perform fire-and-forget mutations and methods to compute view models required by specific views
  14. 14 To keep the code understandable, we write functional style code converting raw data objects into immutable View models by default. As we identified performance bottlenecks through profiling, we added…

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.