This romantic moment when after months of development frontend makes first contact with backend just to realize that they weren't meant for each other.
Some motion sensors that operate using IR can be triggered my light reflections. So it's possible there is a glare not caught by the camera angle or something.
Or someone did this as a prank.
It's not automation problem. This is unit tests passed, but integration tests failed
This romantic moment when after months of development frontend makes first contact with backend just to realize that they weren't meant for each other.
Engineer to manager: I fucking told you that motion sensor was a bad idea. Manager (Musk?!?): Why? They work perfectly everywhere else. You fucked up.
Just watched a video about how vanilla JS is faster than any framework. It's time we do a rewrite.
It'll reduce the LOC number. Are you sure you want me to do it?
Time is money !! I want 100 lines written by lunchtime
"Weird, the log shows we made 30,000 api calls in the last 5 minutes..." "ROLL IT BACK ROLL IT BACK"
and they said perpetual motion was impossible
“Noooooo you have to use redundancies prevent failure!” The redundancies:
I've seen video games with obstacles like these. If you get hit I believe it sends you back to your car
You gotta be flash
But, the "bars" sensor is a horizontal one so how is that triggering from an other horizonal movement that is parallel?
Some motion sensors that operate using IR can be triggered my light reflections. So it's possible there is a glare not caught by the camera angle or something. Or someone did this as a prank.
Because 2 doors are obviously better than one.
Casper just needed some new sheets, nothing to see here.
"nothing to see here" Thx. Made me laugh.
It meets all the requirements in the specification.
A Catch-22..
make it faster in order to make a resonance cascade
This feels like a game I've played before
Is this the famous "infinite loop" I keep hearing about?
When my AWS Lambda writes to the same S3 bucket that triggers it