DEV Community

Cover image for 100 Tips from The Pragmatic Programmers Book: Part 2/10
Rajesh Royal
Rajesh Royal

Posted on

100 Tips from The Pragmatic Programmers Book: Part 2/10

2.1. English is Just Another Programming Language.

Treat English as Just Another Programming Language. Write documents as you would write code: honor the DRY principle, ETC, automation, and so on.


2.2. It’s Both What You Say and the Way You Say It.

There’s no point in having great ideas if you don’t communicate them effectively.


2.3. Build Documentation In, Don’t Bolt It On.

Documentation created separately from code is less likely to be correct and up to date.


2.4. Good Design Is Easier to Change Than Bad Design.

A thing is well designed if it adapts to the people who use it. For code, that means it must adapt by changing.


2.5. DRY—Don't Repeat Yourself.

Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.


2.6. Make It Easy to Reuse.

If it’s easy to reuse, people will. Create an environment that supports reuse.


2.7. Eliminate Effects Between Unrelated Things.

Design components that are self-contained, independent, and have a single, well-defined purpose.


2.8. There Are No Final Decisions.

No decision is cast in stone. Instead, consider each as being written in the sand at the beach, and plan for change.


2.9. Forgo Following Fads.

Neal Ford says, “Yesterday’s Best Practice Becomes Tomorrow’s Antipattern.” Choose architectures based on fundamentals, not fashion.


2.10. Use Tracer Bullets to Find the Target.

Tracer bullets let you home in on your target by trying things and seeing how close they land.

Thanks for reading, happy coding 😀

Top comments (0)