4 ms·

Also interested in hearing people's thoughts on this, as a "demand side" guy who asks programmers to do stuff. My advice, FWIW, is that talking to and really t

Also interested in hearing people's thoughts on this, as a "demand side" guy who asks programmers to do stuff. My advice, FWIW, is that talking to and really trying to understand the problems faced by the engineers/developers working for you goes a VERY long way. Typically, they just want to know that someone is aware of their issues and is working with them, not against them. Not a unique problem though - that's how all management needs to function. Although the technical barriers in programming can be daunting (as I think the OP notes).

icey 17y ago
You'll get significantly better returns on both your time and your money if you approach a developer with a conversation instead of directions. In other words, ask questions while you're trying to figure out the best way to do things. The nice thing about most developers is that they have experience in a lot of different problem domains, and they may have solutions available that you hadn't previously considered.