Scaling Silos (short version)

Presented at DevOpsDays Portugal 2019.

Transcript

1. SCALING SILOS DISTRIBUTED KNOWLEDGE @GREYSCHALE DEVOPSDAYS PORTUGAL 2019
2. http://www.npr.org/player/embed/404548309/404548333
3. https://twitter.com/htde/status/590995577090875393
4. https://twitter.com/Scambl/status/590881078740672512.
6. OBSERVATION: I use Stack Overflow.
 A lot. QUESTION: How will my coding habits change if I give it up for 30 days? @GREYSCHALE
7. HYPOTHESIS: I don't need Stack Overflow that much. PREDICTION: I'll be able to come up with different ways to write the same code. @GREYSCHALE
8. TEST: 1. Route stackoverflow.com in /etc/hosts to 127.0.0.1 2. Code. 3. Keep daily journal of observations. 4. ??? 5. ...Profit?! @GREYSCHALE
9. DAY 1: - Already am struggling. Help. How to PostGIS in Rails without gem. - Postgres documentation ain't so bad...I guess... - Only last two results of this search are not SO.... @GREYSCHALE
10. DAY 2: "Are you on W3Schools because you can't use StackOverflow?" (shockingly...no) @GREYSCHALE
11. DAY 14: - F*CKING F***B**K API WTF TOKEN AM I SUPPOSED TO F*CKING USE. - It's not cheating if you make somebody else use StackOverflow on their computer, right....? @GREYSCHALE
12. DAY 15: - TFW SO result is before the official RSpec docs. - Is it cheating to use WebArchive to SO? @GREYSCHALE
13. DAY 19: - SQL JOINs are hard. - Fixed a ticket with just Rails docs and status code searches. \o/ @GREYSCHALE
14. DAY 22: - Already knew this search query would be all SO results. @GREYSCHALE
15. DAY 26: ¯\_(ω)_/¯ @GREYSCHALE
16. DAY 27: - Github issue ends with, "I posted the solution on StackOverflow." (ϓಠᤦಠ)ϓ⼺彡țȒț @GREYSCHALE
18. CONCLUSIONS: 1. ??? 2. ??? 3. ??? 4. ??? 5. ??? @GREYSCHALE
19. FAULT TOLERANCE
20. https://upload.wikimedia.org/wikipedia/commons/8/80/Stagecoach_London_LT379_on_Route_55%2C_Clapton_Pond_%2816063247983%29.jpg
21. https://xkcd.com/979/
22. http://forums.xkcd.com/viewtopic.php?f=7&t=76560#p2816635
23. https://sh-s7-live-s.legocdn.com/is/image/LEGO/10258
24. (BUS) FACTORISATION: @GREYSCHALE
25. (BUS) FACTORISATION: - Do you have a "go-to" person on your team? @GREYSCHALE
26. (BUS) FACTORISATION: - Do you have a "go-to" person on your team? - Do other people realise this or acknowledge it? @GREYSCHALE
27. (BUS) FACTORISATION: - Do you have a plan for if this person suddenly disappeared? @GREYSCHALE
28. (BUS) FACTORISATION: - Is it the tool itself?! @GREYSCHALE
29. CAP-ish Theorem: @GREYSCHALE
30. CAP-ish Theorem: - Partition Tolerance @GREYSCHALE
31. CAP-ish Theorem: - Partition Tolerance - Availability @GREYSCHALE
32. CAP-ish Theorem: - Partition Tolerance - Availability - Consistency @GREYSCHALE
33. CAP-ish Theorem: - Partition Tolerance - Availability - Consistency @GREYSCHALE
34. RESOURCE SHARING
35. https://xkcd.com/627/
36. https://xkcd.com/627/
39. @GREYSCHALE
40. @GREYSCHALE
41. @GREYSCHALE
42. @GREYSCHALE
43. @GREYSCHALE
44. HOW DO WE SHARE KNOWLEDGE? @GREYSCHALE
45. HOW DO WE SHARE KNOWLEDGE? - Brain dumps? @GREYSCHALE
46. HOW DO WE SHARE KNOWLEDGE? - Brain dumps? - Interrupts? @GREYSCHALE
47. HOW DO WE SHARE KNOWLEDGE? - Brain dumps? - Interrupts? - Discovery? @GREYSCHALE
48. SHARING == <3 @GREYSCHALE
49. SHARING == <3 - Independent @GREYSCHALE
50. SHARING == <3 - Independent - Memetic/epidemic @GREYSCHALE
51. SHARING == <3 - Independent - Memetic/epidemic - Codified @GREYSCHALE
52. CODIFY IT?! @GREYSCHALE
53. CODIFY IT?! - Expectations @GREYSCHALE
54. CODIFY IT?! - Expectations - Modernity @GREYSCHALE
55. CODIFY IT?! - Expectations - Modernity - Update rate @GREYSCHALE
57. CARGO CULTS: @GREYSCHALE
59. CARGO CULTS: - Make it so they don't need it @GREYSCHALE
60. CARGO CULTS: - Make it so they don't need it - Remove pressures @GREYSCHALE
61. https://images-na.ssl-images-amazon.com/images/I/8143BTFiw8L._SL1488_.jpg
62. CARGO CULTS: - Make it so they don't need it - Remove pressures - Attribute everything @GREYSCHALE
63. https://twitter.com/kellabyte/status/1100457037882810370
64. https://twitter.com/iamdevloper/status/1100350155658678274
65. SCALABILITY
66. SCALABILITY?
67. KNOWLEDGE ROADMAPS FOR: - The next month - The next quarter - The next decade?! @GREYSCHALE
68. team size knowledge @GREYSCHALE
69. CONCLUSIONS: @GREYSCHALE
70. CONCLUSIONS: 1. Knowledge IS a distributed system. @GREYSCHALE
71. CONCLUSIONS: 1. Knowledge IS a distributed system. 2. The weakest link weakens the system. @GREYSCHALE
72. CONCLUSIONS: 1. Knowledge IS a distributed system. 2. The weakest link weakens the system. 3. Not all sharing is alike. @GREYSCHALE
73. CONCLUSIONS: 4. I still use Stack Overflow. A lot. @GREYSCHALE
74. CONCLUSIONS: 4. I still use Stack Overflow. A lot. 5. But try to share what I learn more often. @GREYSCHALE
75. CONCLUSIONS: 4. I still use Stack Overflow. A lot. 5. But try to share what I learn more often. <3 @GREYSCHALE
76. https://xkcd.com/1053/
77. THE END
78. THE END?
79. THE PERFECT DISTRIBUTED SYSTEM: @GREYSCHALE
80. THE PERFECT DISTRIBUTED SYSTEM: Never mind, figured it out. posted 08-03-2003 @GREYSCHALE
81. THANK YOU QUESTIONS? @GREYSCHALE DEVOPSDAYS PORTUGAL 2019