Exactly. If they just lay people off, that's just cost cutting, and potentially seen as a bad sign. If they're saying they're laying people off because they're replacing them with AI, then they're innovative!
Kitemaker (YC W21) | Fullstack engineer | Remote | Full-time
Kitemaker just recently completed the W21 batch at YC and now it's time to start growing our team. We're looking for founding members who can not only help us shape our product, but also shape the company itself.
We're building everything in TypeScript top-to-bottom (Node, React), our API uses GraphQL and we're working on a bunch of fun integrations (GitHub, GitLab, Slack, etc.).
Fully remote but should have some workday overlap with GMT+1 timezone.
IANAL but I would assume FB is in the clear legally though as they're not actively blocking anything in particular, merely providing the tool with which admins can do the blocking themselves.
I disagree on #1. There's no need to be a martyr as a tech lead. Assign the tasks based on who is the best person to get it done (based on competency, knowledge of affected components, etc.). Treat your employees like adults. They don't need to be coddled, they know there are unpleasant tasks sometimes. Just try to be fair and ensure that your employees are not getting too such tasks to the point where they feel bogged down. Ask them "are you bored?" whenever you have a 1-on-1 meeting.
I've found this to be the single greatest challenge I have as a tech lead. It's incredibly tempting to say "oh, I think I'll have time this week, so I can take that Trello card". If it's on the critical path, leave it for someone else. You won't have time.
> you need to be the one that monitors and accepts all pull requests
I disagree at least in part. On my team all of the engineers have the ability (and responsibility) to merge PRs. It empowers them and gives them a feeling of ownership. I let the experts in the affected area decide when code goes in/gets deployed as they're able to manage that better than I ever could.
That being said, when something breaks, it's still the tech lead's problem, even if he/she didn't hit the merge button.
I'll leave now...