Pragmatic Programmer Book Review

14,111 views
14,052 views

Published on

Pragmatic Progrmamer book review - my last presentation for Gruden

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
14,111
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Question: How many of you have read or heard the book? Have you heard of Andy Hunt and Dave Thomas? Or the Pragmatic Bookshelf? Well I believe this is the first book that started the Pragmatic Bookshelf
  • Maintain knowledge portfolio So treat your career as an investment – I assume most of you have shares investments of some sort. So when you are an investor – what do you do? You invest regularly, diversification, balance your portfolio between conservatives and high risks, you periodically review your portfolio Similarly with your career – invest on it. Manage your risk by having a balanced and diversified portfolio – have a blue chip skills such as Java, .NET or PHP and combined them with a high risk high reward investment such as Python, Ruby on Rails? Earn more knowledge capital by reading books, learn a new language every year, read non techie book – read management book even, go to user groups, experiment with different env – if you've been a primiarly windows user – try Linux or mac once in a while and appreciate the difference. Try different IDE once in a while.
  • Now that we know a pragmatic programmer looks like – let's look at some of the techniques or ways of life
  • Pragmatic Programmer Book Review

    1. 1. What is the single most influential book every programmer should read?
    2. 4. Don't live with broken windows
    3. 5. Maintain Knowledge Portofolio
    4. 6. Communication Prototyping DRY – Do not Repeat Yourself Estimating Source Control Debugging Strategies Code Generation Design By Contract Programming by Coincidence vs Programming Deliberately Re-factor Code that's easy to test - design to test Requirements Automation Ruthless Testing - unit testing, integration test, performance test, usability test
    5. 7. Tip 1 - Care about your craft Tip 2 - Think! About your work
    6. 8. We want to see pride of ownership . Your signature should come to be recognized as an indicator of quality. People should see your name on a piece of code and expect it to be solid, well written, tested, and documented. A really professional job. Written by real professional.
    7. 9. "I wrote this and I stand behind my work"

    ×