I don't think pandering to the ideas that basically amount to "a 6 week bootcamp makes you a Software Engineer" is honest or useful. It is sycophancy and disingenuous. If someone doesn't even know where to start looking for replacing a binary in a package; they have no grounds to call themselves a "Software Engineer".
Consider how would you respond if someone made a remark like this:
> Honestly, I'm always blown away by accounts [of] "so I just welded the pipes" dropped casually like this. I'm a plumber and have been for over five years, but wouldn't even know where to _begin_ with something like that.
I'd raise an eyebrow, because plumbers here are a trade with on the job training, and pipework is an essential part of it.
Software has a huge surface area these days. That a trained software engineer isn't aware that HIDs and input subsystems are often highly hackable from userspace is no surprise to me.
They may also have been leaning into a compliment of OP in a self deprecating way.
The problem isn't that you should know everything, but that you should know how to dig into these things. The op isn't even talking about HID and input subsystem, they're talking about replacing a goddamn binary in a package. It is a tiny step above working a Zip archive.
C'mon. Don't shrug me now after going all proverbial pointy finger at me for expecting an "Engineer" to know the basics.
Consider how would you respond if someone made a remark like this:
> Honestly, I'm always blown away by accounts [of] "so I just welded the pipes" dropped casually like this. I'm a plumber and have been for over five years, but wouldn't even know where to _begin_ with something like that.