3 ms·
Embedded software medical device developer here. I once worked with a hardware engineer that would verbalize his thought process very explicitly, as we worked
by jes 12y ago
Embedded software medical device developer here.
I once worked with a hardware engineer that would verbalize his thought process very explicitly, as we worked in the lab.
He would say things like: "Ok, I'm about to let the target out of reset. I expect to see the I2C bus controller initiate a master read of address 0x80."
Then he would do it, and look at the oscope, and see if his expectation was confirmed.
If it wasn't, or was fishy in any way, he'd say something like "OK, I have a mystery. I expected to see <X>, but I saw <Y> instead. I'm investigating this before I go further."
So, you get the drift.
For this guy, the rule was "NO MYSTERIES."
Working with him was a fantastic and valuable experience.
- L_Rahman 12y agoAside: I'm a biomedical engineer by way of Hopkins and would love to be able to ask you questions about medical device development. If this is something you'd be interested in, what's the best way to reach you? Conversely, my contact info is in my profile description.
- jfroma 12y agoThis is exactly my though process as a software developer. I work remotely so I dont speak out loud (most of time), but i think it helps too. It is similar to when you have been debugging something for hours and you figure the solution right away when you start explaining the problem to a coworker.
- aptwebapps 12y agoPre-emptive rubber ducking. I'd like to try it, but I'm afraid it might be a nuisance for others.
- LunaSea 12y agoThis is really interesting to me. Do you have other stories or experiences to share about programming on "strict" systems like medical devices ? Stuff like coding styles, rules, practices and the likes.