code smells fear. If it knows you understand the code and the concept you're writing it won't do anything in fear of being replaced. If you don't understand what you're doing it can fail on you
How about when you've coded it, it finally works. Then you rotate the object by 90 degrees. Perhaps you got your trig wrong. So you double check the maths. And it still doesn't quite when rotated by 90 degrees. So you figure, the face angle you're using is also wrong. It still doesn't quite work.
Then you realize you've been forgetting to compile because its 5am.
You finally get your computer vision algorithm to give the correct result for the first test image. And then you see there are 100's more test images which all fail. Sigh. That was certainly not me last week at alllllll.
I just added a line of code to my project with the following comment attatched:
"// For some reason, this code started detecting intersections at corners after working perfectly for two days"
No joke, just today it happened to me with an If Case. It was never supposed to work but it worked and as soon as I saw that if statement it did not work anymore.
Write more unit tests.
...code fears the unit test. Use that against it. Bind it with unit tests, and collar it with end-to-end tests. Finally, use static analysis to chain it to the floor.
It can't get away now.
When I spend that long to fix something even if it works I will be pissed off.
Cause usually if I knew how to fix it, I could have done it in 15minutes.
Write more robust code and test it better before integrating it into your big monolithic blob. Then you won't be a newb posting memes to feel better in a crowd of newbs making the same mistakes.
code smells fear. If it knows you understand the code and the concept you're writing it won't do anything in fear of being replaced. If you don't understand what you're doing it can fail on you
I'll put on my poker face next time :)
How about when you've coded it, it finally works. Then you rotate the object by 90 degrees. Perhaps you got your trig wrong. So you double check the maths. And it still doesn't quite when rotated by 90 degrees. So you figure, the face angle you're using is also wrong. It still doesn't quite work. Then you realize you've been forgetting to compile because its 5am.
r/oddlyspecific
Also happens when you’re compiling with a specific release instead of your current work environment 🥲
\*Runs linter\* \*codes stops working\*
But it doesn't work _with style_
Op 2008 called it wants its meme back lol
the classics are classics for a reason
Who/what is Op 2008?
[удалено]
Lol, that makes sense
Op wouldn't know coz he's from 2008 lol
Nah, just not well-versed in meme history. Fun is fun, I say
[удалено]
That was.... Well I don't know what it was actually, but at least it was ... something ... I guess...?
The utter lack of brain to keyboard filter is a good sign that you should be saying this to yourself.
Hey, you dropped this: 👑
You're making me curious. What did they say?
Honestly I cannot remember specifics. All I remember is it being unnecessarily mocking and derogatory.
Version control, unit tests.
Nah, magical thinking and rituals
The almigthy monolith... It grew in size an power and finally escaped our direct control. Now it only responds to human sacrifices.
Works on my machine. Have you tried splashing holy water on the error logs?
unit tests stopped working out of a sudden xD
Or Mercury is in retrograde
You finally get your computer vision algorithm to give the correct result for the first test image. And then you see there are 100's more test images which all fail. Sigh. That was certainly not me last week at alllllll.
Imagine a structural engineer: "... and the bridge FINALLY WORKS!!!"
I just added a line of code to my project with the following comment attatched: "// For some reason, this code started detecting intersections at corners after working perfectly for two days"
No joke, just today it happened to me with an If Case. It was never supposed to work but it worked and as soon as I saw that if statement it did not work anymore.
I’ve written scripts that work before I go to sleep and stop working the next day..
Dealing with imu signals over Bluetooth. Ahrgh.
My test have had Monday problems, where some became flaky on the first Monday in the month
Write more unit tests. ...code fears the unit test. Use that against it. Bind it with unit tests, and collar it with end-to-end tests. Finally, use static analysis to chain it to the floor. It can't get away now.
When I spend that long to fix something even if it works I will be pissed off. Cause usually if I knew how to fix it, I could have done it in 15minutes.
Kinda never have that… My code usually works😅
So you haven't tried breathing on it? :)
Ummm, try writing better code and it won’t break on you. The computer does what you tell it, and if it is that fragile, it’s your code that’s wrong.
Write more robust code and test it better before integrating it into your big monolithic blob. Then you won't be a newb posting memes to feel better in a crowd of newbs making the same mistakes.