4 ms·
> They write better code. They build the right stuff. They promote better team cohesion. And they execute on difficult projects more effective. Let's put it th
by zamalek 11y ago
> They write better code. They build the right stuff. They promote better team cohesion. And they execute on difficult projects more effective.
Let's put it this way: 10X engineers ship 10X better products. Some places still use the daft metrics you mentioned (LOC, bugs squashed, etc.), sure. I'd assume that a gig such as Twitter would know that a 10x engineer is identified by, essentially, gut feel and can't be quantified. There seems to be two definitions of the meme and I'd assume that most people around here would refer to the more realistic one (10X better products).
More facts of the 10X meme: not every engineer is necessarily 10X on every project you might assign them and, as you mentioned, a 1X hire could end up being a 10X engineer some day.
Back to the article. An EE team isn't the only way to approach this. We've got at least two where I work:
With enough 10Xs around sometimes you just need to let them fly: give them a little freedom to fix shit, take their fixes seriously and trust them. There's a good chance that if something annoys an engineer enough, they will take their own initiative and fix the shit (sometimes in their own time). This is the approach that my team lead takes - he'll give us the time once we can prove the value of our changes.
Another team lead I chat to a lot logs tech debt the very instant that it is created and allocates time every release to remove tech debt. His tech debt backlog is rapidly approaching zero. The advantage here is that his junior engineers learn the cost of tech debt and learn how to make the correct decisions to fix it as they are involved with removing it. An EE team with 10X elites provides no knowledge sharing.
An EE team might not work everywhere (especially for us: our product could be seen as a collection of products), the most important take-away from that article is that tech debt can be solved with a little responsibility and by granting your employees enough autonomy to figure out how to solve it.