I am a Pragmatic Programmer Part 2

This is Part 2 of 7 part series inspired from the book Pragmatic Programmer, read Part 1 here:

  1. Always Use Source Code Control: Source code control is a time machine for your work—you can go back.
  2. Don’t Panic When Debugging: Take a deep breath and THINK! about what could be causing the bug.
  3. Don’t Assume It—Prove It: Prove your assumptions in the actual environment—with real data and boundary conditions.
  4. Write Code That Writes Code: Code generators increase your productivity and help avoid duplication.
  5. Design with Contracts: Use contracts to document and verify that code does no more and no less than it claims to do.
  6. Use Assertions to Prevent the Impossible: Assertions validate your assumptions. Use them to protect your code from an uncertain world.
  7. Finish What You Start: Where possible, the routine or object that allocates a resource should be responsible for deallocating it.
  8. Configure, Don’t Integrate: Implement technology choices for an application as configuration options, not through integration or engineering.
  9. Analyze Workflow to Improve Concurrency: Exploit concurrency in your user’s workflow.
  10. Always Design for Concurrency: Allow for concurrency, and you’ll design cleaner interfaces with fewer assumptions.

Please read part 3 of 7 part series inspired from the book Pragmatic Programmer here.



Leave a comment

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: