DSA Crash Course [Part 22] - Linked List Intro Lecture

In this lecture, Alvin explains the basic structure of a singly-linked list.

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/>

DSA Crash Course [Part 3] - Max Value Walkthrough

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

Code along and test your work in the following editor workspace: <https://structy.net/problems/max-value?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/>

Break Into Tech And Become A Software Engineer [Part 1] - Intro

In this lesson, we explore how anyone can transition into a tech career, regardless of their background.

This lesson covers:

- Brian's journey from a troubled past to becoming an engineering manager and business owner
- How his late start in tech, at age 30, began with small interactions while driving for Uber
- The decision to attend a coding bootcamp, where his passion for coding took off
- The importance of support from friends and community in learning to code and landing a first job
- The idea that people from all kinds of backgrounds, including those with difficult pasts, can break into the tech industry

If you need extra help breaking into tech, join Brian's exclusive, cohort-based bootcamp (just 10 students per batch). Use this link for Taro users for $800 off: <https://www.parsity.io/taro>

Connect with Brian on LinkedIn: <https://www.linkedin.com/in/brianjenney/>

21 Ways to Make Yourself a Better Engineer (From a Senior Engineer at Pinterest)

Join Taro and [**Jordan Cutler**](https://www.linkedin.com/in/jordancutler1/), a Senior Engineer at Pinterest and [**High Growth Engineer**](https://read.highgrowthengineer.com/) author to learn 21 rapid-fire ways to become a better engineer. You'll learn the top underused tips and skills to grow in your career.

We'll cover:

- Career growth
- Influence
- Communication
- Managing up
- Leading projects
- Technical skills
- Productivity

Be ready for practical and actionable advice. No BS included.

Helpful links: 

- [Slides](https://drive.google.com/file/d/1PEgnDJEa4wRw3bjxe22obyfP2qSm9lBB/view?usp=sharing)
- [Jordan on LinkedIn](https://www.linkedin.com/in/jordancutler1/)
- Jordan's newsletter with 68K+ subscribers: [High Growth Engineer](https://read.highgrowthengineer.com/)
- Jordan's course on Taro: [Become The Go-To Expert As A Software Engineer](https://www.jointaro.com/course/become-the-go-to-expert-as-a-software-engineer/)

[Become A Go-To Person 1/18] How This Course Works

A course by [Jordan Cutler](https://www.linkedin.com/in/jordancutler1/), Senior Software Engineer at Pinterest and Author of the [High Growth Engineer Newsletter](https://read.highgrowthengineer.com/)

Maximize Your Productivity As A Software Engineer [Part 22] - Introspect And Reflect

As software engineers, we are constantly getting things wrong, including our productivity system. This is why it's important to learn how to evolve and improve over time - There are very things in engineering where you can just set it and forget it. This lesson teaches you:

- How to set up introspection time and why it's important
- What questions to ask yourself when you reflect
- How to process action items to improve your productivity system

Maximize Your Productivity As A Software Engineer [Part 13] - Decomposition

When you get a huge project as a software engineer, it's easy to get overwhelmed and just sort of... do nothing (or close to it). This lesson teaches you:

- What a well-decomposed project looks like with a concrete example
- How decomposing projects hacks your brain to make it more motivated and productive

To dive deep into tactics on decomposing projects, check out our in-depth explainer: ["How do I make software less overwhelming?"](https://www.jointaro.com/question/YseMPDw538jhyS1MWlTs/how-do-i-make-software-less-overwhelming/)

Learn from the code quality course 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/)

Write A Stellar Resume As A Software Engineer [Part 21] - The REAL Secret For A Top Tier Resume

Unfortunately, it's possible to optimize your resume to the teeth and still not get results. This will be incredibly common for more junior engineers. This lesson teaches you:

- A simple 2-step process to understand how to make an incredible resume
- What to do if you have perfected your resume and you still aren't getting enough interview calls
- Why you are far more powerful than you realize the second you learn how to code and deploy software to production
- How to build impressive side projects that are meaningful on a resume and get you interviews
- How to make impressive open-source contributions that are meaningful on a resume and get you interviews

To dive deeper into building impressive side projects: [\[Taro Top 10\] Building Impressive Side Projects](https://www.jointaro.com/playlist/vKUWMgmmaEvzcYUXZs4B/)

To dive deeper into making impressive open-source contributions: [\[Course\] Become An Open Source Master](https://www.jointaro.com/course/become-an-open-source-master/)

Write A Stellar Resume As A Software Engineer [Part 5] - Resume Gaps

Having an employment gap is effectively inevitable as a software engineer, especially in a layoff-economy. This leads to resume gaps, which unfortunately have a lot of stigma. This lesson teaches you:

- Why employers (rightfully) hold resume gaps against you
- How to include your resume gap on your resume
- What to do in common resume gap scenarios if a company probes you about it during an interview

If you have recently been laid-off, you can check these out as well: [\[Taro Top 10\] Navigating Tech Industry Layoffs](https://www.jointaro.com/playlist/pE7pP0nXDx4X7mOChzHS/)

Grow From Mid-Level To Senior Engineer [Part 9] - Code Quality

Mid-level engineers are usually very solid at coding, but what most don't realize is how high the ceiling truly is when it comes to code quality. This lesson teaches you:

- The difference in code quality between junior, mid-level, and senior engineers
- What a senior engineer level pull request looks like

Become a code quality master by taking our course 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/)

Master The Behavioral Interview [Part 23] - Just Be A Human

Behavioral interviews are really just an exercise in communication (a skill many software engineers struggle with). This lesson teaches you:

- The difference between being an introvert (this is fine) and shy (this is really bad for your career in tech)
- The right mindset to have when it comes to building relationships and the underlying skills necessary to ace behavioral interviews
- The secret behind getting extremely good at communication

To get better at communication, check out our course: [\[Course\] Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)

Master The Behavioral Interview [Part 11] - Interviews Are A 2-Way Street

One of the easiest ways to tank your career as a software engineer is to join the wrong company or team. Despite this, so many software engineers squander their time in behavioral interviews to uncover extremely valuable information about the quality of an organization. This lesson teaches you:

- Why not having thoughtful prepared questions to ask the interviewer makes you look really bad in a behavioral round
- The critical career importance of behavioral interviews being a 2-way street

Master The Behavioral Interview [Part 8] - Timing

Behavioral interviews are intense, containing more questions than every other interview type. This greatly affects how you need to talk to pass these rounds as a software engineer. This lesson teaches you:

- Why behavioral interviews are a marathon
- How long you should take per behavioral interview answer
- Tactics you can use to communicate more efficiently

For more advice on communicating concisely: ["How to make communication succinct and more impactful?"](https://www.jointaro.com/question/QDLV5owweJveRLlspOdc/how-to-make-communication-succinct-and-more-impactful/)

Onboarding Tips Within Larger Companies

In a large company, you should expect a more formal onboarding process. However, don’t let this be an excuse to move slowly. Your goal is (still) to set up your environment and land code within a week.

Big companies will have many teams which may have slightly competing priorities. That means you need to invest in relationships and understand how the work connects between teams. Disperse and collect knowledge from around the company.

Spend some time understanding the unique terminology and culture of the company. Companies like Amazon, Meta, Google, Microsoft are large enough that they have their own set of acronyms, languages, and cultures!

Figuring Out What Matters In A Codebase

In a large codebase, the code will follow the Pareto Principle (the 80/20 rule): 20% of the components account for 80% of the impact. So your goal as the engineer is to spend most of your time on the 20% of code that matters to the business and matters to your coworkers.

How do you figure out where that 20% comes from?

- Talk to people
- Use blames to find hotspots
- Look for patterns in code reviews
- Look at past alerts and what triggered them

Case Study: Setting Up Your Environment

One of the first tasks for an engineer in a new company is to setup their environment. 

- Your goal is **not** to setup your environment

- Your goal is to **do something that the environment setup enables**, e.g. make a copy or color change

Abstraction is essential when you’re working in a large codebase. Don't try to understand everything you come across: there will surely be a guide or script that you'll blindly follow, and that's ok. Keep your focus on completing the setup so you can make progress.

If you get blocked (*you probably will...*), forecast ahead what's coming and check if there's something else you can do in parallel.

Ace Your Tech Interview As A Software Engineer [Part 30] - Talk To Your Recruiter

Too many software engineers see the tech recruiter as the enemy when they really shouldn't be. In reality, one of the core keys behind a successful interview loop is leveraging your recruiter optimally. This lesson teaches you:

- How to understand the world through the eyes of a recruiter, particularly when they have given you a chance and let you into their company's interview process
- Why software engineers usually fail to collaborate with their recruiter properly to maximize their chances of passing the interview
- The true cost of interviewing a software engineer (it's probably higher than you realize)
- How you can reach out optimally to recruiters to figure out what's going to be on your upcoming interview with an in-depth message example

Ace Your Tech Interview As A Software Engineer [Part 14] - Referrals

Having a current employee put you into their hiring pipeline via a referral is one of the most powerful ways to level up your job search. However, referrals are often misunderstood by software engineers. This lesson teaches you:

- The 2 different types of referrals and which one is better (spoiler: engineers usually struggle getting the better one)
- The massive difference between *weak referrals* and *strong referrals*
- Why you are more special than you realize and how you can leverage that to get more strong referrals
- How to approach professional networking properly to cultivate huge amounts of strong referrals over time

To help you get strong referrals, check out our networking course: [Networking Guide: Build Deep Relationships Quickly In Tech](https://www.jointaro.com/course/networking-guide-build-deep-relationships-quickly-in-tech/)

Level Up Your Code Quality As A Software Engineer [Part 21] - Non-Descriptive Names

Naming: It's important for your children but quite important for your code as well. When it comes to your variables, methods, and classes, you should put in the effort to name them properly. This lesson will teach you:

- Why descriptive, high-effort names can add up to add a huge amount of quality to a codebase
- How to identify a poor name in code and the common patterns leading to it
- How much time you should spend on each type of name and how to prioritize accordingly, particularly in code review feedback
- The mentality to convert bad names to good names in code with an in-depth example walking through a classic utility method

Level Up Your Code Quality As A Software Engineer [Part 14] - How To Handle Migrations

There is term called "promotion-driven development" where software engineers propose big refactors and migrations to look good but don't fully follow through. This is especially common in Big Tech. This lesson will teach you:

- How to do code migrations properly
- How to judge the quality of a codebase based off of its consistency and how "good, modern code" can actually be harmful to the health of the codebase overall
- The mental and operating model behind how new engineers code, which is especially important if you're a tech lead (never forget this!)

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.