Get The Rating You Deserve [Part 19] - Conclusion

**In this course, we’ve explored strategies for increasing our impact and achieving long-term success.**

We covered three key areas:

- **Understanding Impact Dynamics:** We learned how to create value and communicate it effectively to others.
- **Increasing Luck Surface Area:** We explored strategies for getting things done and sharing our work with the world.
- **Building an Empowering State:** We discussed the importance of cultivating a positive mindset, building strong relationships, and prioritizing self-care.

By applying these principles, we can improve our professional and personal lives. If you have any questions or would like to delve deeper into these concepts, please don’t hesitate to reach out.

If you want to get personalized support from Yogi, you can reach out to him at [**coaching@yogisharma.com**](mailto:coaching@yogisharma.com) or schedule an introductory call to dive into your situation at [**https://tinyurl.com/meetyogi**](https://tinyurl.com/meetyogi).

Master The DSA Interview [Part 20] - Missing What Matters

When you're doing a data structures and algorithms interview, you don't have a ton of time. That's why it's important to focus on what matters. This lesson teaches you:

- What order to code your solution in when it comes to happy flow and edge cases
- Why the core data structures and algorithms themselves often aren't that important during the interview
- How to get functionality for free, explained with a real-life Meta interview example
- A tactic you can use to prioritize components of your data structures and algorithms solution properly

Asking Great Questions [Part 14] - What Have You Tried?

If you don't do it right, asking questions can seriously damage your reputation among the team and mark you as a low-performer. This lesson teaches you:

- Why engineers in particular are extremely allergic to low-quality questions
- How low-quality questions can put you in the target of a PIP (performance improvement plan)
- A simple way to identify if a question is low-quality or high-quality based on its overall vibe
- 3 core tactics you should try if possible before asking a question
- What it means to masterfully incorporate what you've tried into a question, explained with an incredibly in-depth example

The MANY Benefits of Code Review (What You Didn't Realize)

In this video, we explore the deeper value of **code review**—going beyond its obvious impact on code quality to highlight how it shapes team culture, collaboration, and continuous learning. While improving code is a benefit, we emphasize that the long-term value lies in building a stronger, more aligned engineering team.

### Key Takeaways:

- **We use code review to improve code quality**: At a basic level, reviews catch issues and lead to cleaner, more maintainable code—but that’s just the surface-level benefit.
- **We treat code review as essential feedback**: Just like feedback in any other domain, having someone else evaluate our work helps us grow—technically and professionally.
- **We build team awareness and cross-pollination**: Code reviews help teams stay aligned and aware of each other’s work, which strengthens cohesion and product velocity.
- **We learn even when no changes are made**: Valuable discussions often emerge from understanding *why* code was written a certain way, even if the final diff remains unchanged. This raises the collective standards of the team.
- **We view code review as a cultural cornerstone**: We love it so much that reviewing code became a natural, even joyful, part of our daily routine—it’s how we grow, connect, and elevate our craft.

DSA Crash Course [Part 64] - Island Count Walkthrough

In this lesson, Alvin walks through the python implementation for the *island_count* problem.

Code along and test your work in the following editor workspace: <https://structy.net/problems/island-count?language=py>

If you need additional support taking these DSA skills and actually applying them, take [**Alvin's**](https://www.linkedin.com/in/alvin-zablan-b73a92117/) *complete* data structures and algorithms course on [**Structy**](https://structy.net/?utm_source=taro). You can try out the concepts yourself in their interactive code editor and learn advanced DSA patterns like stack exhaustive recursion.

Use [**this link to get 20% off**](https://structy.net/purchase?promo_code=taro20) the entire Structy DSA learning experience.

Follow Alvin on LinkedIn: [**https://www.linkedin.com/in/alvin-zablan-b73a92117/**](https://www.linkedin.com/in/alvin-zablan-b73a92117/)

Clear Communication For SWEs [Part 6] - The Pyramid Principle

In this video, I explain the Pyramid Principle, a powerful communication framework that structures information hierarchically for clear and logical communication. I discuss how to apply it in presentations and communications, emphasizing starting with the main idea, supporting it with arguments, and providing detailed evidence.

**Action requested:** Understand and apply the Pyramid Principle for efficient and effective communication.

Connect with me on LinkedIn: <https://www.linkedin.com/in/ryan-wiens/>

Asking Great Questions [Part 11] - Avoid Question Ping Pong

If you want better answers faster on your question, the goal is simple: *Make it dead simple to answer your question*. But how do we do that? This lesson teaches you:

- A simple mental framework you can apply to your question to understand if it's good
- What a bad question looks like when it violates that mental framework
- How to use that mental framework to determine the quality of a question

Why You Should Always Negotiate Your Offers

- Negotiation is particularly life-changing, especially if you're early-in-career. It's also really high ROI as the cost is effectively just a couple emails and some potential awkwardness.
- Negotiation doesn't hurt anyone within or outside the company - It's effectively a part of life when it comes to the hiring game.
- What you negotiate for isn't connected to your costs: It's about getting what's fair given the market rate and your current leverage situation (i.e. do you have other offers).
  - Even if an offer is good given your personal situation, you should try negotiating, especially if it's below fair market rate for that level/company/geography and you have competing offers.
  - You can always do something with extra money!

If you need premier negotiation support, check out our 3+ hour negotiation course: [The Insider's Guide To Negotiating Your Tech Salary And Compensation](https://www.jointaro.com/course/the-insiders-guide-to-negotiating-your-tech-salary-and-compensation/)

Become An Open Source Master [Part 16] - Understand The Basics

We need to learn the codebase of a new open source project to contribute effectively. It's important to understand the bigger picture instead of focusing on every single line of code. Some questions worth asking when approaching a new codebase are: what is the purpose of the code, what are the opinions of the developers, and how is the code structured?

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

How To Be An Effective Tech Lead [Part 11] - Set The Direction

One of the crowning growth moments for software engineers is when they become less focused on *how* to get where they need to be and more focused on *where* they should be going to begin with. That direction component is a huge part of a tech lead's responsibilities. This lesson teaches you:

- What it means to define good direction for a project
- The components behind effective direction-setting for a project
- How to decompose a goal into actionable items
- The ingredients behind empowering your team to work cohesively

To dive deeper into project management: [\[Taro Top 10\] Project Management](https://www.jointaro.com/playlist/4CtqCnUYwqedd0my2EEw/)

Negotiation Course: The Importance Of Equity In Negotiation

Most companies have larger allowable bands in the equity component of their compensation. For this reason, you should treat it with additional importance as a way to best meet your compensation target. 

There are 2 reasons why companies are more willing to increase equity (RSUs or stock options) compared to other parts of the offer: 

1. Equity doesn’t hurt the profit and loss (P&L) statement of the company. This is especially important for startups.
2. Equity has inherent incentive alignment between the company and the employee. The employee will be more motivated to grow the company because the equity is worth more when the company succeeds.

In addition, equity is generally less understood by employees. Rahul's friend at Uber shared stories of people who rejected an equity grant and simply asked for an additional salary (when they could have gotten significantly more in equity). The risk tolerance for receiving stock compensation is less understood outside the US, e.g. in European countries.

For many people in tech, their base salary is enough to cover their day-to-day living expenses. In a major metro area, an engineer's base salary in a Big Tech co can range from $100K - $300K. This can cover things like rent, food, travel, and even some savings.

If you are in this scenario, Rahul's advice is to be **very aggressive** about increasing the equity component of the comp package. You should tell the recruiter that you want to "*take part in the success that you'll help to create at the company*" and therefore want to be at the highest possible range for equity. 

We'll share more about sample phrases you can use later in the course.

Asking Great Questions [Part 10] - Put Yourself On The Line

When you ask a question, you are asking some human(s) out there to spend some time providing you with an answer. To make this process go better, you must do everything you can to prevent the interaction from being one-sided in the wrong direction. This lesson teaches you:

- How to swap the time dynamics behind a question in your favor
- What it looks like to offer your time within a question, explained with an in-depth example
- When and how to take the more extreme route of offering synchronous time, explained with an in-depth example

Grow From Junior To Mid-Level Engineer [Part 15] - Participating In Bigger Meetings

Big meetings can be daunting for engineers, especially junior ones - What if you say something dumb? This lesson teaches you:

- The difference between junior and mid-level engineers when it comes to meeting participation, explained with very simple pictures
- Tactics you can use to come up with more to say in meetings, even if you're the most junior person there
- A clever tactic you can use to participate in a meeting and add value to the discussion, even if you aren't entirely sure of what's going on

DSA Crash Course [Part 65] - Minimum Island Approach

In this lesson, Alvin explores the strategy to solving the following interview problem:

> Write a function, *minimum_island*, that takes in a grid containing Ws and Ls. W represents water and L represents land. The function should return the size of the smallest island. An island is a vertically or horizontally connected region of land.
>
> You may assume that the grid contains at least one island.

```
grid = [
['W', 'L', 'W', 'W', 'W'],
['W', 'L', 'W', 'W', 'W'],
['W', 'W', 'W', 'L', 'W'],
['W', 'W', 'L', 'L', 'W'],
['L', 'W', 'W', 'L', 'L'],
['L', 'L', 'W', 'W', 'W'],
]

minimum_island(grid) # -> 2
```

```
grid = [
['L', 'W', 'W', 'L', 'W'],
['L', 'W', 'W', 'L', 'L'],
['W', 'L', 'W', 'L', 'W'],
['W', 'W', 'W', 'W', 'W'],
['W', 'W', 'L', 'L', 'L'],
]

minimum_island(grid) # -> 1
```

```
grid = [
['L', 'L', 'L'],
['L', 'L', 'L'],
['L', 'L', 'L'],
]

minimum_island(grid) # -> 9
```

If you need additional support taking these DSA skills and actually applying them, take [**Alvin's**](https://www.linkedin.com/in/alvin-zablan-b73a92117/) *complete* data structures and algorithms course on [**Structy**](https://structy.net/?utm_source=taro). You can try out the concepts yourself in their interactive code editor and learn advanced DSA patterns like stack exhaustive recursion.

Use [**this link to get 20% off**](https://structy.net/purchase?promo_code=taro20) the entire Structy DSA learning experience.

Follow Alvin on LinkedIn: [**https://www.linkedin.com/in/alvin-zablan-b73a92117/**](https://www.linkedin.com/in/alvin-zablan-b73a92117/)

This Is What Most Companies Get WRONG About Promotion

- 2 types of promotion:
  - **Strong companies:** Already functioning at the next level
  - **Weak companies:** Mastery of current level + long tenure
- In the best tech companies, each level is fundamentally different from the previous one. This is why promotion is lagging there: You need to be functioning at the next level consistently for 3-6 months before getting promotion.
- The goal is to avoid the Peter Principle: Getting promoted to higher and higher levels until you are completely incompetent. When levels are truly meaningful, it's really easy to be doing great at your current level and then be struggling to survive at the next one.

DSA Crash Course [Part 79] - Non Adjacent Sum Approach

In this lesson, Alvin explores the strategy to solving the following interview problem:

> Write a function, *non_adjacent_sum*, that takes in a list of numbers as an argument. The function should return the maximum sum of non-adjacent items in the list. There is no limit on how many items can be taken into the sum as long as they are not adjacent.
>
> For example, given: \[2, 4, 5, 12, 7\]
>
> The maximum non-adjacent sum is 16, because 4 + 12. 4 and 12 are not adjacent in the list.

```
nums = [2, 4, 5, 12, 7]
non_adjacent_sum(nums) # -> 16
```

```
nums = [7, 5, 5, 12]
non_adjacent_sum(nums) # -> 19
```

```
nums = [7, 5, 5, 12, 17, 29]
non_adjacent_sum(nums) # -> 48
```

```
nums = [
72, 62, 10,  6, 20, 19, 42,
46, 24, 78, 30, 41, 75, 38,
23, 28, 66, 55, 12, 17, 9,
12, 3, 1, 19, 30, 50, 20
]

non_adjacent_sum(nums) # -> 488
```

If you need additional support taking these DSA skills and actually applying them, take [**Alvin's**](https://www.linkedin.com/in/alvin-zablan-b73a92117/) *complete* data structures and algorithms course on [**Structy**](https://structy.net/?utm_source=taro). You can try out the concepts yourself in their interactive code editor and learn advanced DSA patterns like stack exhaustive recursion.

Use [**this link to get 20% off**](https://structy.net/purchase?promo_code=taro20) the entire Structy DSA learning experience.

Follow Alvin on LinkedIn: [**https://www.linkedin.com/in/alvin-zablan-b73a92117/**](https://www.linkedin.com/in/alvin-zablan-b73a92117/)

DSA Crash Course [Part 62] - Shortest Path Walkthrough

In this lesson, Alvin walks through the python implementation for the *shortest_path* problem.

Code along and test your work in the following editor workspace: <https://structy.net/problems/shortest-path?language=py>

If you need additional support taking these DSA skills and actually applying them, take [**Alvin's**](https://www.linkedin.com/in/alvin-zablan-b73a92117/) *complete* data structures and algorithms course on [**Structy**](https://structy.net/?utm_source=taro). You can try out the concepts yourself in their interactive code editor and learn advanced DSA patterns like stack exhaustive recursion.

Use [**this link to get 20% off**](https://structy.net/purchase?promo_code=taro20) the entire Structy DSA learning experience.

Follow Alvin on LinkedIn: [**https://www.linkedin.com/in/alvin-zablan-b73a92117/**](https://www.linkedin.com/in/alvin-zablan-b73a92117/)

Grow From Senior To Staff Engineer [Part 19] - Code Machine

As a software engineer, one of your most powerful tools to land more impact is to write more code. While many engineers write less code as they grow to staff, there is 1 large exception. This lesson teaches you:

- What the code machine staff engineer archetype is
- Why the code machine archetype is quite rare and usually not supported
- How to become a code machine

As this lesson talks about, code machines have both a stunning degree of velocity and quality. Level up your code quality here: [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

Taro Book Club: Designing Data Intensive Applications - Chapter 1

Discussion led by: [**Ankur Agrawal**](https://www.linkedin.com/in/erankuragr/) & [**Raj Shah**](https://www.linkedin.com/in/therajshah/)\
\
In this #taro-bookclub discussion, we'll go over Chapter 1 of the book [**"Designing Data-Intensive Applications"**](https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321) by Martin Kleppmann. This chapter is about Reliable, Scalable, and Maintainable Applications and will provide good mental models to think about reliability, scalability and maintainability of Distributed Data Systems.

Here's the agenda:

- We’ll break down and discuss the key concepts from Chapter 1.
- There will also be time for any questions and answers you might have.

Get ready for our first session on this engaging and informative book!

We hope to see you for Chapter 2 as well: [**Taro Book Club: Designing Data Intensive Applications - Chapter 2 (Data Models and Query Languages)**](https://www.jointaro.com/event/taro-book-club-designing-data-intensive-applications-chapter-2-data-models-and-query-languages/)

If you don't have a Taro Premium membership, you can get it at a discount with Ankur's special link here: [**https://www.jointaro.com/r/eventu507/**](https://www.jointaro.com/r/eventu507/)

Nail Your Promotion As A Software Engineer [Part 30] - Be Patient

It can be frustrating waiting so long to get promoted as a software engineer. You've been working so hard for so long, and you still don't have that fancier title. This lesson teaches you:

- Why getting promoted is so hard
- The right mentality to always have as you're going through the promotion process
- A clear framework you can use to determine if you are truly getting better as an engineer

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.