Devloper Excuses (extracted from http://developerexcuses.com/)

excuses.json

[
   "That code seemed so simple I didn't think it needed testing",
   "That isn't covered by my job description",
   "I can't test everything",
   "That's not a bug it's a configuration issue",
   "That wasn't in the original specification",
   "It's just some unlucky coincidence",
   "Oh, you said you DIDN'T want that to happen?",
   "There were too many developers working on that same thing",
   "I have too many other high priority things to do right now",
   "We outsourced that months ago",
   "Why do you want to do it that way?",
   "It's an unexpected emergent behaviour of several last minute abstractions",
   "Nobody has ever complained about it",
   "Our internet connection must not be working",
   "I couldn't find any library that can even do that",
   "It probably won't happen again",
   "I couldn't find any examples of how that can be done anywhere else in the project",
   "The original specification contained conflicting requirements",
   "I thought I finished that",
   "I broke that deliberately to do some testing",
   "I must have been stress testing our production server",
   "Well at least we know not to try that again",
   "The specifications were ambiguous",
   "That's already fixed it just hasn't taken effect yet",
   "Our redundant systems must have failed as well",
   "Where were you when the program blew up?",
   "How is that possible?",
   "We didn't have enough time to peer review the final changes",
   "It's a browser compatibility issue",
   "It worked yesterday",
   "That feature would be outside of the scope",
   "Even though it doesn't work, how does it feel?",
   "I'll have to fix that at a later date",
   "Nobody asked me how long it would actually take",
   "It was working in my head",
   "That wouldn't be economically feasible",
   "We should have updated our software years ago",
   "Our hardware is too slow to cope with demand",
   "That's the fault of the graphic designer",
   "It works for me",
   "I haven't touched that code in weeks",
   "I forgot to commit the code that fixes that",
   "This code was not supposed to go in to production yet",
   "It's not a code problem - our users need more training",
   "There's currently a problem with our hosting company",
   "The third party API is not responding",
   "I didn't anticipate that I would make any errors",
   "I didn't receive a ticket for it",
   "The accounting department must have cancelled that subscription",
   "The third party documentation doesn't exist",
   "The client wanted it changed at the last minute",
   "It's a known bug with the server software",
   "That was literally a one in a million error",
   "No one told me so I was forced to assume which way to do that",
   "The client must have been hacked",
   "That error means it was successful",
   "The request must have dropped some packets",
   "It's always been like that",
   "It works, but it's not been tested",
   "What did I tell you about using parts of the system you don't understand?",
   "I heard there was a solar flare today",
   "That important email must have been marked as spam",
   "It must be because of a leap year",
   "I'm not getting any error codes",
   "Well done, you found my easter egg!",
   "That behaviour is in the original specification",
   "I told you yesterday it would be done by the end of today",
   "I can have a look but there's a lot of if statements in that code!",
   "There was too little data to bother with the extra functionality at the time",
   "It's a known bug with the programming language",
   "I thought he knew the context of what I was talking about",
   "I'm not familiar with it so I didn't fix it in case I made it worse",
   "I'm surprised that was working at all",
   "Oh, that was only supposed to be a placeholder",
   "It's never shown unexpected behaviour like this before",
   "It's a third party application issue",
   "Well, at least it displays a very pretty error",
   "The problem seems to be with our legacy software",
   "The project manager told me to do it that way",
   "It must be because of a leap second",
   "Our code quality is no worse than anyone else in the industry",
   "There must be something strange in your data",
   "What did you type in wrong to get it to crash?",
   "I thought I fixed that",
   "It would take too long to rewrite the code from scratch",
   "In the interest of efficiency I only check my email for that on a Friday",
   "The marketing department made us put that there",
   "I have never seen that before in my life",
   "The code is compiling",
   "Maybe somebody forgot to pay our hosting company",
   "I'm still working on that as we speak",
   "It must be a hardware problem",
   "Actually, that's a feature",
   "I was told to stop working on that when something important came up",
   "Management insisted we wouldn't need to waste our time writing unit tests",
   "That feature was slated for phase two",
   "That's interesting, how did you manage to make it do that?",
   "The person responsible doesn't work here anymore",
   "It would have taken twice as long to build it properly",
   "The existing design makes it difficult to do the right thing",
   "That process requires human oversight that nobody was providing",
   "That code was written by the last guy",
   "I thought you signed off on that?",
   "My time was split in a way that meant I couldn't do either project properly",
   "I must not have understood what you were asking for",
   "It must be a firewall issue",
   "I'm surprised it works as well as it does",
   "I haven't been able to reproduce that",
   "I haven't had the chance to run that code yet",
   "It's never done that before",
   "I haven't had any experience with that before",
   "The program has never collected that information",
   "I can't make that a priority right now",
   "Your browser must be caching the old content",
   "The unit test doesn't cover that eventuality",
   "I didn't create that part of the program",
   "I had to do the project backwards as people demanded results out of order",
   "The WYSIWYG must have produced an invalid output",
   "It can't be broken, it passes all unit tests",
   "You're doing it wrong",
   "You must have done something wrong",
   "It's a character encoding issue",
   "This is a previously known bug you told me not to work on yet",
   "The project manager said no one would want that feature",
   "I did a quick fix last time but it broke when we rebooted",
   "THIS can't be the source of THAT",
   "I usually get a notification when that happens",
   "Well, that's a first",
   "I'm not sure as I've never had a look at how that works before",
   "We spent three months debugging it because we only had one month to build it",
   "You must be missing some of the dependencies",
   "The download must have been corrupted",
   "Did you check for a virus on your system?",
   "Oh, that was just a temporary fix",
   "I couldn't find any examples of how that can be done anywhere online",
   "I was just fixing that",
   "That worked perfectly when I developed it",
   "Don't worry, that value is only wrong half of the time",
   "It's a remote vendor issue",
   "Everything looks fine my end",
   "You can't use that version on your system",
   "The third party documentation is wrong",
   "Somebody must have changed my code",
   "The user must not know how to use it",
   "You must have the wrong version"
]