4 ms·
Shouldn't have to. Should be able to talk intelligently about what you do and that should be enough. If I write SW that interacts with RFID readers, I should be
by JustSomeNobody 9y ago
Shouldn't have to. Should be able to talk intelligently about what you do and that should be enough. If I write SW that interacts with RFID readers, I should be able to talk about the various protocols. I should be able to talk about poll vs push and the benefits (and pains) of both. I should be able to talk about how to architect a performant system that gets the data from the devices, processes it and sends it on to some other device.
I should not have to worry about not being able to show any of that. If the people interviewing me don't understand what I did without me showing them, then I am certainly applying at the wrong company.
- rapind 9y agoI once wrote some software that needed to interact with RFID readers. I couldn't talk about protocols then and I still can't today, but the program is still running just fine 10 years later. Don't underestimate the value of some general understanding / intuition of how systems will probably work combined with a little googling.
- martijn_himself 9y agoI agree. I also read somewhere that talking about past behaviors (e.g. how you solved a complex issue) is the best indicator for competency (I can't back that up with sources sorry). On a side note I also worked with RFID readers, they were yesteryear's Internet of Things :).