Re:A guide for how to talk to a developer
by throwaway2016a on Wednesday May 23, 2018 @02:12PM
(#17136516)
Rather than memorize a bunch of flash cards it seems much easier to just talk to them like humans and if they say something you don't understand don't be embarrassed to ask them what it means.
[ Parent
| on HN ]
I know non-technical people who, when they think they are hearing anything remotely technical, seem to shut down and go into "I don't know technical stuff!" mode...
Not that flashcards are going to cure _that_.
I think you're right. I also know technical people who obscure gaps in their own knowledge with jargon. So clarifying questions that might expose the gap are responded to with increasingly technical rambling. Bad habits all around, feeding off each other.
Increasingly technical rambling is good. What I hate is when techies start to imply that whoever they talk with is an idiot after they reach limit of their knowledge. That tactic is used surprisingly often.
It makes people scared to ask and passive.
Re:A guide for how to talk to a developer
by IshKebab on Wednesday May 23, 2018 @05:00PM
(#17138237)
No he means increasingly technical rambling that is also meant to obscure the fact that they don't know the answer. Definitely not good.
Re:A guide for how to talk to a developer
by LyndsySimon on Wednesday May 23, 2018 @03:16PM
(#17137209)
True, but one-sentence explanations can be helpful for managers and PMs that aren't familiar with the specific tech stack to get up to speed quickly.
I don't think this is a bad idea per se, but I do think that it's got a long way to go before it's really useful (or even correct).