3 ms·
I think this isn’t justified. There’s people who are control freaks, but it’s not necessarily OPs case. In a product I delivered (I do hardware design), I help
by xondono 5y ago
I think this isn’t justified. There’s people who are control freaks, but it’s not necessarily OPs case.
In a product I delivered (I do hardware design), I helped the “firmware team” (one guy at that point) to get started because I was more experienced, and stuck helping with some small modules to get things ready for demos and things of that nature.
Later the team expanded, so I let go of firmware development and went back to my work, and the code slowly changed to the point that I wasn’t really aware of what the device did in scenario X, much less how it did that.
I still was the go-to guy when it came to questions about the device behavior for months, even if all my replies where “I have no idea, ask this people”.
All it takes is for someone to say “that guy has been working on this since the beginning”, and a lot of questions will find your inbox when others are unsure about the answer.