Pragmatic programer 1


Published on

Recently I read the book Pragmatic programmer by Andrew Hunt and David Thomas. I liked the book a lot, it helped me to understand how should we react to each and every thing happens while developing a software.
The book gives you so many tips to remember so that you could be more calm, patience, realistic, more descriptive, better speaker/listner and open minded. You can easily relate to your problems while developing the software.
In this presentation I am sharing 10 tips explained in the book. I hope you will enjoy

Published in: Education
1 Comment
  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Pragmatic programer 1

  1. 1. Pragmatic Programmer - 1 By -: Uday Pratap Singh
  2. 2. Agenda What is Pragmatic Programmer Traits Problems Practices Tips Rewards
  3. 3. Pragmatic Programmer Pragmatic + Programmer
  4. 4. Pragmatic Practical approach to any problem rather than theory. Advocate Behavior. Be aware of everything happening.
  5. 5. Programmer Programmer is a craftsman. Programmer directs the computer to do what he/she wants it to do. Programmer captures requirements and find a way so that a mere machine can do it. Programmer document the work so that others can understand.
  6. 6. Traits Early adopter Inquisitive Critical thinker Realistic Think in large context Take responsibility Jack of all trades Continuous improvements
  7. 7. Tip Tip 1  Care About your craft Tip 2  Think! About your work
  8. 8. The Cat Ate My Source Code  Problems happens in every project despite of taking every measure of safety (i.e; testing, documents, automation etc).  Don’t afraid to admit ignorance or error.  If anything can go wrong, it will. So don’t assume and prepare yourself for the worst.
  9. 9. The Cat Ate My Source Code  We can be proud of our ability but we must be honest about our shortcomings.  Take Responsibility.  Be accountable for your responsibility.  Dont blame someone or something else and dont make excuse.
  10. 10. The Cat Ate My Source Code  Provide solution for the problem  Dont say it cant be done; explain why it can’t be done  Before asking any help, explain problem go through the conversation in your mind
  11. 11. Tip Tip 3  Provide options, Dont Make Lame Excuses
  12. 12. Software Entropy  Despite of best plans and people, a project can still experience ruin and decay in its lifetime.  It could be because of some bad decision and stretching it.  Keep your project updated w.r.t changed requirement and environment.
  13. 13. Software Entropy  Broken Window Theory.  Fix each piece of bad code as it discovered or comment if you are out of time.  Help your team by surveying your neighborhood.  Choose 2-3 broken windows and discuss it with your colleagues.
  14. 14. Tip  Tip 4  Dont Live with Broken Windows
  15. 15. Stone Soup and Boiled Frog Be Catalyst Don’t take support for granted Be Focused People lose the will to fight entropy. So do it slowly.
  16. 16. Tip Tip 5  Be Catalyst for Change Tip 6  Remember The Big Picture
  17. 17. Good Enough Software Perfect Software is a Myth. Good enough for your users, maintainers, your own peace of mind. Involve your users in trade off. Know when to stop cause painting with so much colors sometimes loses its identity.
  18. 18. Tip Tip 7  Make Quality a Requirement issue
  19. 19. Your Knowledge Portfolio Your knowledge and experience are your professional assets. Unfortunately theyre expiring assets and need to be sharpen continuously. Your value declines with the knowledge you have.
  20. 20. Build Your Portfolio Invest regularly Diversify Review and rebalance your portfolio periodically Buy Low Sell High
  21. 21. Build Your Portfolio Read Technical/Non Technical books Participate in user groups Experiment Stay current Use your learning Critical Thinking
  22. 22. Tip Tip 8  Invest Regularly in Your Knowledge Portfolio Tip 9  Critically Analyze What You Read and Hear
  23. 23. Communicate Its not what you got but also how you package it. Every good idea is useless if you cant package it well. We spends hours in it so we need to do it well. We communicates with client, team mates, machines etc.
  24. 24. Communicate (WISDOM) What you Want them to learn? What is their Interest? How Sophisticated are they? How much Detail do they want? Whom do you want to Own the information? How you Motivate them to listen to you?
  25. 25. Communicate Know What You Want to Say Know Your Audience Choose Your Moment Choose a Style
  26. 26. Communicate Make It Look Good Involve Your Audience Be a Listener Get Back to People
  27. 27. Tip Tip 10  Its Both What You Say and the Way You Say It
  28. 28. Rewards Active involvement in your work Mastery on number of subjects Pleasure of feeling of continuous improvements In long run you and your team will be more efficient Easy maintainable code Less meetings
  29. 29. Thank You!