Elliott-McCrea: Software problem timelines range from days to years based on clarity
Kellan Elliott-McCrea · How to supercharge your engineering org | Kellan Elliott-McCrea (Adobe, Dropbox) · Aug 17, 2023 · at 20:25
Former Etsy CTO Kellan Elliott-McCrea explains why software engineering timelines vary dramatically.
0:00 / 0:13exact quote · 13.1s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“One of the things that's really different about software engineering than other types of engineering is the fungibility. Problems can take two days or they can take two years. And the fundamental difference is the excitement and clarity you have around the solution.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →
More from Kellan Elliott-McCrea
Elliott-McCrea: Slow engineering execution always stems from leadership's lack of clarity
“When I'm going and having these conversations with leaders, and this is, I think the standard conversation most people have is it starts with leadership. If we're moving too slow, it always does. We've always believed that we've been more clear. We've created …”
Elliott-McCrea: Dropbox's runaway early success created a flawed product development mindset
“Dropbox hit a home run basically out of the gate. And there was kind of an expectation that that's how you built products. And like people came from different places and very different experiences, but pretty deep in the culture was this idea that you build it…”
Elliott-McCrea: Google hires often struggle elsewhere because its internal systems don't replicate
“I think the canonical example of this is Google, by the way. I mean, I think that
Sort of in industry. Now we've kind of learned you hire people out of Google and they show up and they don't know how to operate because they've been such a determined high funct…”
Elliott-McCrea: Leaders should not automatically bring former colleagues into new organizations
“One of the things that people ask me is you look like you've worked with a bunch of great people. Like, do you just like bring them with you to every organization? And the answer is, of course not. Like every organization is different and partially I need the …”
Elliott-McCrea: Shielding engineering teams from company chaos causes them to misalign
“Actually, one of the early stereotypes about engineering managers in our industry is as the shit umbrella, you know, just gonna keep people from being distracted by all the crazy. And what that is, is those teams end up just drifting off. You know, you talk ab…”
Elliott-McCrea: Management quality matters more for scaling than code reviews or architecture
“You know, I really have come to believe that high quality management is one of the keys if you're going to scale your organizations. And so the degree to which I invest in that versus invest in architectural principles or code reviews or other things has grown…”