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
What is the single most influential book every programmer should read?
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
Tip 1 - Care about your craft Tip 2 - Think! About your work
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.
"I wrote this and I stand behind my work"