Never intended on it. But to respond to “can you say when this is useful” with a string of complicated looking math comes across as elitist and could be off putting to students who maybe aren’t quite there. Far too often I see people dismiss solutions that are simpler as “garbage” and instead refer people to whatever crazy thing 254/971 is doing these days.
Not all systems need accurate motion profiling, sometimes you can get away with a limit switch or two It’s an important business lesson to.
Recently I had one of our C suite folks declare he wanted to redo how we manage version numbers internally. I pushed back as we are a small team and tried to understand the problem he was really solving which, as it turns out, was that he didn’t like how they were displayed in the UI. So we were able to bunt a complex change (lots of different systems use that version number) into a relatively low risk UI change because we understood the problem space.
Now, I am a fairly experienced engineer who also happens to have a bit of a reputation for not biting my tongue on things. I have absolutely no problem pushing back to understand the problem. However, when a 10th grader who barely groks PID sees some of us talking about arbitrary feed forwards and calling solutions that ARE viable ■■■■ they aren’t going to be able to identify the particular circumstances under which PID isn’t enough.
Communication is hard yo, we should strive to suck less at it.