Download to read offline
Uploaded byDominic Graefen
Productive Programmer
This document discusses productivity for programmers. It defines productivity as the ratio of output to input. Key factors that impact programmer productivity are discussed, including teamwork, communication, planning, quality, and efficiency. Specific techniques for improving quality include reading books, using frameworks/libraries, learning a new language each year, sharing code, respecting feedback, and leaving one's comfort zone. Efficiency techniques include DRY principles, questioning work processes, and using best practices. The Unix philosophy of writing modular, reusable programs is advocated. Ruby is presented as a productive programming language due to its interactive shell, large library of gems, and ability to easily create executables and automation scripts.
Productive Programmer
- 2.
- 3.
- 6.
- 7.
- 8. PRODUCTIVITY IS THE EFFICIENCY OFPRODUCTION
- 9.
- 10.
- 11.
- 12. LINES OF CODE ? TIME ?
- 13.
- 14.
- 15. PRODUCTIVITY FACTORS COMMUNICATION TEAMWORK
- 16. PRODUCTIVITY FACTORS COMMUNICATION TEAMWORK PLANNING
- 17. PRODUCTIVITY FACTORS COMMUNICATION TEAMWORK PLANNING QUALITY
- 18. PRODUCTIVITY FACTORS COMMUNICATION TEAMWORK PLANNING QUALITY EFFICIENCY
- 19. PRODUCTIVITY FACTORS QUALITY TEAMWORK COMMUNICATION PLANNING EFFICIENCY
- 20.
- 21.
- 22. QUALITY question authority choose theright tool for the job
- 23.
- 24.
- 26.
- 27. PUREMVC IN2AR COCOONP2P TWEENMAXTONFALL AWAY3D ROBOTLEGS BEYONDREALITY SIGNALS NAVIGATOR PARSLEY HYDRAP2P EMBER
- 28.
- 29. RUBY SCALA HAXEJAVA PYTHON AS3 C# OCAML ERLANG CLOJURE FANTOM HASKELL JAVASCRIPT LISP LUA OBJECTIVE-C PROLOG
- 30.
- 31.
- 32.
- 33.
- 34. LEAVEchange your platform change your tools YOUR COMFORT ZONE
- 35. LEAVEchange your platform change your tools YOUR change your processes COMFORT ZONE
- 36.
- 38.
- 40.
- 41. EFFICIENCY DRY: don’t repeatyourself
- 42. EFFICIENCY DRY: don’t repeatyourself question the way you work
- 43. EFFICIENCY DRY: don’t repeatyourself question the way you work use best practices
- 44.
- 45.
- 46.
- 47.
- 48. THE UNIX PHILOSOPHY write programsthat do one thing and do it well
- 49. THE UNIX PHILOSOPHY write programsthat do one thing and do it well write programs to work together
- 50. THE UNIX PHILOSOPHY write programsthat do one thing and do it well write programs to work together write programs to handle text streams
- 51.
- 52.
- 53.
- 54.
- 56.
- 57.
- 58. A 3 MINUTETASK YOU DO 10 TIMES A DAY
- 59. MAKES ABOUT 10 HOURSA MONTH OF WASTED TIME
- 60. RAKE THE RUBY WAY OFAUTOMATION
- 61.
- 62.
- 63.
Editor's Notes
- #2 \n
- #3 \n
- #4 \n
- #5 \n
- #6 \n
- #7 \n
- #8 \n
- #9 \n
- #10 \n
- #11 \n
- #12 \n
- #13 \n
- #14 \n
- #15 \n
- #16 \n
- #17 \n
- #18 \n
- #19 \n
- #20 \n
- #21 \n
- #22 \n
- #23 \n
- #24 \n
- #25 \n
- #26 \n
- #27 \n
- #28 \n
- #29 \n
- #30 \n
- #31 \n
- #32 \n
- #33 \n
- #34 \n
- #35 \n
- #36 \n
- #37 \n
- #38 \n
- #39 \n
- #40 \n
- #41 \n
- #42 \n
- #43 \n
- #44 \n
- #45 \n
- #46 \n
- #47 \n
- #48 \n
- #49 \n
- #50 \n
- #51 \n
- #52 \n
- #53 \n
- #54 \n
- #55 \n
- #56 \n
- #57 \n
- #58 \n
- #59 \n
- #60 \n
- #61 \n
- #62 \n
- #63 \n
- #64 \n
- #65 \n
- #66 \n
- #67 \n
- #68 \n
- #69 \n
- #70 \n
- #71 \n