Comments on: How To (Not) Get an Interview With The Google http://bratton.com/index.php/2007/06/27/how-to-not-get-an-interview-with-the-google/ Infrequent Techy Ramblings Wed, 21 Jul 2010 14:42:44 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: ajit http://bratton.com/index.php/2007/06/27/how-to-not-get-an-interview-with-the-google/comment-page-1/#comment-118 ajit Thu, 20 Nov 2008 10:35:45 +0000 http://bratton.com/index.php/2007/06/27/how-to-not-get-an-interview-with-the-google/#comment-118 many thanks for that.. really interesting. my manager has asked me to upgrade patches on SVN in CLG! I need to know what the risks and issues are if I am to give him a detailed report on how to do this. do you have any ideas how I can do this with certaintly.. your assistance would be much appreciated sincerely ajit chambers ajitchambers@hotmail.com many thanks for that.. really interesting.
my manager has asked me to upgrade patches on SVN in CLG!
I need to know what the risks and issues are if I am to give him a detailed report on how to do this.

do you have any ideas how I can do this with certaintly..

your assistance would be much appreciated
sincerely
ajit chambers
ajitchambers@hotmail.com

]]> By: Peter Payne http://bratton.com/index.php/2007/06/27/how-to-not-get-an-interview-with-the-google/comment-page-1/#comment-51 Peter Payne Tue, 20 May 2008 16:46:25 +0000 http://bratton.com/index.php/2007/06/27/how-to-not-get-an-interview-with-the-google/#comment-51 Ah finally someone to explain what I've always suspected.. if anyone has read the book "The Pragmatic Programmer" there is a section that explains the usefulness of text - no matter what technologies are available in the future a text file will always be readable (be it an .ini file or a .xml or whatever). Stick anything into binary format and you're at the mercy of that format. I'm completely lost as to why people in the development community are moving to SVN - sure it lets you move files across directories - so what!! For this single advantage there are many potential disadvantages - you can't clean up a bad commit (imagine if someone pasted profanities all through your source, checked it in, wouldn't you like your admin to be able to remove it at some point? - you can't with SVN! Imagine if you checked in a file with your illegal indiscretions documented and then you hear a legal team has rights to discovery on your repository.. and you rush to remove those bad bits of your history - you can't with SVN!). And then you could lose your entire respository - as you just pointed out, which would never have happened with CVS. Ah finally someone to explain what I’ve always suspected.. if anyone has read the book “The Pragmatic Programmer” there is a section that explains the usefulness of text – no matter what technologies are available in the future a text file will always be readable (be it an .ini file or a .xml or whatever).

Stick anything into binary format and you’re at the mercy of that format.

I’m completely lost as to why people in the development community are moving to SVN – sure it lets you move files across directories – so what!! For this single advantage there are many potential disadvantages – you can’t clean up a bad commit (imagine if someone pasted profanities all through your source, checked it in, wouldn’t you like your admin to be able to remove it at some point? – you can’t with SVN! Imagine if you checked in a file with your illegal indiscretions documented and then you hear a legal team has rights to discovery on your repository.. and you rush to remove those bad bits of your history – you can’t with SVN!).

And then you could lose your entire respository – as you just pointed out, which would never have happened with CVS.

]]>