[usrbinbash]

>The solution is not one that may involve code or even engineering in general, but rather, a clear understanding of the problem, its constraints

Problem is: The only way to really understand a problem in engineering, is trying to engineer a solution for it.

[justjico]

Agreed. But the problem itself may not really be an engineering problem, and therefore a potential solution may exist outside.

I agree though, particularly in tech, the tendency is for great leaders to be deeply knowledgeable on engineering details because that is a requirement for a good strategy.

Nonetheless, in a broader sense, defining success for a business can create a solution space that extends well beyond engineering.

[usrbinbash]

If it is not an engineering problem, then engineers should not be bothered with it, simple as that. Not because we cannot do it, but because we can do things others cannot. And these things take time and focus to do well. And without them, all the talking and planning and strategizing and wearing suits, becomes pointless, because there is no product to sell.

I am a coder. It is not my responsibility to sell our product, convince someone to see a demo, or do "market research" into what features we require.

"division of labour" exists for a reason. If I am supposed to be doing the job of the guys in suits&ties, in addition to be able to write, read and test code, then I have to ask the question why we should pay these guys in the first place.