Crashes DESTROYED with CODING and ALGORITHMS.
“big air” is hating these revolutions [spinning fan emoji]
yea, pretty much like that
For a sufficiently defined “goingToCrashIntoEachOther” and “don’t”, isn’t that basically how it works?
Well, even at that level of abstraction, it’s a bit weird, because
goingToCrashIntoEachOtheranddont()both need the information from where a collision is going to take place, so you’d expect something to be passed intodont().Well, and it’s easy to dismiss this stuff as implementation details, but that if-statement needs to run as part of a loop. This loop should probably be on a separate thread, so it doesn’t get blocked by other stuff going on. Which means access to the motors needs to be behind some form of mutex, which it needs to be able to acquire fairly quickly. And then, yeah, those implementation details quickly add up to become the part that’s actually complex.
It definitely should be, but at some point in time, very intelligent people though that this was a Good Thing:
bReadLine(bPort,&arru8NumberList)
These days they’d write “AI” and you’d be none the wiser, because even if it involves a machine learning model (which is definitely not a given either), they will still have used quite a lot of coding and algorithms to tie it all together.
I like to mentally substitute these terms with “magic”. Because ultimately, it just means that they don’t want to explain it to you, but they need to tell you something, so you don’t ask about it.
Whoah, coding and algorithms???
I think you mean magic and miracles!
Magnets, how they work?
If {not_broken} then {fix_it_anyway};
; }
This is actually how I would start out if I were developing this algorithm. I always start with the highest-level code first, then flesh out all the details in function definitions.
plsAndThankYou
