Peak of a Programmer

Presentation presented at VilniusRB Meetup.
September 2015

Transcript

1. The peak of a programmer ruby
2. @edvinasbartkus semi-geek
6. The peak of a programmer ruby
8. Disclaimer DON’T
 GET
 OFFENDED
10. Ballmer’s Peak
13. The peak of a programmer ruby
16. Intro
17. Stick
18. Profit
19. Profit
22. O.H.M.B.T. Once
 Heard Must Be
 True
23. O.H.M.B.T. • Java from the University • PHP is for web • Ruby is slow • IDE operators
25. C Ruby
26. C Ruby
27. O.H.M.B.T. • Tried Ruby • Did not like it • Moved on
29. Ruby Scientists • Variable names • You don’t review code
 You review output
30. Ruby Scientists • Variable names • You review output • My way is better
 Then common way
33. Ruby Perfectionists • No deploy without continuous integration • They spend 5 seconds to understand your code • They always keep on refactoring
35. Ruby Achievers • Variable names:

36. Ruby Achievers • Variable names:
 gautas_atstumas
 distance_rounded
37. Ruby Achievers • Variable names:
 getDistanceFrom
 set_user_distance
38. Ruby Achievers • Variable names • It takes month to get to know the environment • Duplicated code • Duplicated code
39. Ruby Achievers • Variable names • It takes month to get to know the environment • Duplicated code • Many things works!
41. Silicon Valley Rubists • Editor font matters • Setup instructions must work • Beautiful presentations • New things come along quickly
42. You can be like one of those
43. You can be like one of those none of those
44. The peak of programmer
45. The peak of programmer When you spend more teaching than learning
46. All the action in Ruby happens because you send a message
47. All the action in Ruby happens because you send a message Mr. Literally, 1987
48. Call to action: - Do you couch interns - Do you speak in meetups and conferences - Talk with people!
49. 拽拽