Skip to content

Instantly share code, notes, and snippets.

@choyan
Created April 18, 2022 21:37
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save choyan/29d537b11d0662b4036f5305b75ae7e9 to your computer and use it in GitHub Desktop.
Save choyan/29d537b11d0662b4036f5305b75ae7e9 to your computer and use it in GitHub Desktop.

[00:10:28]

What do you think separates a good react engineer from a great react engineer? It's a good question. What separates a good react engineer from a great react engineer? I don't know if I can think of anything that's gonna be particularly tailored to react. In general, the best engineers that I've worked with communicate super well.

[00:10:55] And when I say that they, like let's say, I come into your office and I say, hey, I need you to build this new search functionality that allows users to checkout faster or something like that, right? A good engineer is going to ask a lot of follow up questions so that they can get the product requirements down to like, okay, we need to build this and this and this and so they understand the problem domain really, really well before they start working on something.

[00:11:23] That has been historically that the engineers I've seen that perform the best at can take something that's really ambiguous and distill it down to step by step steps that they can then go out and build, right? It's a really junior engineer kind of move to go in and just say, okay, I'll build it.

[00:11:42] And then they just go build something and it's not what was actually meant to be built. So those kinds of like human interaction personal skills like, that's what makes the best engineers. I'll say that when I worked at Netflix which is probably the hardest front end work that I ever had to do, it was the most advanced, was the most performance sensitive.

[00:12:04] 95% of my job there could have been done by literally any junior engineer anywhere, right? It was just mostly marshaling JavaScript and CSS around, which most of us can do fairly well, right? It was that last 5% that was really difficult. Scaling problems or problems that you run into that you can't just Google and say, how do I do x, right?

[00:12:23] And that was what the senior part of my senior engineering title kind of came in is like, okay, I've seen this before at Reddit, this happened we did these things. This didn't work and this didn't happen. So that experience helps a lot as well. Trying to think if there's anything else that I would really say that sets apart a great engineer.

[00:12:46] It really comes down to communication and experience are really the two things that are gonna set people apart as they move forward in their career. The most effective engineers like know how to work well with others and like be a force multiplier for their entire team. Like we've heard of the mythical 10x engineer helps other people be twice as productive, right?

[00:13:07] If they can do that for five people then they are a 10x engineer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment