The pragmatic programmer

A more complete talk about what is and how to be pragmatic.

Transcript

1. The pragmatic programmer Lucas Oliveira | lucasprag.com
2. It's a book
5. What makes a pragmatic programmer? A pragmatic philosophy A pragmatic approach
6. What makes a pragmatic programmer?
7. early adopter fast adapter
8. inquisitive
9. critical thinker
10. realistic
11. Jack of all trades
12. Jack of all trades != master of none
13. T-shaped skills
14. A pragmatic philosophy
15. "The greatest of all weaknesses is the fear of appearing weak" - JB Bossuet
16. The cat ate my source code
17. Take responsibility
18. Provide options, don't make lame excuses
19. Everybody is learning
20. Don't live with broken windows
22. Control your software entropy
24. it's time to bring out the stones
25. people find it easier to join an ongoing success
26. if something could be better, change it
27. be a catalyst for change
28. projects slowly get totally out of hand
29. remember the big picture
30. Good enough software
31. make quality a requirement issue
32. involve users in the trade-off
33. know when to stop
34. Your knowledge portfolio
35. "An investment in knowledge always pays the best interest" - Benjamin Franklin
36. it's similar to managing a financial portfolio
38. Building your portfolio
39. invest regularly
40. diversify
42. manage risk
44. buy low, sell high
45. review and rebalance
46. Goals
47. - learn one new language every year - read technical books - read nontechnical books too - read and write blog posts Goals
48. Goals - take classes - participate in local user groups - stay current - get wired
49. Critically analyze what you read and hear
50. Communicate!
51. A large part of our day is spent communicating, so we need to do it well.
52. know what you want to say
53. plan what you want to say
54. write an outline
55. ask yourself: Does this get across whatever I'm trying to say?
56. refine it until it does
57. know your audience
58. understand the needs, interests and capabilities of your audience
60. get to the same frequency of your audience
61. choose your moment
62. choose a style
63. make it look good
64. be a listener
65. A pragmatic approach
66. By keeping these fundamental principles in mind during development, you can write code that's better, faster, and stronger. You can even make it look easy
67. Every piece of knowledge must have a single, unambiguous, authoritative representation within a system
68. DRY don't repeat yourself
69. - imposed duplication - inadvertent duplication - impatient duplication - interdeveloper duplication How does duplication arise?
70. eliminate effects between unrelated things
71. Benefits
72. increase productivity
73. reduce risk
74. increase reversibility
75. every decision can be changed!
76. Coding DRY
77. keep your code decoupled
78. avoid global data
79. avoid similar functions
80. Single responsibility
81. must to be easy to test
82. Domain languages
83. "The limits of language are the limits of one's world" - Ludwig Wittgenstein
84. computer languages influence HOW you think about a problem
85. program close to the problem domain
86. The Basic Tools
87. shell games
88. use the power of shell commands
89. grep
91. awk
94. xargs
97. power editing
98. one editor
99. use it very well
100. use it for all editing things
101. editor features
102. configurable
103. extensible
104. programmable
105. increase your cursor movement
106. automate
111. Debugging
112. fix the problem, not the blame
114. rubber ducking
116. "select" isn't broken
117. don't assume it, prove it
118. What makes a pragmatic programmer? A pragmatic philosophy A pragmatic approach
119. You can learn a lot more
120. Thank you