This is so anecdotal but I remember taking a Lyft from Noe Valley to Taraval earlier this year and the ride went through (I'm zooming into Google Maps for the neighbourhood names) Miraloma and surrounding areas. Basically the neighbourhoods just north of Monterey Blvd. The area just looked and felt really nice, homey, and safe.
I've haven't driven past that area before nor after, but it really made me feel like long-term it would be a nice place to reside in SF away from the classic SF problems you've described.
There are two types of "bad" neighborhoods you don't want to live in: the ones where crime lives and the ones crime visits. Much of San Francisco falls victim to the latter which isn't always obvious on an Uber ride or casual walk.
These neighborhoods feel "dreamy" but living there is a different reality. You have to trek down a hill to buy things and when you do, you get the full SF doom loop experience. Most people pay a small fortune to DoorDash and Uber to avoid leaving their dreamy neighborhoods.
No, NW border of Excelsior is 280, so definitely not north of Monterrey Blvd. Broad strokes neighborhood is Twin Peaks area. That part of Twin Peaks is heavily influenced by historically affluent planned developments. Some of the more well known ones listed here https://en.wikipedia.org/wiki/San_Francisco_Residence_Parks.
His internal badge (ie. goodbye) post. This is definitely not in the article.
Edit: The article has a link to some other paywalled link that may contain the full contents of the note. I don't have a subscription so I can't tell but the quote is real at least.
Hm, the number of teams that work on these distributed systems is smaller than I think you believe exists at Meta, though I suppose it depends on the type of system being built. Even the internal post on this topic links to a note from last year that talks about the 3 teams in the core systems area that needs to work directly with PTP.
The vast majority of people will probably end up working on product-related team compared to infrastructure-related teams.
I like the product/infra distinction quite a bit more than frontend/backend. This is basically how Facebook describes its engineers - product engineers who typically work in the "product" repo and works on UI as well as API design and data fetching, vs infrastructure engineers who work in the "service" repo and work on what you typically think of infrastructure (data, systems, efficiency, etc).
After being here for a while and speaking with recruiters from other companies, I've really grown to dislike describing myself as "backend" since I have to make myself explicitly clear that I do not want to work on "backend" portion of product and enjoy myself in the infrastructure side of the world.
I'll give my perspective which I think is very different than the rest of the HN crowd here in the comments. I think this mainly stems from the fact that I'm probably much younger than a lot of the folks here. I do a lot of random shopping online...
I opted into the FB tracking when I got the popup yesterday because I do FB/IG a lot and I click on interesting ads. Honestly, I tend to buy quite a bit from the ads that I see because they genuinely interest me, and a lot of them are from smaller businesses that I want to try out. If I see ads on FB/IG, at least I want them to be relevant to me rather than be generic.
Just throwing some info out there since I graduated from this exact program. We may graduate with an engineering degree, but we technically cannot use the word engineer in our title (in Canada) until we get our accreditations, which require a couple years working in Canada under a somebody else with their P.Eng license.
The vast majority of us (definitely > 90% of my class) have moved to the US after graduation where we pretty much can use whatever role we want (eg. my official title is software engineer at my company), but from what I know of the few people left in Canada, their roles are officially "programmer" or "developer". I've actually heard stories of P.Engs on messaging people in my program on LinkedIn to change their job titles to not include the word engineer. I'm not really sure what the repercussions are.
> we technically cannot use the word engineer in our title
Just for completeness: it’s OK to use the title “B. Eng.”, which means you have a Bachelor’s in engineering, without implying anything about being a professional engineer.
Question for you then: Can you work under someone who's a P.Eng mechanical or civil engineer, and then get your own P.Eng license that way (as a software engineer)?
IIRC there's no limitations on who you work under provided they are licensed; P.Eng license is a not tied to any specific discipline. If I complete my engineer-in-training (4 years professional industry experience under the supervision of one (or more P.Engs)) and pass the exam component, then I will also be licensed as a P.Eng. I may choose to work as a software engineer, or any other role, but being a P.Eng means that I uphold the standards, ethics, and discipline of the engineer title.
I did a lot of travelling in Europe earlier in the year, and had McDonald's in a lot of different cities in different countries. What really helped were the automatic digital kiosks that you can just order from (without talking to a cashier). They had the official languages of the country, plus always English as an option so you'd always be able to use the machine. You get assigned a number and then just wait for your number to pop up - no conversation at all except a little thank you when you pick up your food.
I'm also really interested in renting an RV and just driving across the US. Seems like a relaxed way to travel.
I've haven't driven past that area before nor after, but it really made me feel like long-term it would be a nice place to reside in SF away from the classic SF problems you've described.