One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
Hi, thanks for your answer! I do understand that there is no such thing as a perfect brief, but still, I believe there are problems and pain developers are ready to explain. And this can be used to make kind of a perfect brief ;)
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
So that's interesting, you understand that there cannot exist something like a perfect brief, but in the end you contradict yourself by saying that you could anyway make kind of a perfect brief.
Which one is it?
I will give you my understatement:
Your company doesn't understand developers and I don't think you can attract developers as long as you sound like marketers who are talking between themselves about developers.
@jmfayard
You might be misunderstanding Elena's goal here (granted, I might be too!). I think the use of the term "perfect" is a literary device for attracting attention to the article, to give readers the idea that, "Okay, this article might help me do much better at X".
The overall goal seems to be to improve communication between the people coming up with technical work to be done, and the people doing the technical work.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
I get that she didn't make this to make me mad. And I'm not mad.
But I have the impression that she wants to connect with developers, and I wanted to warn her that right now she doesn't have the language and empathy to do so.
You're so right about needing to approach this with empathy and armed with the right language 💯
Engineers are often very pedantic, whether by nature or because of the nature of our work, and I know that for me attitude and word-choice have a big impact on how I respond to the information being presented to me.
It seems like in Elena's situation, the marketing team is preparing these project briefs, and I think it's safe to assume they have varying levels of technical background. How can we help them get better at presenting these briefs to us effectively?
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
I would be glad to tell it if it was possible.
But there is, in fact, no shortcut.
To develop empathy, they need to talk with and listen for a long time to real world developers.
Definitely agree there is no shortcut, I wasn't asking for one 👍 working together and imagining each other more complexly is the only way I know of to get better at approaching communication with empathy.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ok so even your title is wrong.
There is no such a thing that a "perfect" brief.
Trying to find the "perfect" anything causes a lot of stress, because there is not such a thing.
Simple hint: developers are really good at understanding other developers. Maybe search for developers who can write?
Hi, thanks for your answer! I do understand that there is no such thing as a perfect brief, but still, I believe there are problems and pain developers are ready to explain. And this can be used to make kind of a perfect brief ;)
So that's interesting, you understand that there cannot exist something like a perfect brief, but in the end you contradict yourself by saying that you could anyway make kind of a perfect brief.
Which one is it?
I will give you my understatement:
Your company doesn't understand developers and I don't think you can attract developers as long as you sound like marketers who are talking between themselves about developers.
Okay, I've heard you.
@jmfayard You might be misunderstanding Elena's goal here (granted, I might be too!). I think the use of the term "perfect" is a literary device for attracting attention to the article, to give readers the idea that, "Okay, this article might help me do much better at X".
The overall goal seems to be to improve communication between the people coming up with technical work to be done, and the people doing the technical work.
I get that she didn't make this to make me mad. And I'm not mad.
But I have the impression that she wants to connect with developers, and I wanted to warn her that right now she doesn't have the language and empathy to do so.
You're so right about needing to approach this with empathy and armed with the right language 💯
Engineers are often very pedantic, whether by nature or because of the nature of our work, and I know that for me attitude and word-choice have a big impact on how I respond to the information being presented to me.
It seems like in Elena's situation, the marketing team is preparing these project briefs, and I think it's safe to assume they have varying levels of technical background. How can we help them get better at presenting these briefs to us effectively?
I would be glad to tell it if it was possible.
But there is, in fact, no shortcut.
To develop empathy, they need to talk with and listen for a long time to real world developers.
Definitely agree there is no shortcut, I wasn't asking for one 👍 working together and imagining each other more complexly is the only way I know of to get better at approaching communication with empathy.