It's all fun and games until you have to implement goingToCrashIntoEachOther()
// TODO: needs improvements but works 99% of the time
return false;
This looks good. PR approved.
return (staticCrashCounter++ % 100 == 0 ? true : false);
To improve that, you could get rid of the comment to save space.
void dont() {
fuckenNoseDiveLmao();
}
Well I think goingToCrashIntoEachOther needs to return another drone object. Then don't can take that object. Based on self.serialNo and other.serialNo a mutually beneficial avoiding manoeuvre could be executed.
If you're about to crash into more than one other drone.. Good luck the function specifies "EachOther" meaning just one other drone!
this calls for a whiteboard
Did a Japanese lunar probe write this?
You leaked the code for when it's out of warranty
Or when your subscription to braking has lapsed.
Love me some clean code. Just please don't look at the function definition or ever expect me to change my pyramid of abstractions.
That's what interns are for.
for the person who wrote that "coding and algorithms" is the same as "magic and alchemy"
if (launch) {
landOnMoon()
}
What's so hard, Japan?!? Sheesh.
Hey, the code was executed perfectly. The orientation wasn't defined!
You could even say it self-optimized and saved fuel by not decelerating!
I think they call algorithms AI these days. At least I caught one of our VPs saying that a few months ago.
I think the vast majority of people has no idea how coding works, doesnt know what an algorithm does and is oblivious to the fact that AI isnt everything its hyped to be.
I had a manager 10 years ago tell me we should start using these "API" things he had just read about. A conspicuously non-technical manager, obviously.
I work in IT. My boss is by all accounts very competent in both programming and administration, yet all his documentation basically says "remember to set DoTheRightThing=True"
Edit: I just looked up the documentation for an internal service and under "Error recovery" it just says "The output of command xy should make sense". fml
#pragma OccasionallyCrash false
Damn, I must've been missing this in my code the whole time.
Not even joking, I've got a project that crashes the MSVC linker with "Internal compiler error occurred" like 1 out of every 5 builds.
Back in the olde days of programming (I'm talking about compilers from the 80s) the coding connoisseur knew that getting a certain error that seemed like nonsense could easily be solved by adding an extra, or removing a remark line from the top of the code and recompiling.