Maximize Your Productivity As A Software Engineer [Part 18] - Procrastination

We all learn how to procrastinate in school - It feels good to wait until the last minute to get something done as this means you got to use all that initial time to have fun! This lesson teaches you:

- Why people procrastinate
- The main tactic to apply to avoid procrastination
- What to do if you simply can't stop procrastinating

How To Be An Effective Tech Lead [Part 17] - Go Deeper: Follow Through

Congratulations on making it to the final lesson of the course! This lesson teaches you:

- The key takeaways of being an effective tech lead
- Technical items you can take on to start being a better tech lead
- Leadership items you can take on to start being a better tech lead

For further support, start career discussions in the Taro forum to get top-tier advice: <https://www.jointaro.com/questions/create/>

You can also go deeper with our related courses:

- [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)
- [\[Course\] System Design Masterclass: Shipping Real Features To Production](https://www.jointaro.com/course/frontend-system-design-masterclass-building-playlists/)
- [\[Course\] Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)
- [\[Course\] Nail Your Promotion As A Software Engineer](https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/)

Paper Reading: Beyond Next-Token Prediction: Enhancing Language Models with Multi-Token Outputs

Session led by: [Lucia Mocz](https://www.linkedin.com/in/lucia-mocz-ph-d-35a98a1b6/)

In this talk, we will look at groundbreaking research on advancing the training of large language models. Traditional models like GPT and Llama rely on next-token prediction, which can be expensive and time-consuming, but this research suggests a more efficient approach: multi-token prediction.

**Key Highlights:**

- **Enhanced Sample Efficiency**: Training models to predict multiple future tokens at once increases sample efficiency, leading to significant improvements in downstream capabilities.
- **Innovative Architecture**: By employing n independent output heads on a shared model trunk, better performance with no additional training time can be achieved.
- **Superior Performance**: 13B parameter models outperform strong baselines on generative benchmarks, solving 12% more problems on HumanEval and 17% more on MBPP.
- **Algorithmic Reasoning**: Multi-token prediction fosters the development of induction heads and enhances algorithmic reasoning capabilities.
- **Faster Inference**: Models trained with 4-token prediction are up to 3 times faster during inference, even with large batch sizes.

Join us to explore how multi-token prediction can revolutionize language model training and performance, especially for coding and natural language tasks.

Don't miss this opportunity to learn about the future of language model training and its practical applications!\
\
Paper: [**https://arxiv.org/pdf/2404.19737**](https://arxiv.org/pdf/2404.19737)

Maximizing a Severance Package 7/9 - Common Asks and Gives

- Connect with [Ethan on LinkedIn](https://www.linkedin.com/in/ethanevansvp/)
- Taro members get a discount to join [**Ethan's Level Up community**](https://levelupwithethanevans.substack.com/taro25)

[Timeless Career Advice] What to Learn

[Timeless Career Advice] One on Ones

[Timeless Career Advice] Compounding Engineers vs Detractors

[Timeless Career Advice] What Do Software Engineers Do?

Become An Engineer Influencer [Part 2] - Michael's Backstory

Michael saw the transformative power of influence after he left his job at Netflix. This video reveals the new opportunities enabled by cultivating an audience. Michael talks about which platforms he grew on, among Medium, LinkedIn, Twitter, a newsletter, and more.

Connect with Michael:

- LinkedIn: <https://www.linkedin.com/in/michael-lin-tech/>
- Twitter: [https://x.com/\_michaellin](https://x.com/%5C_michaellin)
- Newsletter: <https://www.michaellinwrites.com/>

Write A Stellar Resume As A Software Engineer [Part 11] - Self Ratings

There's tremendous pressure to stand out with your resume as a software engineer, especially as you usually need to beat out 100+ or even 1000+ other engineers to get an interview opportunity. This lesson teaches you:

- Why self ratings don't add any value to a resume
- The dangers behind self ratings on a resume, particularly with more junior engineers

Paper Reading: MyRocks: LSM-Tree Database Storage Engine Serving Facebook's Social Graph

Session led by [Dharin Shah](https://www.linkedin.com/in/dharinshah/)

**Event description**

Facebook uses MySQL to manage tens of petabytes of data in its main database named the User Database (UDB). UDB serves social activities such as likes, comments, and shares. In the past, Facebook used InnoDB, a B+Tree based storage engine as the backend. The challenge was to find an index structure using less space and write amplification.

LSM-tree has the potential to greatly improve these two bottlenecks. RocksDB, an LSM tree-based key/value store was already widely used in variety of applications but had a very low-level key-value interface. To overcome these limitations, MyRocks, a new MySQL storage engine, was built on top of RocksDB by adding relational capabilities. With MyRocks, using the RocksDB API, significant efficiency gains were achieved while still benefiting from all the MySQL features and tools. The transition was mostly transparent to client applications.

The paper was published at the **International Conference on Very Large Databases (VLDB)**: [**https://research.facebook.com/publications/myrocks-lsm-tree-database-storage-engine-serving-facebooks-social-graph/**](https://research.facebook.com/publications/myrocks-lsm-tree-database-storage-engine-serving-facebooks-social-graph/).

Paper authors:

- [**Yoshinori Matsunobu**](https://www.linkedin.com/in/yoshinorimatsunobu/)
- [**Siying Dong**](https://www.linkedin.com/in/siyingdong/)
- Herman Lee

Negotiation Course: Reneging An Offer

Backing out after accepting an offer (*"reneging on the offer"*) is unfortunate but happens more frequently than you think. Imagine that you accepted a job offer, but two weeks later, you finally get an offer from another company that is better in every way. What do you do?

First, prevention is the best cure: try to get all the offers around the same time.

If the timing mismatch is unavoidable, you should do what’s best for you: don’t worry too much about the company.

In the US, employment is at-will, so there’s nothing legally preventing you from joining. Of course, you may have to give back any kind of signing bonus.

There may be reputational damage: talk about why the opportunity is incredibly unique and you hope to work with them again. Reneging on a large company is not as big a deal compared to a startup.

Negotiation Course: Recruiter Case Study: Insights From An Ex-Meta Recruiter

This was a conversation with a recruiter who spent several years as a recruiter at Facebook (Meta) and Pinterest. 

- The tactic of *"I will sign the offer if you meet me here"* is **effective if it's sincere**. You should be prepared to explore/defend various options around other ways the company could compel you to sign the offer.
- Exploding offers are almost always fake. Recruiters know that "**time kills all deals**" so they want to close candidates quickly. However, as a candidate, you can and should push back on an arbitrary deadline. Ask why the timing constraint exists and share why you need more time.
- Be graceful when you turn down a company's job offer. This recruiter would frequently be able to hire candidates several years later who had received an offer if they kept the relationship alive.

Negotiation Course: What's Best To Negotiate

As you think about what components in the offer to negotiate, you should consider: 

1. **Where do you have the most alignment with the company?** For example, reducing the "clawback period" for your signing bonus from 1 year to 3 months is unaligned since the company wants to incentivize you to stick around beyond 3 months. On the other hand, doubling your equity package is more aligned, since your comp will go up if the company does well.
2. **Where can the recruiter best help you?** Generally, a recruiter is powerless to adjust things like 401(k) match or performance bonuses since they're standardized across the company. However, recruiters are able to adjust salary or equity, especially if you are willing to make trade-offs between them.

Another dimension to consider is that equity is riskier than salary, so, therefore, it should translate to a higher potential reward. Stock options and RSUs fluctuate in value based on the market.

If you're ok with the risk tolerance, you are likely able to get more equity vs salary, e.g. increase your equity $20K/year vs salary $5K/year. This is an **obviously** good trade for a Big Tech (FAANG) company, which will have a fairly stable stock price.

Negotiation Course: When Should You Negotiate? And When Should You Not?

Negotiation makes the most sense for "high-leverage jobs" like software engineering or most other jobs in tech. An example of a low-leverage job would be to stock shelves in a grocery store or drive a taxi in NYC. The difference between the best and average worker in those fields is not that large. But in engineering, the difference in output for the best vs the average can easily be 10x or 100x.

Within the high-leverage category, there are jobs that have many comparable data points (e.g., junior or mid-level engineer) and those that are bespoke because they're rare/senior at the company, e.g., executive level or senior engineering leads.

Negotiation makes less sense for jobs that are purely stepping stones, or those that are time-bound. The classic example here is for internships. A good litmus test is if you know anyone who has ever negotiated that offer, e.g. no one at Stanford ever negotiated the summer research pay.

Finally, negotiation does not make sense if you already accepted the offer at a lower number.

Nail Your Promotion As A Software Engineer [Part 28] - This Might Not Be Enough

So many software engineers feel unfairly treated when it comes to their promotion, being stuck at the same level forever. And here's the thing - A lot of them are right! This lesson teaches you:

- The right mentality to have when it comes to deciding between doubling down and jumping ship
- The large career cost of switching teams, especially if you are changing companies in the process
- A framework to use when figuring out whether you should give up and change teams or continue plodding on and fighting for that promotion

Ace Your Tech Interview As A Software Engineer [Part 25] - Practical Coding

Practical interview coding rounds are the purest form of software engineering and what software engineers generally hope the interviews are (at least when they complain about data structures and algorithms problems online). This lesson teaches you:

- What a practical coding round is and when to expect it
- What kinds of companies give practical coding rounds
- How to prepare for practical coding rounds

To get the absolute best practice for practical coding rounds, check out our side projects playlist: [\[Taro Top 10\] Building Impressive Side Projects](https://www.jointaro.com/playlist/vKUWMgmmaEvzcYUXZs4B/)

Handling a PIP: The Ultimate Guide To Navigating A PIP

There are two options after a PIP: either the employee will remove all the doubts about the performance concern, or the employee will be terminated.

Your job as an employee is to judge your manager’s intentions. Your manager is the most important person in the PIP, and more generally, in your career. Many managers view the PIP as a formality before termination, and they’ve already given up on you. In that case, **you need to leave.** You don’t win any bonus points by "proving them wrong."

If the manager is responsive to your questions, provides constant feedback, and has a reasonable PIP plan, you may have a chance to succeed.

However, in the vast majority of cases, our recommendation is that you **must start looking for a** **new job.**

The biggest reason a PIP is not worth fighting is because **you want to work for people who believe in you**. This is critical for career success: you need someone who is unfailingly supportive of you, whether that's a friend, mentor, or manager. A PIP does not feel like support. In fact, it feels like the opposite. Your manager felt your performance was weak enough that they literally spent hours documenting how you fell behind, and then informed you in a legal manner.

The joke is that PIP should stand for “Paid Interview Period”, and that is honestly our recommendation for many tech workers who receive a PIP.

Here is the **PIP Evaluation Framework** in order to make the best decision once you’ve received the PIP. If 1+ of the following are true, you should **not** plan to have a long-term future at your current company.

- Your manager is uncommunicative or closed off
- The time horizon for the assigned work on the PIP is unrealistic (e.g. 1 week for a launch)
- The goalposts for the projects keep shifting
- The PIP work and your “normal duties” result in an unmanageable workload
- Your team is unsupportive

Conclusion: The Ultimate Guide To Navigating A PIP

Thanks for being part of this course! Here are the main takeaways:

- A PIP **does not** mean your career is over
- Make it easy to receive feedback
- You should (probably) start looking for a new job
- Don’t over-share information
- Discussions:
  - [I have been put in PIP. What should I do?](https://www.jointaro.com/question/i2RqeCiAQJ04eU1rp0eQ/i-have-been-put-in-pip-what-should-i-do/)

  - [Bouncing back after termination](https://www.jointaro.com/question/iDARmEmqYKlCIhzKIMNh/bouncing-back-after-termination-what-can-i-do-to-move-forward/)

  - [Advice on PIP with unsupportive team?](https://www.jointaro.com/question/93GBTJ73ayNLPY0sLuHz/advice-on-pip-with-unsupportive-team/)

Pinterest Case Study: The Ultimate Guide To Navigating A PIP

This was a non-engineer who had several years of experience before joining Pinterest.

- **Before**: 90 days after joining, was told they needed to improve

- **During**: “Completely blindsided” when placed on PIP at the 4 month mark. Goalposts kept shifting, didn’t receive feedback until 4 weeks later

- **After**: Took the termination after taking leave for interview prep

Tech Career Growth Videos

Our instructional videos provide software engineers with insights needed for career growth. Masterclasses go incredibly in-depth on a specific tech topic while case studies are real examples from established engineering leaders.