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 8] - Find Companies Active In Open Source

The video discusses where to find open source projects to contribute to.

- The GitHub Octaverse Report and websites like <https://gitstar-ranking.com/> provide lists and rankings of companies and projects active in open source.
- Many large tech companies, like Microsoft and Google, have active open source ecosystems.
- The GitHub trending pages can help you discover new and interesting projects that are gaining popularity.
- Don't limit yourself to one type of project or technology; contributing to a variety of projects will broaden your skills and experience.

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

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)

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

[Become A Go-To Person 15/18] - Other Ways To Build Expertise

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

[Become A Go-To Person 7/18] How Expertise Translates To Influence

Maximize Your Productivity As A Software Engineer [Part 14] - Do The Hardest Thing First

When you get a tough project, it's tempting to tackle the easiest parts first because you already know how to do them, putting off the most difficult portions for later (you'll totally figure it out right?). This lesson teaches you:

- The difference between bad and good engineers when it comes to taking on a project
- Why tackling the hardest parts of a project first is effective risk management and a defining behavior of the best tech leadWhen you
- The massive team-wide benefit solving the hardest problem grants you

How To Be An Effective Tech Lead [Part 6] - Be The Code Guardian

As a tech lead, you are ultimately responsible for all the code that is delivered. The tricky part is that you need to do this without simply writing all of it. This lesson teaches you:

- The role tech leads play when it comes to cleaning up the code and paying down tech debt
- A high-level, multiplicative lever tech leads should pull to enforce code quality
- The in-the-weeds tactic tech leads need to constantly use to keep code quality high

To get better at code reviews, particularly those outside of your immediate domain, read through this: ["How to give better code reviews without full business context?"](https://www.jointaro.com/question/vio35mw1SYWM8AYojB2w/how-to-give-better-code-reviews-without-full-business-context/)

How To Be An Effective Tech Lead [Part 4] - Go Deep, Not Broad

In order to become a tech lead, you need to have incredibly effective technical skills. So what does that mean?

- What it takes for your technical skills to be respected as an engineer
- Why depth is more important than breadth
- What it means to have true technical depth, shown with an in-depth example

To sharpen your technical depth, take our code quality course: [\[Course\] Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

How To Be An Effective Tech Lead [Part 3] - What Makes A Good Tech Lead

Good tech leads provide immense value to their teams through a large collection of ways. This lesson teaches you:

- What it means from a technical skills perspective to be a good tech lead
- How good tech leads exercise effective leadership
- The mindset tech leads must champion

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.