wroclove.rb 2017 - recap

This is a presentation which I gave on Rzeszow Ruby User group meeting about the best Ruby conference in Poland - wroclove.rb 2017

Transcript

1. WROCLOVE.RB 2017 RECAP Mateusz Bielec 28.03.2016, RRUG#5
2. WROCLOVE.RB
3. https://twitter.com/wrocloverb/status/844147433424805888
4. https://twitter.com/cs3b/status/843748260963672064
5. https://twitter.com/hubertlepicki/status/843117548300394497
6. https://twitter.com/gosiaczu/status/843413092532961280
7. https://twitter.com/wpiekutowski/status/843430456603414528
8. TALKS
9. KARAFKA - PLACE WHERE RUBY, RAILS AND KAFKA MEET TOGETHER Maciej Mensfeld
10. https://kafka.apache.org/images/logo.png
11. http://mensfeld.github.io/karafka-framework-introduction/img/ karafka-04.png
12. MACHINE LEARNING FOR THE RESCUE Mariusz Gil
13. https://twitter.com/b0niek/status/842790351991701504
14. „MACHINE LEARNING IS NOT A SINGLE RUN OF ALGHORITM IT'S A PROCESS"
15. THE OVERNIGHT FAILURE Sebastian Sogamoso
16. https://d3vv6lp55qjaqc.cloudfront.net/items/2b003g3631383Q1H1E16/ image.jpg
17. https://speakerdeck.com/sebasoga/the-overnight-failure-1
18. FAULT TOLERANCE IN RUBY Hubert Łępicki
19. FAULT TOLERANCE IN RUBY
20. FAULT TOLERANCE IN RUBY • Fault tolerance
21. FAULT TOLERANCE IN RUBY • Fault tolerance • Circuit Breaker pattern
22. FAULT TOLERANCE IN RUBY • Fault tolerance • Circuit Breaker pattern • Fail fast
23. AUTOMATED TYPE CONTRACTS GENERATION FOR RUBY Valentin Fondaratov
24. BINDINGS IN RUBY - BEHIND THE MAGIC OF BLOCKS Piotr Szmielew
25. THE BABEL FISH IS DATA: A CASE STUDY Norbert Wójtowicz
26. https://twitter.com/voter101/status/843470327963439104/photo/1
27. WE ALL BUILD DISTRIBUTED SYSTEMS Maciej Rząsa
28. https://twitter.com/wrocloverb/status/843402581464567809
29. https://twitter.com/mbie/status/843411191359852544
30. PREDICTING PERFORMANCE CHANGES OF DISTRIBUTED APPLICATIONS Wojciech Rząsa
31. https://twitter.com/wrocloverb/status/843417549618470912
32. https://twitter.com/pankowecki/status/843427241828794368
33. CONCURRENTRUBY V1.1.0: NEW FRAMEWORK, NEW WAY OF WRITING CONCURRENT CODE! Petr Chalupa
34. DISCUSSION PANELS
35. https://twitter.com/PoslinskiDotNet/status/843103247728590848
36. HOW TO SURVIVE IN THE JAVASCRIPT WORLD AS A RUBY PROGRAMMER AND STAY SANE (IN 2017)
37. LIGHTING TALKS
38. https://twitter.com/fribulusxax/status/842799833446567936
39. https://twitter.com/vovaua/status/843132288468770817
40. LIGHTING TALKS
41. LIGHTING TALKS • Always rescue StandardError
42. LIGHTING TALKS • Always rescue StandardError • TIG - Text-mode interface for git
43. LIGHTING TALKS • Always rescue StandardError • TIG - Text-mode interface for git • Google Summer of Code
44. LIGHTING TALKS • Always rescue StandardError • TIG - Text-mode interface for git • Google Summer of Code • Ruby is fast
45. LIGHTING TALKS • Always rescue StandardError • TIG - Text-mode interface for git • Google Summer of Code • Ruby is fast • https://github.com/obrok/discombobulator
46. LIGHTING TALKS • Always rescue StandardError • TIG - Text-mode interface for git • Google Summer of Code • Ruby is fast • https://github.com/obrok/discombobulator • https://github.com/niklas/rails-dairylog
47. WE WERE THERE https://twitter.com/RRUGpl/status/843892405703233540
48. MOST ACTIVE USERS ON TWITTER WITH #WROCLOVERB
49. MOST ACTIVE USERS ON TWITTER WITH #WROCLOVERB 1. mjrzasa - 34
50. MOST ACTIVE USERS ON TWITTER WITH #WROCLOVERB 1. mjrzasa - 34 2. pankowecki - 23
51. MOST ACTIVE USERS ON TWITTER WITH #WROCLOVERB 1. mjrzasa - 34 2. pankowecki - 23 3. wrzasa - 22
52. MOST ACTIVE USERS ON TWITTER WITH #WROCLOVERB 1. mjrzasa - 34 2. pankowecki - 23 3. wrzasa - 22 4. wrocloverb - 22
53. MOST ACTIVE USERS ON TWITTER WITH #WROCLOVERB 1. mjrzasa - 34 2. pankowecki - 23 3. wrzasa - 22 4. wrocloverb - 22 5. nerdblogpl - 18
54. MOST ACTIVE USERS ON TWITTER WITH #WROCLOVERB 1. mjrzasa - 34 2. pankowecki - 23 3. wrzasa - 22 4. wrocloverb - 22 5. nerdblogpl - 18 6. RRUGpl - 16
55. SUMMARY
56. SUMMARY • Hard to get a single ticket
57. SUMMARY • Hard to get a single ticket • Huge engagement, different topics
58. SUMMARY • Hard to get a single ticket • Huge engagement, different topics • Elixir is not a Ruby replacement… yet
59. QUESTIONS?
60. QUESTIONS?
61. RESOURCES • https://mensfeld.github.io/karafka_-_place_where_ruby_rails_and_kafka_meet_together/#/ • https://speakerdeck.com/sebasoga/the-overnight-failure-1 • http://slides.com/hubertlepicki/fault-tolerance-in-ruby#/ • https://speakerdeck.com/valich/automated-type-contracts-generation-for-ruby • https://speakerdeck.com/esse/bindings-in-ruby-behind-the-magic-of-blocks • https://speakerdeck.com/wrzasa/predicting-performance-changes-of-distributed-applications • https://speakerdeck.com/mrzasa/we-all-make-distributed-systems-wroc-love-dot-rb-2017 • https://hackpad.com/How-to-survive-in-the-JavaScript-world-as-a-Ruby-programmer-and-stay-sane-in-2017-AlN9bM04SEk • https://hackpad.com/Ruby-vs-Elixir-pTeC0e6tsnd • http://michal.muskala.eu/2017/03/22/why-i-stayed-with-elixir.html • http://blog.endpoint.com/2017/03/wrocloverb-2017-part-1.html