Run it in your head, find the edge cases yourself, fix the bug… weakling.
Or do what I do in real life which is patch in new bugs and even a security flaw or two.
the energy of a chaotic neutral?
“maybe it’ll work, maybe it won’t, but it’ll be FUN”
or chaotic evil?
"naw. fuck y’all’s weekend.
Merging failing tests so everybody else has failing tests and wastes time figuring out why.
Nothing neutral here
I haven’t played DnD in like 20 years. Is “Chaotic Dickhead” an alignment now?
That’s what the pipeline is for. It’s not that hard to pinpoint the commit that lead to the errors.
If I rebase my branch with main I do not expect any failing tests. If you waste my time merging shit code, fuck you. Fix your shit.
Unless prod is on fire and the CEO is prowling (even then, I’d argue standards should be maintained)
“maybe it’ll work, maybe it won’t, but it’ll be FUN”
Flashback to that Tom Cruise Scientology interview 🤣:
It really is … Fun.
Tests are just booby traps for the other engineers so they don’t break your code by mistake.
Its funny cause its true. I often design tests to be “if a case/enum value is added this test will explode and tell them to add code here”
Saaaaame. But sometimes even strongly typed stuff wont break on compilation time
Real programmers test in production.
Oh I trust my code, but I don’t trust my coworkers not to break something on the very next commit.
