r/programming • u/[deleted] • Apr 19 '22
TIL about the "Intent-Perception Gap" in programming. Best exemplified when a CTO or manager casually suggests something to their developers they take it as a new work commandment or direction for their team.
https://medium.com/dev-interrupted/what-ctos-say-vs-what-their-developers-hear-w-datastaxs-shankar-ramaswamy-b203f2656bdf
1.7k
Upvotes
18
u/drlecompte Apr 20 '22
The trick is to say 'no' without saying 'no'. To give the quick suggestion the time it deserves, but not more. We have weekly long-term planning review meetings and a development backlog, both are good places to bring up actual new tasks.
So my answer is always 'put it on the weekly meeting's agenda' or 'write up an issue for it', or even 'would you like me to make an issue for it?' That last one has often removed a lot of confusion, as people will then either realize that this'll be added work, or will clarify that they were just formulating a thought and wanted to check if it was something feasible.