Hate to be that guy but you're likely holding the tool wrong. Being an expert does not guarantee you're one of those people who can easily get good results from an (frontier) LLM.
Just because it's easy to post doesn't mean you have to press submit on every thought that comes to your head. It's okay to admit you're working off of a very "self-taught" understanding.
If you think the job is just writing code then yes you are screwed, just like if you thought your job was just making punch cards. In most roles you have more responsibilities than plainly converting words into text. You're probably not being paid to simply be a human calculator (otherwise you'd be paid a lot less!).
It only needs additional context and work if you are unfamiliar with the concepts underlying it. Possibly consider you are out of your depth here, rather than jumping to conclusions.
It's primarily used by people who tend to sit on the cutting edge e.g. startups and developers who follow the latest tools. It's not well worn enough to be adopted by slower enterprise environments. Bun is well known within web development but if you don't work in the space and don't keep up to date with modern tooling it's unlikely you would have awareness of it.
It is not "absolutely" something that can lead to injury. Injury itself is difficult to define, and often the reason one experiences pain sensation is multifactorial. Within lifting contexts, generally the factor which has the strongest evidence for injury prediction is how sharply an athlete increases intensity compared to what they have previously adapted to.
No offense, but this post does come across as you only having a surface level understanding of the field. Especially surrounding injury/pain perception, I would be more careful of what you assume is true, there's far more nuance.
As someone who has been very deep down this rabbit hole and hacked together multiple path and velocity trackers over the years (specifically for olympic weightlifting), there is no extra information that tracking bar path will give you that simply looking at the video won't, and often just adds more clutter. You don't need to graph bar path to see that the bar is looping too far forward after hip contact in the snatch.
Velocity on the other hand is a great metric to track and is used as a proxy for RPE. Mike Tuchscherer was the first one to systematize it for powerlifting a while back, if you've been lifting for 20 years you're probably aware of the name.