DSA Crash Course [Part 72] - Sum Possible Walkthrough

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

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

DSA Crash Course [Part 14] - Pair Product Approach

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

> Write a function, *pair_product*, that takes in a list and a target product as arguments. The function should return a tuple containing a pair of indices whose elements multiply to the given target. The indices returned must be unique.
>
> Be sure to return the indices, not the elements themselves.
>
> There is guaranteed to be one such pair whose product is the target.

```
pair_product([3, 2, 5, 4, 1], 8) # -> (1, 3)
```

```
pair_product([3, 2, 5, 4, 1], 10) # -> (1, 2)
```

```
pair_product([4, 7, 9, 2, 5, 1], 5) # -> (4, 5)
```

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 11] - Most Frequent Char Walkthrough

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

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

How to Crack System Design Interviews - Part 6: Mock Interview

This video demonstrates a system design interview for analyzing Snapchat filter usage. We are tasked with designing a system to track and analyze filter usage data for executives and product managers. Here's what we do:

- **Gather requirements:** We clarify the scope of the system, including the number of filters, their dynamic nature, and the desired metrics (daily, weekly, monthly usage, and potentially hourly breakdowns).

- **Design the system:** We propose a write-heavy system with separate read and write paths to optimize performance. The write path handles incoming events from users, while the read path aggregates and transforms data for querying.

- **Consider scalability:** We discuss sharding and using a write-optimized database like Cassandra to handle the high volume of incoming events.

- **Address data aggregation:** We explore using Apache Spark to process and aggregate data based on time and user demographics, storing the results in a database like DynamoDB.

- **Differentiate query types:** We propose separate APIs for common, pre-aggregated queries and custom queries, acknowledging the potential latency differences between the two.

[Gaurav Sen](https://www.linkedin.com/in/gkcs/) has conducted 1000s of system design interviews while working at Uber and building his [YouTube channel](https://www.youtube.com/@gkcs) to 500K+ subscribers. His platform [InterviewReady](https://interviewready.io/?_aff=JOINTARO) combines video explainers, live Zoom classes, and an automated System Design Judge.

Master The DSA Interview [Part 26] - Find A Buddy

When it comes to data structures and algorithms, it's best to not go it alone. This lesson teaches you:

- Why data structures and algorithms is the easiest part of the interview space to partner with someone on
- How having a data structures and algorithms buddy is greatly helpful for your personal morale
- A sample meetup agenda that you can use when you meet with your data structures and algorithms interview buddy

Find a data structures and algorithms interview buddy here: <https://www.jointaro.com/networking/?selectedServices=Mock+Interviews>

Break Into Tech And Become A Software Engineer [Part 22] - Maintaining A Positive Mindset

In this lesson, Brian emphasizes the importance of controlling the information you consume and maintaining a positive mindset when navigating the tech job market.

This lesson covers:

- The dangers of negative content, like fear-mongering videos on social media, which can distort your perception and feed into unnecessary fear and pessimism
- The "red car theory," where focusing on something makes you see it everywhere, influencing how you perceive reality, especially when it comes to fear and job security
- How to cultivate optimism by unfollowing fear-based content, following educational accounts, and using tools like the imposter syndrome killer worksheet to identify gaps and take actionable steps toward your goals

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

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

Break Into Tech And Become A Software Engineer [Part 19] - Selling Yourself As A Developer

In this lesson, Brian explains how to effectively market yourself as a software developer by positioning your skills and experience clearly to potential employers.

This lesson covers:

- Presenting yourself as a software developer, ensuring your resume and LinkedIn profile immediately reflect your skills and experiences in the field
- Avoiding terms like "junior" or "aspiring" developer and instead using strong language that showcases confidence, such as "architected," "led," and "deployed"
- Framing your achievements with a formula that highlights the technology used, the features created, and the outcomes achieved, demonstrating the value you bring to a team

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

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

Break Into Tech And Become A Software Engineer [Part 9] - Working In Sprints

In this lesson, Brian explains the value of working in sprints to manage large projects and goals, breaking them down into manageable tasks to maintain focus and track progress.

This lesson covers:

- The concept of sprints in software development, how to decompose large goals into smaller tasks, and making incremental progress toward them
- Using tools like Trello or notebooks to organize tasks, set deadlines, and track success with clear deliverables and realistic time estimates
- The importance of having a clear goal for each task and recalibrating your approach when necessary to stay on track

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

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

Break Into Tech And Become A Software Engineer [Part 2] - There's More To It Than Coding

In this lesson, we cover the essential steps beyond just learning to code for successfully transitioning into a tech career.

This lesson covers:

- The limitations of advice for engineers at top companies like FAANG and how to focus on realistic guidance for the majority of engineers
- The importance of developing a clear learning path, mastering time management, and focusing on one meaningful side project
- How building an online presence, networking authentically, and maintaining optimism throughout the journey is critical for career-switchers

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

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

Become An Open Source Master [Part 17] - How Is The Project Laid Out?

We need to understand the layout and structure of your target open-source project. We should identify the important modules and configuration items, and understand how the data flows through the project. We can also look for the entry points to the code base, such as the top-level file with all the exports or the command line interface.

- [Vue.js on GitHub](https://github.com/vuejs)

Connect with James:

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

Become An Open Source Master [Part 10] - How To Evaluate A Project’s Health

We can evaluate potential open-source projects by examining their issues and community interactions:

- **Analyze the Issues tab**: Look for a healthy ratio of solved to open issues, evidence of tagging and triage, and positive community engagement. Check for responsiveness to older issues.
- **Observe conversations around issues and pull requests:** Get a sense of the community's dynamics, code quality standards, and how welcoming they are to new contributors.
- **Check the Discussions tab (if available):** See how the community debates future changes and get a feel for the project's overall vibe.
- **Utilize the Insights tab:** Look at statistics like open and closed pull requests, active issues, and contributors to gauge the project's activity level.

Connect with James: 

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

Grow From Junior To Mid-Level Engineer [Part 18] - Done Is Better Than Perfect

We all make mistakes. In fact, we'll all make a lot of mistakes as software engineers, especially when we're junior. This lesson teaches you:

- The many types of dumb things you will inevitably do as a junior engineer (and continue doing as a mid-level/senior/staff/principal engineer)
- The simple growth mentality and formula you should follow to speed run the junior to mid-level engineer
- Why it's awesome to be the dumbest person in the room
- A simple mathematical way to understand the difference between a fast-growing junior engineer and a slow-growing junior engineer

Learn how to learn from your mistakes here: ["How to turn a string of silly mistakes into a mature positive outcome?"](https://www.jointaro.com/question/JybGyc935lsYbM8dAo7Y/how-to-turn-a-string-of-silly-mistakes-into-a-mature-positive-outcome/)

Grow From Junior To Mid-Level Engineer [Part 10] - Be Vulnerable

As a junior engineer, you will have a lot of weaknesses. How you deal with them will greatly determine how fast you grow. This lesson teaches you:

- The definition of true strength and how it relates to being vulnerable
- A simple strategy to become very independent very quickly
- The difference in mindset when it comes to independence for junior engineers vs. mid-level engineers
- Why you can't solo-study your way towards becoming a great engineer

Grow From Junior To Mid-Level Engineer [Part 9] - Become A Go-To Person

One of the most obvious signs of engineer seniority is that everybody on their team goes to them for help with certain areas. More senior = more areas. This lesson teaches you:

- The easy way to understand the difference in mentality between junior and mid-level engineers when it comes to ownership
- How to become a go-to person for your area
- The one mantra you need to follow to organically deduce all the proper action items to become a go-to person

Speed run your way to becoming a go-to person with [Jordan's](https://www.linkedin.com/in/jordancutler1/) course: [Become The Go-To Expert As A Software Engineer](https://www.jointaro.com/course/become-the-go-to-expert-as-a-software-engineer/)

Grow From Junior To Mid-Level Engineer [Part 5] - Decomposition

As a junior engineer, you will inevitably get a problem that's super scary which you have 0 idea how to solve. This will probably happen sooner rather than later. This lesson teaches you:

- The core tactic you need to master to solve large, incredibly complex problems
- Why decomposition is critical to being a good engineer
- The differences between junior and mid-level engineers when it comes to decomposition
- What it means to effectively decompose a problem, shown with an in-depth example

Take the code quality course here: [Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

Top System Design Interview Mistakes [Part 12] - Don't Ignore New Information

In this segment, we discuss the issue of ignoring new information during system design interviews. This happens when candidates fail to adapt their designs based on additional requirements or edge cases presented by the interviewer. Here’s the core points from the video:

- If the interviewer introduces new requirements or issues, like handling scenarios with no available drivers, we must adapt our design accordingly. Ignoring these hints can lead to incomplete or impractical solutions

- Sometimes, a simpler solution might be more effective. For example, informing customers that no drivers are available and suggesting they try again later might be a better approach than complex tracking systems

- When given new information, reassess and incorporate it into the design. This flexibility is crucial for creating effective and practical solutions

If you need extra help with your system design interview, [Formation.dev](https://formation.dev/partners/taro) can provide you hands-on, personalized support. Join us here: <https://formation.dev/partners/taro>

Clear Communication For SWEs [Part 16] - Next Steps And CTA

Thank you for watching my course on clear communication for software engineers! To enhance your communication skills, regular practice is essential, along with real-time feedback and role-playing exercises. This video also talks about my coaching services tailored to software engineers aiming to improve their communication skills, including non-native English speakers seeking confidence and effectiveness in communication. I can help you with public speaking, presentations, active listening, and everyday work communication, providing a hands-on approach in a supportive environment.

Connect with me on LinkedIn (it's also the best way to reach out to me for coaching services): <https://www.linkedin.com/in/ryan-wiens/>

Grow From Senior To Staff Engineer [Part 8] - Create Scope

The best engineers don't need to be told what to do. Creating scope is a behavior that usually develops as an engineer hit senior, and it's sharply refined as they grow to staff. This lesson teaches you:

- Why staff engineers often write less code than their senior engineer counterparts
- The difference between senior and staff engineers when it comes to creating scope
- A trap senior engineers often fall into when trying to creating scope
- The more graceful way competent staff engineers create scope within their organizations

Watch Rahul's internal tool case study here: [\[Case Study\] Building A Meta Internal Tool To Empower An Entire Org: Staff Promotion Story](https://www.jointaro.com/lesson/qvp2quodqAEWSkN7sayt/case-study-building-a-meta-internal-tool-to-empower-an-entire-org-staff-promotion-story/?playlistId=EWIo3USNcsgXbCs5PS0h)

Grow From Senior To Staff Engineer [Part 7] - Own The Goal

As a senior engineer, you are used to getting large, impactful projects and delivering them well, even if the initial project is incredibly ambiguous. However, this isn't nearly enough to get to staff. This lesson teaches you:

- The difference between senior and staff engineers between what they own on their teams and how staff engineers have a fundamentally higher altitude with their perspective
- What it means to own impact at a staff level instead of a senior, explained with an in-depth example
- The core, high-level behavior shift you need to make from an ownership perspective to grow from senior to staff

Asking Great Questions [Part 23] - Deep Thanks

Your journey doesn't end after you get an answer to your question, quite the opposite. The follow-through after getting a great answer is absolutely critical. This lesson teaches you:

- What a basic thanks looks like and an easy way to level up past it
- 5 more creative ways to give deeper thanks
- Why giving thanks is also a skill with tremendous depth that can unlock tremendous opportunity if you truly become one of the best in the world at it (with one of those opportunities being making everyone want to answer your questions all the time)

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.