Name Your State State Your Thread (Nordic Ruby 2013)

Transcript

1. Andrés N. Robalino @androbtech 1 Saturday, December 14, 13
2. RoleModel.check :up Jorge Robalino @sd @jera1618 Sebastian Delmont 2 Saturday, December 14, 13
3. Jorge Robalino @sd @jera1618 Sebastian Delmont Yo 3 Saturday, December 14, 13
4. Jorge Robalino @sd @jera1618 Sebastian Delmont Yo 4 Saturday, December 14, 13
5. THREADS BECAUSE WE WANT AND WILL LOVE USING THEM! BUT... 5 Saturday, December 14, 13
6. THERE ARE SURPRISES WE NEED TO BE AWARE OF 6 Saturday, December 14, 13
7. ‘(Race Condition Starvation Deadlock) (WHEN ‘[COORDINATION NEEDED] ) 7 Saturday, December 14, 13
8. ‘(Race Condition Starvation Deadlock) (WHEN ‘[COORDINATION NEEDED] ; MANUAL SYNCHRONIZATION ) 8 Saturday, December 14, 13
9. ‘(Race Condition Starvation Deadlock) (WHEN ‘[COORDINATION NEEDED] ; MANUAL SYNCHRONIZATION EASY TO FORGET! ) 9 Saturday, December 14, 13
10. BUT THE PROBLEM IS ELSEWHERE... 10 Saturday, December 14, 13
11. BUT THE PROBLEM IS ELSEWHERE... SHARING MUTABILITY 11 Saturday, December 14, 13
12. IS MUTABILITY BAD? NOT NECESSARILY. ONLY WHEN WE MUTATE AND SHARE 12 Saturday, December 14, 13
13. HOW TO GET AROUND WITH STATE FOR PROGRAMS TO DO USEFUL THINGS STATE MANIPULATION CANNOT BE AVOIDED. 13 Saturday, December 14, 13
14. HOW TO GET AROUND WITH STATE STATE MANIPULATION DOESN’T NECESSARILY MEAN STATE MUTATION. 14 Saturday, December 14, 13
15. HOW TO GET AROUND WITH STATE ‘(and I can hear our functional programming friends telling us to think STATE TRANSFORMATION instead of state modification) 15 Saturday, December 14, 13
16. •Encapsulate mutability and share only immutable data. •Make everything immutable. •Shared mutability. •Use libraries to watch over changes and warn of violations (if any) 16 Saturday, December 14, 13
17. •Encapsulate mutability and share only immutable data. •Make everything immutable. •Shared mutability. •Use libraries to watch over changes and warn of violations (if any) 17 Saturday, December 14, 13
18. •Encapsulate mutability and share only immutable data. •Make everything immutable. •Shared mutability. •Use libraries to watch over changes and warn of violations (if any) 18 Saturday, December 14, 13
19. •Encapsulate mutability and share only immutable data. •Make everything immutable. •Shared mutability. •Use libraries to watch over changes and warn of violations (if any) 19 Saturday, December 14, 13
20. Thank you. ANDRÉS N. ROBALINO @androbtech 20 Saturday, December 14, 13