Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Programmer excuses

programmerexcuses.com

Post reply on HN
Print view View original

61–69 of 69 posts

Re: Programmer excuses

#64

Post by ShaneOG »

vardump wrote: post #21
fbernier wrote: post #2

git commit -m "$(curl -s programmerexcuses.com | sed -n '/ >/{s/ ] >//g;p}')"

I'd like to commit a bugfix: git commit -m "$(curl -s programmerexcuses.com | sed -n '/ /{s/ ]*>//g;p}')"

And for any OS X user (* BSD based sed)

  curl -s programmerexcuses.com | sed -n -e '//{s/]*>//g;' -e 'p' -e '}'

  git commit -m "$(curl -s programmerexcuses.com | sed -n -e '//{s/]*>//g;' -e 'p' -e '}')"

Re: Programmer excuses

#65

Post by giblaz »

lfuller wrote: post #63
paulftw wrote: post #9

Great idea, but after trying it dozen times I still didn't get the most common excuse: "works fine on my machine"

This is why Vagrant / Chef is so great.

Yesir. I'm using Puppet myself and it's saving me boatloads of time and energy and brainwracking.

The fact that it can be used not just for Vagrant but for setting up your nodes on a cloud infrastructure is kind of overpowered :D

Re: Programmer excuses

#66

Post by democracy »

paulftw wrote: post #9

Great idea, but after trying it dozen times I still didn't get the most common excuse: "works fine on my machine"

You know sometimes it is a polite way to say that " it is YOU who messed it up, so why don't you analyze what you have or have not done and try to fix it"
Post reply on HN