site banner
PaperclipPerfector  13d ago (text post)   1495 thread views

Wellness Wednesday for April 16, 2025

The Wednesday Wellness threads are meant to encourage users to ask for and provide advice and motivation to improve their lives. It isn't intended as a 'containment thread' and any content which could go here could instead be posted in its own thread. You could post:

  • Requests for advice and / or encouragement. On basically any topic and for any scale of problem.

  • Updates to let us know how you are doing. This provides valuable feedback on past advice / encouragement and will hopefully make people feel a little more motivated to follow through. If you want to be reminded to post your update, see the post titled 'update reminders', below.

  • Advice. This can be in response to a request for advice or just something that you think could be generally useful for many people here.

  • Encouragement. Probably best directed at specific users, but if you feel like just encouraging people in general I don't think anyone is going to object. I don't think I really need to say this, but just to be clear; encouragement should have a generally positive tone and not shame people (if people feel that shame might be an effective tool for motivating people, please discuss this so we can form a group consensus on how to use it rather than just trying it).

2
Top Bottom Old Controversial Comments
Jump in the discussion.

No email address required.

We finally fired the guy. (I'm a SWE at FAANG.) I'm so relieved. You would not believe how much time and documentation it took. I'll estimate 20 pages of explaining his mistakes, not counting the code itself, over the course of six months. I have no idea how much time and energy our manager had to put into it - probably more than me. After 3.5 years, he was at what I consider 1-1.5 years of skill. How the hell he got promoted, I do not know.

I got asked to be his lead (kill me), which is good for my shot at promo to senior (results tomorrow!), so obviously I said yes. I immediately start complaining. Our manager doesn't see the problem. After a couple months of casual complaining (read: spending ~half my highly-valued weekly 1:1 sharing examples), I put together a meticulous spreadsheet. He sees the problem and says Junior needs to rapidly improve or will be fired. Junior makes no progress. Junior insists he is making great progress. Four months later, Junior is offered a severance or PIP and, in his first display of real intelligence, takes it.

Two of my favorite mistakes:

  1. He asserted that my code review idea to use an interface was conceptually impossible because when he tried it, the compiler said "attempting to assign weaker access privileges; was public," which apparently he found inscrutable. Solution: change the impl to also be public.
  2. On a project whose entire point was "set a timestamp, then filter stuff out if it's before that time," he set the timestamp wrong. It was set to the epoch. He had no tests that caught this. After this was pointed out, he pushed a new commit that was also wrong (differently). Twice. After four months on this project, he almost finished - the smaller half of it, which should have taken 2-3 weeks.

I have complained about this ongoingly to everyone I know for months. It was getting to be a problem. Work is so much chiller now. I can literally see the day he got fired in my sleep tracking metrics, as everything discontinuously improved.

What drove me the craziest was that my manager, reasonably, was too discrete to be straight with me about his agreement. I'm not sure at what point I really won him over. This left me chronically feeling unsure if, in the eyes of He Who Writes My Reviews, I was nitpicky and disagreeable, shitting on a coworker who he thought was just fine. Thankfully, the ending of the story strongly suggests he didn't think that, but it's still unclear if it hurt my reputation.

Or helped it - I did just save the company over 1 SWE-yr/yr, in perpetuity.

This isn’t particularly related to your post, but I’m curious about what it takes to get past that initial screen to be considered at FAANG.

Long story short: I have a PhD in (pure) math and am finishing up a postdoc, but I’m just done with academia for a number of reasons and wanting to transition to industry. Other than a brief 1 year stint at a small company before starting grad school, almost all my coding experience is in an academic context.

I’m fairly confident I would demolish most Leetcode-style DSA interview questions and can learn new skills pretty fast, but it’s hard to get my foot in the door because I don’t have any shipped products or industry connections. I’d really appreciate any guidance or advice!

I don't think we're really hiring, so hard to say. In practice, the answer is, as it is for everyone at all times, grind leetcode and spam recruiters/your network.

With a PhD, you'd come in at typically mid level (new grad + 1, aka senior - 1). Expectation there is just leetcode, no system design. If you can comfortably do mediums, and communicate well while doing it, that's likely good enough. You might catch a hard now and then, but we'd really rather see if people can write clean code for a medium and communicate well (tradeoffs in algorithms or naming, working through examples, etc)

Thanks for that, I really appreciate it. I’ve been grinding leetcode and feel very confident, if only I could manage to get my foot in the door. I’ve just haven’t had any luck getting interviews in the first place. I’ll try spamming more recruiters, but as for networking, I don’t think I know anyone working in FAANG at the moment.

I'd expand from just faang. Get your foot in the door by looking at every generic startup. If you don't already live in the bay (SF), consider moving.

What is this place?

This website is a place for people who want to move past shady thinking and test their ideas in a court of people who don't all share the same biases. Our goal is to optimize for light, not heat; this is a group effort, and all commentators are asked to do their part.

The weekly Culture War threads host the most controversial topics and are the most visible aspect of The Motte. However, many other topics are appropriate here. We encourage people to post anything related to science, politics, or philosophy; if in doubt, post!

Check out The Vault for an archive of old quality posts. You are encouraged to crosspost these elsewhere.


Why are you called The Motte?

A motte is a stone keep on a raised earthwork common in early medieval fortifications. More pertinently, it's an element in a rhetorical move called a "Motte-and-Bailey", originally identified by philosopher Nicholas Shackel. It describes the tendency in discourse for people to move from a controversial but high value claim to a defensible but less exciting one upon any resistance to the former. He likens this to the medieval fortification, where a desirable land (the bailey) is abandoned when in danger for the more easily defended motte. In Shackel's words, "The Motte represents the defensible but undesired propositions to which one retreats when hard pressed."

On The Motte, always attempt to remain inside your defensible territory, even if you are not being pressed.


New post guidelines

If you're posting something that isn't related to the culture war, we encourage you to post a thread for it. A submission statement is highly appreciated, but isn't necessary for text posts or links to largely-text posts such as blogs or news articles; if we're unsure of the value of your post, we might remove it until you add a submission statement. A submission statement is required for non-text sources (videos, podcasts, images).

Culture war posts go in the culture war thread; all links must either include a submission statement or significant commentary. Bare links without those will be removed.

If in doubt, please post it!


Rules


Recommended Posts And Communities

Recommended Realtime Chats