Try Usersnap for Product Development<\/h2>Try Usersnap Now<\/a><\/div>\n\n\n\n1. \u201cHow hard can that be.\u201d<\/h2>\n\n\n\n![\"developer](\"https:\/\/usersnap.com\/blog\/wp-content\/uploads\/2016\/06\/howhardcanthatbe-dev-talk.png\")
<\/a><\/figure>\n\n\n\n<\/p>\n\n\n\n
I guess it\u2019s one of the most-used phrases non-developers use in order to annoy developers. That can\u2019t be that difficult. How hard can that be. Similar phrases are (which of course I also recommend avoiding):<\/p>\n\n\n\n
\n- Why does that take soooo long?<\/li>\n\n\n\n
- Can\u2019t you just speed it up a bit and do it faster?<\/li>\n<\/ul>\n\n\n\n
No matter, which kind of phrases you use. If you try to be the development expert as a non-developer, you won\u2019t have any chance to win that game. Trust your developer\u2019s expertise and rely on strategic HR management<\/a> to ensure you have a capable and skilled development team in place to drive success in your projects.<\/p>\n\n\n\nWhat to say instead:<\/strong><\/p>\n\n\n\n\n- Could you please give me some insights on how the resource calculation was done?<\/li>\n\n\n\n
- Which sub-tasks need to be completed in order to finish that project?<\/li>\n<\/ul>\n\n\n\n
2. \u201cI don\u2019t know how to code, that\u2019s your job.\u201d<\/h2>\n\n\n\n![\"I](\"https:\/\/usersnap.com\/blog\/wp-content\/uploads\/2016\/06\/dont-code-1024x512.png\")
<\/a><\/figure>\n\n\n\n<\/p>\n\n\n\n
Well, ok. Obviously, you do not know how to code and it\u2019s definitely not your responsibility in your project or company.<\/p>\n\n\n\n
But I heard this sentence quite a few times when people don\u2019t feel confident talking with a developer. And the main reason is that people don\u2019t know enough to feel confident.<\/p>\n\n\n\n
\u201cI don\u2019t know how to code, and that\u2019s your job\u201d often simply describes the shortcut non-developers try to go. Instead of actually thinking and dealing with the task.<\/p>\n\n\n\n
What to say instead:<\/strong><\/p>\n\n\n\n\n- I do not know how to describe that problem. Would you mind helping me out?<\/li>\n<\/ul>\n\n\n\n
3. \u201cMy neighbor\u2019s son can do that for $10 an hour.\u201d<\/h2>\n\n\n\n![\"developer](\"https:\/\/usersnap.com\/blog\/wp-content\/uploads\/2016\/06\/neighborsson.png\")
<\/a><\/figure>\n\n\n\n<\/p>\n\n\n\n
Well, that\u2019s great. Please go to your neighbor’s son and hire him. He might even be a great developer. But chances are high that he\u2019s not doing it on a professional level.<\/p>\n\n\n\n
Don\u2019t compare your developer to a 16-year old geek.<\/p>\n\n\n\n
What to say instead:<\/strong><\/p>\n\n\n\n\n- There\u2019s nothing to say instead. Simply don\u2019t say this to any developer working in a professional environment.<\/li>\n<\/ul>\n\n\n\n
4. \u201cSo, you\u2019ve only written these few lines of code in … days?\u201d<\/h2>\n\n\n\n
This is quite a common mistakes a lot of non-developers fall into. Judging the work of a developer by the amount of lines of code written is truly a big one.<\/p>\n\n\n\n
You don\u2019t judge your project manager by the amount of emails she wrote, right? So, better do not judge your developers by the amount of lines of code they write.<\/p>\n\n\n\n
It\u2019s even the other way around. The less code, the better.<\/p>\n\n\n\n
<\/a><\/figure>\n\n\n\n<\/p>\n\n\n\n
I guess it\u2019s one of the most-used phrases non-developers use in order to annoy developers. That can\u2019t be that difficult. How hard can that be. Similar phrases are (which of course I also recommend avoiding):<\/p>\n\n\n\n
- \n
- Why does that take soooo long?<\/li>\n\n\n\n
- Can\u2019t you just speed it up a bit and do it faster?<\/li>\n<\/ul>\n\n\n\n
No matter, which kind of phrases you use. If you try to be the development expert as a non-developer, you won\u2019t have any chance to win that game. Trust your developer\u2019s expertise and rely on strategic HR management<\/a> to ensure you have a capable and skilled development team in place to drive success in your projects.<\/p>\n\n\n\n
What to say instead:<\/strong><\/p>\n\n\n\n
- \n
- Could you please give me some insights on how the resource calculation was done?<\/li>\n\n\n\n
- Which sub-tasks need to be completed in order to finish that project?<\/li>\n<\/ul>\n\n\n\n
2. \u201cI don\u2019t know how to code, that\u2019s your job.\u201d<\/h2>\n\n\n\n
<\/a><\/figure>\n\n\n\n<\/p>\n\n\n\n
Well, ok. Obviously, you do not know how to code and it\u2019s definitely not your responsibility in your project or company.<\/p>\n\n\n\n
But I heard this sentence quite a few times when people don\u2019t feel confident talking with a developer. And the main reason is that people don\u2019t know enough to feel confident.<\/p>\n\n\n\n
\u201cI don\u2019t know how to code, and that\u2019s your job\u201d often simply describes the shortcut non-developers try to go. Instead of actually thinking and dealing with the task.<\/p>\n\n\n\n
What to say instead:<\/strong><\/p>\n\n\n\n
- \n
- I do not know how to describe that problem. Would you mind helping me out?<\/li>\n<\/ul>\n\n\n\n
3. \u201cMy neighbor\u2019s son can do that for $10 an hour.\u201d<\/h2>\n\n\n\n
<\/a><\/figure>\n\n\n\n<\/p>\n\n\n\n
Well, that\u2019s great. Please go to your neighbor’s son and hire him. He might even be a great developer. But chances are high that he\u2019s not doing it on a professional level.<\/p>\n\n\n\n
Don\u2019t compare your developer to a 16-year old geek.<\/p>\n\n\n\n
What to say instead:<\/strong><\/p>\n\n\n\n
- \n
- There\u2019s nothing to say instead. Simply don\u2019t say this to any developer working in a professional environment.<\/li>\n<\/ul>\n\n\n\n
4. \u201cSo, you\u2019ve only written these few lines of code in … days?\u201d<\/h2>\n\n\n\n
This is quite a common mistakes a lot of non-developers fall into. Judging the work of a developer by the amount of lines of code written is truly a big one.<\/p>\n\n\n\n
You don\u2019t judge your project manager by the amount of emails she wrote, right? So, better do not judge your developers by the amount of lines of code they write.<\/p>\n\n\n\n
It\u2019s even the other way around. The less code, the better.<\/p>\n\n\n\n
- There\u2019s nothing to say instead. Simply don\u2019t say this to any developer working in a professional environment.<\/li>\n<\/ul>\n\n\n\n
- I do not know how to describe that problem. Would you mind helping me out?<\/li>\n<\/ul>\n\n\n\n