Re:Programming excuses
by orf on Friday August 07, 2015 @11:22AM
(#10022958)
I would love a list of all the excuses, they look great in error pages. I made a quick script[1] to scrape the site, but that's not as nice as a plaintext file that could just be downloaded?
Re:Programming excuses
by joeax on Friday August 07, 2015 @11:39AM
(#10023081)
I worked with a developer who would say "it worked on my box" that meant it was gold and he refused to investigate further. He was connected to the CEO so there was little we could do except work around his bugs or ignore completely.
Re:Programming excuses
by glhaynes on Friday August 07, 2015 @11:56AM
(#10023183)
This is one more reason a continuous integration system is wonderful. If it works on a developer's box but breaks the integration, it's broken by definition. (No warranty is expressed or implied that the CEO will see it that way, of course!)
Edit: Here[2] is a complete list
1. https://gist.github.com/orf/87825a18e6685144ae3b
2. https://gist.github.com/orf/db8eb0aaddeea92dfcab
https://gist.github.com/anonymous/69e8ad93f9f6aba25c8d
Oh, yeah...
EDIT: the more I refresh this page the more I think it should be called excuses for lazy coders and designers:
You can't use that version on your system
You must have done something wrong
Why do you want to do it that way?
Anyway, it's a nice, painfully accurate collection ...
Seriously? :-)