Shit developers say??

"Just awk out that regex so I can sed it into my grep script and pipe 1 to curl."

"why should i test this? is an easy fix.."

@nanhb followed shortly by "well it worked in my machine"

"Yes, I'll do that soon"

Translation:
Maybe somewhere this year if I feel like it but probably not

It's cache

If it works...don’t touch it lol

"I did it like it was done before. I think refactoring the whole file will be overkill"
To lines with 160-200 characters.

After that main maintainer said it was fine. I tried to explain him why this is bad idea but he was dickhead...

"yeah I know that this issue exist, we will MAYBE fix it next year"

This is not how it works. This is not how ANY of it works.

"Yo tony where'd u get that fresh pepperoni"

"You fucking kidding me rn"

"please goddamnit just work this time"

"but this time its different"

"Worked on my machine!"

"We disabled tests/linting/peer review/basic human sanity to get this out the door because it was crunch time"

(after an extremely basic js or css issue) "I can't fix this because I'm a backend developer..."

(after an extremely basic server side or DB error) "I can't fix this because I'm a front-end developer..."

Try turning it off and on again.

Unit tests are pointless and just another thing to maintain.

What? How?

"How is this working?"

.