"The product side needs to provide a set of requirements, and the development side needs to find out what the client needs, and how to deliver it. The development side has to have enough product knowledge to determine the actual need, not the stated want" disagree with that statement. "The product side needs to find out what the client really needs and build requirements out of it. The development side has to determi…
See? Now you're going back to "engineer is a dumb machine who translates other peoples' thoughts into code" land. Reality is more like this: "The sales side figures out what customers claim they can't live without. The product side figures out how to turn those perceived needs into a product. Development figures out how to make it meet with reality."
“Developers Don't Need to Know the Product”
21–27 of 27 posts
Re: “Developers Don't Need to Know the Product”
#22Earlier quoted context omitted.
I have been fortunate to be surrounded by people who are generally intelligent and progressive that believe engineers should be part of the entire lifecycle. Would you care to share your experience with us?
It's rarely that blatant. Most people use more covert methods to keep engineers out of the lifecycle. It can be frustrating because most of these statements can be valid when uttered under different circumstances. - "Only " power users " will use that." Sometimes this one's true, but some people will say this about any idea engineers come up with. - "Let's see what someone in product thinks." The key thing you have t…
I personally think it is ASININE not to involve my engineers in the decision process, bc they might be able to optimize my business process, or even my thoughts as a product owner. I am a sales and marketing guy, that desperately wants to become a good product manager. The only way I can do that is by learning from others' approaches. If you'd like to continue the dialogue feel free to email me at ben@projectsherpa.com
Cheers,
Ben CoFounder ProjectSherpa ben@projectsherpa.com
Re: “Developers Don't Need to Know the Product”
#23I've had a similar experience in financial services but from the other direction, and particularly as an architect. I can't tell you how many times I have heard the phrase "I'm a banker, I don't need to understand the technology" from people in very senior positions with very high salaries. The thing that they fail to understand - apart from routinely missing fundamental banking concepts like "on behalf of" or "produ…
Everything is based on stored bits. It's how those bits are interpreted that matters. No banker should care that they store bits instead of physical cash. It simply doesn't matter. I've only ever seen inept programmers think that everyone should know the underlying technology, which I guess you could say is hypocritical, as I doubt many of them truly understand what's happening in the lower levels of programming, phy…
Re: “Developers Don't Need to Know the Product”
#24I've had a similar experience in financial services but from the other direction, and particularly as an architect. I can't tell you how many times I have heard the phrase "I'm a banker, I don't need to understand the technology" from people in very senior positions with very high salaries. The thing that they fail to understand - apart from routinely missing fundamental banking concepts like "on behalf of" or "produ…
Re: “Developers Don't Need to Know the Product”
#25I've had a similar experience in financial services but from the other direction, and particularly as an architect. I can't tell you how many times I have heard the phrase "I'm a banker, I don't need to understand the technology" from people in very senior positions with very high salaries. The thing that they fail to understand - apart from routinely missing fundamental banking concepts like "on behalf of" or "produ…
You have to consider their goals, which define their needs. If they are in very senior positions and have very high salaries already, and don't understand the technology, then it's fairly obvious that they do not need to understand the technology. They got everything they wanted without that ever being a requirement. Of course, it's better for everybody else if they do. We need them to understand the technology. They…
Re: “Developers Don't Need to Know the Product”
#26Earlier quoted context omitted.
Everything is based on stored bits. It's how those bits are interpreted that matters. No banker should care that they store bits instead of physical cash. It simply doesn't matter. I've only ever seen inept programmers think that everyone should know the underlying technology, which I guess you could say is hypocritical, as I doubt many of them truly understand what's happening in the lower levels of programming, phy…
That is all going to change as the world becomes more data driven. As a sales person, relationships are important, but still without a deep understanding of my data, I would be incredibly inefficient. Talk like that also sounds like what the Equities traders were saying up until 2007 or 2008. I don't need to know tech, I don't need to know algos, until they were replaced by trading tech and those same guys who were m…
Re: “Developers Don't Need to Know the Product”
#27Earlier quoted context omitted.
That is all going to change as the world becomes more data driven. As a sales person, relationships are important, but still without a deep understanding of my data, I would be incredibly inefficient. Talk like that also sounds like what the Equities traders were saying up until 2007 or 2008. I don't need to know tech, I don't need to know algos, until they were replaced by trading tech and those same guys who were m…
If you could throw in some extra buzzwords and drop a few more names, it might be helpful in convincing me you're not an idiot.