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

excuses.json

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

دمت گرم

دمت گرم

ممنون 💙

These are the best excuse, but not every time! 😅

These are the best excuse, but not every time!

it means you have lots of experience 😆 😄