> This week marks the beginning of my 4th year at Facebook. My > experience here has been incredibly transformative: I joined > Facebook after dropping out of college having never faced the > challenges that I've seen during my time here. At this point, I've > worked through these challenges for longer than 4/5 of the people at > the company and thought I would share some of my insights in hopes > that other engineer…
[Continuing because of HN's length restrictions] > In the code base that you live in, you quickly develop an > understanding of how the components fit together. Use this > knowledge: instead of only fixing a bug you're assigned, consider > how you can prevent that class of bug from ever happening > again. Instead of implementing a new feature, consider how you can > create a common abstraction between the new and old…
That's interesting, because you often hear that "code wins arguments" at FB.
>> This might take more effort now but gives vastly greater results in the long run.
I'm also surprised by this. There seems to be a lot of importance placed on moving fast. Some of FB's mantras are "DONE IS BETTER THAN PERFECT", "MOVE FAST AND BREAK THINGS", and "STAY FOCUSED AND KEEP SHIPPING".
> * Actually, I am glad to say that I am now happily employed.
Your first comment starting by saying you were unemployed. Did someone just hire you since your comment?