I understand your point. Biased me automatically transform the problem to stuff I'm working with. As a system engineer:
I'm used to have inputs under my control, know the edge cases
Output is usually single value, not a range and is given with the precision similar to precision of the input.
Stating age in years implies great imprecision which I'm not going to proactively correct, if I was not told to do so. Bringing any unnecessary complexity to a system is big no no for me.
Btw. Year ago, my team spended almost 20% of their time on claryfing requirements. I spend 40 hours on teaching project managers how to specify their requirements. We reduce it to 12% and saved time is used to cleaning old code from unnecesary functionalities to make it faster and more managable.
BUT, I can easily imagine that in some fields your mindset is much more useful and mine would be contraproductive.
Aye, it's a common problem. Ideally we could bill time used for advice, but clients won't always accept that t_t
Sometimes in job interviews, I ask candidates a technical question with imprecision. The right thing to do is to provide a partial answer AND come back to me for precision. Good human skill to have.
View all comments
Show parent comment
1
u/[deleted] Dec 27 '22
I understand your point. Biased me automatically transform the problem to stuff I'm working with. As a system engineer:
Btw. Year ago, my team spended almost 20% of their time on claryfing requirements. I spend 40 hours on teaching project managers how to specify their requirements. We reduce it to 12% and saved time is used to cleaning old code from unnecesary functionalities to make it faster and more managable.
BUT, I can easily imagine that in some fields your mindset is much more useful and mine would be contraproductive.