I found this the other day
http://www.fukung.net/images/2674/designer.gif
I find it so true, it applies to programmers too, in fact it applies to everyone that works providing a service. Enjoy.
Somewhere to write when I want to say something.
April 18th, 2008 — life
I found this the other day
http://www.fukung.net/images/2674/designer.gif
I find it so true, it applies to programmers too, in fact it applies to everyone that works providing a service. Enjoy.
April 18th, 2008 — windows, programming
Now this is a really nice one from microsoft. To reproduce:
Now my question is, why on earth are they unpacking in other letter other than c:? Even better why they don’t do a check instead of taking the last letter available?? nice way to go really, go microsoft!
April 16th, 2008 — tips, linux
Well this is something I have been wanting to do for a LONG time. But so far I didn’t found a good alternative.
I’m a long time svn user but doing this with svn presented the following issues.
Today for some reason I started reading the mercurial documentation and it just hit me, this is what I needed. Why? well…
So lets get dirty first create the repository. And lets add a basic .hgignore, I got the .hgignore file tip from here which means I’m not the first one to come up with this idea. And lets commit that.
$ cd
$ hg init
$ printf "syntax: glob\n*\n" > .hgignore
$ hg commit
Now we need to figure out which files we want to get into the repository so lets figure that out.
$ ls -a1 >> .hgignore
note, that’s a “one” it will output the file in columns, if you didn’t knew that go read the man page, you will love all the switches.
Now we need to edit the .hgignore file a bit delete the following lines
*
syntax: regexp
./
../
also delete (or comment with a #) all the lines of the files you want to version (remember this is an ignore file)
then just start adding files and when you are done commit. And now you have full history of all your changes, Which is awesome for managing your config files, remembering all the tricks in your .vim or .bashrc and exporting them to other machines.
EDIT:
* in-place import means that the original code you import into the versioning system becomes a working copy.
In SVN when you do an import the original tree does not become a working copy of the code, so you have to do an import then a checkout into the same dir from which you imported. It’s very tricky and most people don’t know about it. Although There is a way to trick svn into doing it but most people don’t know about it.