A pragmatic programmer is someone who deals with problems sensibly and realistically based on practical considerations rather than theory. They are typically early adopters of new technologies, inquisitive critical thinkers who don't accept things at face value. Pragmatic programmers understand the underlying nature of problems, are familiar with a broad range of technologies, and care about crafting high quality software. Some tips for becoming pragmatic include fixing issues as soon as they arise rather than living with "broken windows," being an agent of positive change, and remembering the big picture rather than getting lost in details.

1. The Pragmatic Programmer
Nilesh Sharma
JRD Group

2. Who is a Pragmatic Programmer ?
● Dictionary meaning: dealing with things sensibly and realistically in a way
that is based on practical rather than theoretical considerations.
● Early Adopter/ Fast Adapter: Love try new things, apply knowledge quickly.
● Inquisitive: Tends to ask questions ( What’s best way to do ?)
● Critical Thinker: Rarely takes things without getting facts. Don’t like
sentences like (Because that’s the way it’s done).
● Realistic: Understand underlying nature of problem. Good feeling how
difficult a thing is and how much time it’s gonna take.
● Jack of all trades: try hard to be familiar with broad range of techs and
environments.

3. Tips for becoming a Pragmatic Programmer
Tip-1: Care about your craft - Develop your software well with good software
tools and best possible technology available.
Tip-2: Think ! about your work - Turn off the autopilot, think every decision you
are making everyday.

4. The Pragmatic Philosophy
A way of approaching problems and their solutions in
a unique way.

5. The cat ate my source code.

6. Take responsibility: Should not be afraid to admit
ignorance or errors. It will happen on best of projects.

7. Tip-3: Provide options. Don’t make lame excuses
● Use a rubber duck to explain your problem that
why this can’t be done.
● Have a conversation your mind, what other
person is likely to say.

8. Software Entropy
Entropy: Amount of disorder in system.
Law of thermodynamics: Entropy tends to increase in system. Similar thing
happens in software system, in result software rot happens.
How to stop it ?
Using Broken Window Theory

9. Broken Window Theory

10. Tip-4: Don’t live with broken windows. Fix them
ASAP.

11. The Stone Soup Story:

12. Tip-5: Be a catalyst of change.

13. How to boil a frog ?

14. Tip-6: Remember the Big Picture.

15. Conclusion:
● Care about your craft.
● Think ! about your work.
● Provide options, Don’t make lame excuses.
● Don’t live with broken windows.
● Be a catalyst of change.
● Remember the big picture.
To become pragmatic programmer is a continuous process. So much more to
learn. May be in another brown bag session :).

16. Thankyou :)