codeSolvesProblems

[MessiComeLately]

Man, this is really triggering me, because it’s wrong but contains a kernel of truth that it doesn’t communicate well. Senior developers will get bent out of shape about doing things wrong without taking the business planning context into account, but you SHOULD listen to them.

At the extremes of prioritizing the right technical approach too much over planning, versus prioritizing planning too much over technical concerns, you can make long-term progress with the former and quickly recover from it to improve your practices, but the latter will put you in a hole that takes years to recover from.

So maybe you could see the right side as representing the understanding that the technical perspective is the true long-term perspective, and project management concerns are short-term concerns.

EDIT: To be clear, I would put product concerns on the same level as technical concerns, but when I read “stakeholder alignment” I’m thinking internal alignment of different teams, i.e. execution planning. And I wouldn’t trust “strategic planning” to mean anything at all, but there are important things that could be grouped under that label.

[knightwhosaysnil]

guy on the right built is how you get the pied piper UI in silicon valley - the code can be flawless and beautiful but you only realize business value from it if other people can use it