It's all very solid advice, but there seems to be a tacit assumption that the engineer is working for a reasonable employer in a time of economic stability. Meta is or at least was that 10-15 years ago, but these lessons need moderating if, say, you are a dev at a 1000 person software company in Kansas City.
The cold reality is that you are one Zoom call away from losing your livelihood, and maybe also your healthcare, your immigration status, and your employer is, even now, aggressively looking for ways to cut labor costs, which make up a huge chunk of their inputs. So strategies like the one OP lays out are not wrong, but they are much harder to implement when you get laid off every few years or work under that continual threat along with your coworkers.
This seems fairly generic linkedin-post type of writing - humblebrag with few specifics. It is rare to see the human come through these days. There are no examples, no stories to be memorable. It might as well have been written by someone in government, or a consulting firm, or an LLM. Complete with repeating a summary of the bullet points in the end.
I still don’t know what Facebook engineering even is. I see a web site. There’s surely some backend work but it seems like you could add a few more servers to pass text around.
You do not just sort by date time, nope, this is a highly complex technical process of sorting posts in a semi-random order that creates just enough frustration by the user to keep clicking and scrolling around to find stuff.
The advantage is that all of that navigating provides a fractal landscape of opportunities to push more ads.
She worked for 10 years and then quit to write a book to help other engineers grow? That sounds weird at best. I think I'll go on a 20-mile run to think about that.
Oh. Wait. I don't do that. And have never known anyone who does.
It's all very solid advice, but there seems to be a tacit assumption that the engineer is working for a reasonable employer in a time of economic stability. Meta is or at least was that 10-15 years ago, but these lessons need moderating if, say, you are a dev at a 1000 person software company in Kansas City.
The cold reality is that you are one Zoom call away from losing your livelihood, and maybe also your healthcare, your immigration status, and your employer is, even now, aggressively looking for ways to cut labor costs, which make up a huge chunk of their inputs. So strategies like the one OP lays out are not wrong, but they are much harder to implement when you get laid off every few years or work under that continual threat along with your coworkers.
I am glad some people like working in that type of environment. It is necessary, I guess.
But even reading this makes me itch. I suppose I am just not suitable for working with ambitious people.
There's a difference between ambition and 惊输, and it's not a small one.
"The fear of losing"?
I think this post is well-meaning, but joining a company at the start of hyper-growth feels as much "right place, right time" as anything else.
Big tech wants to look special but you can apply a lot of the advice to any part of corporate America by making small changes.
This seems fairly generic linkedin-post type of writing - humblebrag with few specifics. It is rare to see the human come through these days. There are no examples, no stories to be memorable. It might as well have been written by someone in government, or a consulting firm, or an LLM. Complete with repeating a summary of the bullet points in the end.
If you look at the author's background, you're not far off: after Stripe, she went into policy/politics, government and investing/VC.
I still don’t know what Facebook engineering even is. I see a web site. There’s surely some backend work but it seems like you could add a few more servers to pass text around.
Well, you have to sort the posts.
You do not just sort by date time, nope, this is a highly complex technical process of sorting posts in a semi-random order that creates just enough frustration by the user to keep clicking and scrolling around to find stuff.
The advantage is that all of that navigating provides a fractal landscape of opportunities to push more ads.
She worked for 10 years and then quit to write a book to help other engineers grow? That sounds weird at best. I think I'll go on a 20-mile run to think about that.
Oh. Wait. I don't do that. And have never known anyone who does.
No doubt she’s talented but I wonder how much of this is an effect of working at a rocket ship?
Think about it this way, would her trajectory repeat if she started off again right now?
these environments are toxic and teach you nothing about building in the real world