5 ms·
> Being aligned with teammates on what you're building is more important than building the right thing. So, let's cave in to peer pressure or management dictat
by einpoklum 7y ago
> Being aligned with teammates on what you're building is more important than building the right thing.
So, let's cave in to peer pressure or management dictates and continue down the wrong path (technically/socially)?
Strongly disagree with that.
> Peak productivity for most software engineers happens closer to 2 hours a day of work than 8 hours.
Here I mostly agree. The thing is, that you don't know in advance when these hours are going to happen. Also, sometimes it's 2, sometimes 0 and sometimes 8.
> The amount of sleep that you get has a larger impact on your effectiveness than the programming language you use.
(Yawn) Indeed...
- _petronius 7y ago> So, let's cave in to peer pressure or management dictates and continue down the wrong path (technically/socially)? Seems like a very unfair restatement of what the author said. I would read that as "it's more important that everyone has a common understanding of what you are building than it is to spend time worrying about whether you have the exactly perfect goal." Or to phrase it another way: if the understanding of the product isn't clear across the whole team, it doesn't matter if any one individual has a bunch of brilliant ideas for/about the product, because you aren't all working towards the same goal.
- smitty1e 7y agoI'd offer that the "alignment" is substantially a function of the management/leadership on display.
- _petronius 7y agoSure, but hopefully the choice isn't a binary one between "lack of alignment" versus "management/leadership dictates", since that would be evidence of a rather toxic team culture.
- gwd 7y ago> I would read that as "it's more important that everyone has a common understanding of what you are building than it is to spend time worrying about whether you have the exactly perfect goal." The fact is, that unless you have a functioning crystal ball, you don't actually know what the perfect goal is; you only have hazy guesses at best. At some point, extra time spent looking for the perfect goal is wasted, because one hazy guess is no better than the next. It's much better to get something that is well-structured and functioning out the door. If you've done your due diligence, it has as much chance of succeeding (or failing) as the next thing. And to get something well-structured and functional out the door, you need everyone to be working towards the same goal, even if they don't all necessarily agree that that's the perfect goal. There's an argument that this is how ancient divination worked in practice. You don't know whether you should attack from the north, attack from the south, or hunker down and build defenses. You definitely can't do all three. It's much better to pick one and do it boldly than to dither around in indecision. Divination gets everyone fully behind one option; that option may not be the optimal one, but it's certainly better than "do nothing". Which makes me wonder if maybe modern product management would be better with some oracle bones...
- ojilles 7y agoIt's also a reflection (or assertion?) that software development largely is a team sport, not an individual one.
- dadarepublic 7y agoThis is pretty much how I grokked the point. Having a common vision is critical in team building and in actually building the right/correct/good thing.
- AnthonBerg 7y ago> So, let's cave in to peer pressure or management dictates and continue down the wrong path (technically/socially)? That's misalignment :)
- pfarrell 7y ago> So, let's cave in to peer pressure or management dictates and continue down the wrong path (technically/socially)? That's not alignment. For alignment to happen, everybody should be on the same page. And any party can tank this if they refuse to negotiate. I read this as getting alignment between all parties is something that leads to successful projects and therefore is something that should require attention and effort to make happen. I've ruminated on Jeff Bezos/Amazon's "Disagree and commit" leadership philosophy a bit and think it pertains here. Leaders are obligated to respectfully challenge decisions when they disagree, even when doing so is uncomfortable or exhausting. Leaders have conviction and are tenacious. They do not compromise for the sake of social cohesion. Once a decision is determined, they commit wholly. [0] Where I think "leaders" is a quality of a person's actions, not a job title. [0]: https://www.amazon.jobs/en/principles https://www.amazon.jobs/en/principles
- pc86 7y agoJust make sure you're negotiating the thing you're supposed to negotiate. I've been in meetings where junior or mid-level developers with minimal experience are arguing the merits of the business model with executives. I'm all for asking thoughtful questions but if you have 2 years of experience at a different company in a different industry, saying you don't think Product X is going to make money doesn't really qualify. Likewise, I wish "business folks"/product owners/whatever you want to call them would give a little more leeway on technical decisions to their technical team. We shouldn't be discussing choice of database tech or service architecture with a VP Finance.
- knightofmars 7y ago> I've been in meetings where junior or mid-level developers with minimal experience are arguing the merits of the business model with executives Oof. I'm a big supporter of questions not statements in these situations. I've witnessed people with this behavior, where a person makes claims and argues a point but doesn't have a clear understanding of the situation. They don't realize they're ignorant to a certain portion of information which they need to ask questions to learn about. This happens both with those with minimal experience as well as leadership. Though in the latter case I suspect it is not wanting to be perceived as not having grasp of a situation or being perceived as lacking in knowledge. Which is sad, as people who ask smart questions generally are the best leaders.
- crimsonalucard 7y ago>So, let's cave in to peer pressure or management dictates and continue down the wrong path (technically/socially)? He didn't say cave in. Your first step in the above scenarios is to get buy in and alignment with management and peers. If you cave in then you aren't in alignment. He is saying the latter event is worse.