A guide for how to talk to a developer
hatchapps.com
A guide for how to talk to a developer
1–10 of 45 posts
Re: A guide for how to talk to a developer
#2It looks like it's just several flash cards to help managers talk like Pointy Haired Boss from Dilbert.
Re: A guide for how to talk to a developer
#3Some of these are just wrong. "Django" is not "A style sheet language that extends from CSS."
Re: A guide for how to talk to a developer
#4If you’re a manager of developers and you need these cards to tell you what some of these things are (database, stack...) you probably shouldn’t be managing developers.
Re: A guide for how to talk to a developer
#5Some of these are just wrong. "Django" is not "A style sheet language that extends from CSS."
Now you ruined the fun of some boss trying to say he understands Django :(
Re: A guide for how to talk to a developer
#6Rather 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.
Re: A guide for how to talk to a developer
#7Surely as developers we should be able to reduce or explain our use of jargon for the person we're speaking to, rather than the rest of the world having to learn our industry-specific language?
Re: A guide for how to talk to a developer
#8It looks like it's just several flash cards to help managers talk like Pointy Haired Boss from Dilbert.
It is. And it should be titled as such. The current title calls it a "guide", which is misleading.
Re: A guide for how to talk to a developer
#9[deleted]
Re: A guide for how to talk to a developer
#10Surely as developers we should be able to reduce or explain our use of jargon for the person we're speaking to, rather than the rest of the world having to learn our industry-specific language?
I try not to use any jargon at all when communicating to non-dev stakeholders, and they still complain about jargon.
Words like "server" or "database" are not jargon. There are literally no other words to use for those things. And if you don't want to hear any technical-sounding words at all, then don't ask technical questions. Or better yet, don't work at a tech company.