« Lotus Domino Web Application Development: Wiki and a Webcast | Main| Creativity v. Compliance? »

Print Screen Isn't a Method of Source Control


Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

I am amazed at the number of people I talk to that use 'print screen' as a method for controlling their source code. The rationale is, apparently, that if the modified date for a design element is the same in this printout from last month as the printout I did today, the design must not have been changed. But does that printout tell you when someone restored that version from a backup? What happened in between? And if the date has changed, can the printout tell you why it changed? Now, I truly believe that not all applications need to be tracked, but for those that do, how can manual processes be acceptable? There are so many shortcomings with screen prints that people shouldn't even bother.

Comments

Gravatar Image1 - I work in a heavily regulated industry and we routinely use screen captures as "evidence" of compliance. I agree that this is absolutely ridiculous because it is so easy to manipulate the content being captured.

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::lips::rolleyes:;-)