You say lazy like it's a bad thing.
Programmer excuses
51–60 of 69 posts
Re: Programmer excuses
#52I got "The third-party API is not responding" the first time, and I thought for a second that it was a 500-class server error. Then I reloaded, and laughed.
Re: Programmer excuses
#53git commit -m "$(curl -s programmerexcuses.com | sed -n '/ >/{s/ ] >//g;p}')"
You read my mind.
I would have preferred a more client-aware response, similar to http://ifconfig.me/, so that you can save the sed call.
Re: Programmer excuses
#54"Internal Server Error" is also an excuse?
Re: Programmer excuses
#55Great idea, but after trying it dozen times I still didn't get the most common excuse: "works fine on my machine"
Re: Programmer excuses
#56My favorite excuse so far: http://i.imgur.com/X0aFVfy.png
What did you type in wrong to get it to crash?
Re: Programmer excuses
#57What about the heisenbugs, the ones which disappear as soon as I try to debug them?
Re: Programmer excuses
#58git 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}')"
www.whatthecommit.com alternative to this:
git commit -m "$(curl -s http://whatthecommit.com | grep -o '.*' | sed 's|]*>||g')"
Re: Programmer excuses
#59git 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}')"
Or you can use it in your post-commit hook:
Re: Programmer excuses
#60Does anyone know where to find the full list of excuses?