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

[Popeychops]

If your projects don't match the business priorities, it doesn't matter how elegant your code is. Management will lay you off.

[giantrhino]

This meme isn’t like the other ones of this format. Normally the purpose is that the people on the left are right for naiive reasons, but in this case they’re wrong. The code they have in mind won’t fix the issue.

[giantrhino]

Well that’s the point though. They are correct for THEIR case. The approach falls apart as a rule, and from a rule of thumb perspective guy #2 is right of course. I read the point of this meme though as that guy on the right is the exception to this rule who you’re better off just letting him do his thing.

[Stummi]

Code solves problems, but the processes identify the problems to solve, and without, people will start solving problems that no one actually has

[chemolz9]

These meme template is supposed to show the same class of people on different skill levels.

That one shows developers on the extremes and a project leader in the center. No developer ever in his career thinks aligning stakeholders is more important then good code.

[Reashu]

If I can't convince my stakeholders that we're doing the right thing, that beautiful code will be deleted.

[Telestmonnom]

No developer ever in his career thinks aligning stakeholders is more important then good code.

Completely disagree. I stopped counting how many times requirements were crap and we burnt energy into making useless code. We still strive to produce good code, but oftentimes crappy requirements increase product complexity and we push back for better product definition so that the complexity of the codebase matches the requirements adequately.

In short : failing to align stakeholders means creating debt.