• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Is There any Emphasis on Continuous Inspection

 
Ranch Hand
Posts: 2874
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is there any emphasis on continuous inspection in the book. I mean how we should practice this. Or may be best practices or something?
 
Ranch Hand
Posts: 471
Mac OS X Hibernate Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I don't see any thing on that on the table of contents
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Doesn't look that way from the table of contents. As far as I remember, Uncle Bob's book "Agile Software Development - Principles, Patterns, Practices" has a chapter on Pair Programming, though.
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Ilja Preuss:
Doesn't look that way from the table of contents.


Nor from reading the book.
 
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It is well know that code review is very effective in reducing bugs and improving code quality. Be it agile, when two developer are working over the same code, where review is happening while it is being coded, or when it is done by peer once a developer has finished with. Both has positive effect on the code.

But there are other trick issues involved with it some organizations.


You many want to look at this
http://smartbearsoftware.com/codecollab-book-review.php

There are two more books good books on this, i will try to get this information and post it later.

Thanks,
Vijay Venkataraman
 
Author
Posts: 76
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Adeel Ansari:
Is there any emphasis on continuous inspection in the book. I mean how we should practice this. Or may be best practices or something?



Indeed there is. The idea is simple. We should constantly and continuously improve our code. The book talks about the "Boy Scout Rule" which is that we should always check our code in just a bit cleaner than when we checked it out.
 
Adeel Ansari
Ranch Hand
Posts: 2874
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks, Uncle Bob.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic