Asking Great Questions [Part 16] - Attaching The Code

Code is heavy, especially when viewed outside the context of an IDE or code review platform like GitHub. It's critical to keep this in mind when you're asking questions about your code. This lesson teaches you:

- The most common failure mode when it comes to attaching code to questions
- What it means to gracefully attach code to your question, explained with an in-depth example
- A trick you can use to share a lot of code without overwhelming your question

To learn how to isolate relevant code, take our debugging masterclass: [\[Masterclass\] How To Become A Debugging Master And Fix Issues Faster](https://www.jointaro.com/lesson/ioR6WzamAIUTpySLAr7o/masterclass-how-to-become-a-debugging-master-and-fix-issues-faster/)

Asking Great Questions [Part 13] - Please Don't Do This: Leading Hello

A lot of what we're taught growing up doesn't translate very well into the software engineering world, and how we greet people is one of those things. This lesson teaches you:

- Why a standard solitary "Hello" or "Hi" is a terrible way to get help digitally
- What being polite actually means in the engineering world
- What you should do instead of leading hello

If you want to join the cause of "No Hello": [https://nohello.net/](https://nohello.net/en/)

Asking Great Questions [Part 12] - Length Balancing

One of the most important attributes of a question is its length, and the reason why is simple: The length of a question is directly connected to how much time a helper needs to spend answering it. This lesson teaches you:

- Why questions that are too short are bad
- Why questions that are too long are bad
- What to do if your question seems too short
- What to do if your question seems too long
- What a healthy question length is, demonstrated with a real-world example
- A tactic you can use to keep the length of your question in-check while still including a lot of important context

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

[Become A Go-To Person 17/18] Go Deeper: Follow Through

["Become an expert" template](https://jordancutler.notion.site/Become-an-expert-template-80b8a2dc2c7148bea01d2180adf1c9bb)

- 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/)
- Get a discount on Jordan's newsletter here: <https://read.highgrowthengineer.com/taro>

[Become A Go-To Person 16/18] Recap

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 13/18] Answer Questions To Become An Expert

[Become A Go-To Person 12/18] Lead Projects To Become An Expert

[Become A Go-To Person 5/18] Become The Technical Expert

Tech Lead Blueprint 11/17 - Empathetic Leadership

Connect with Lalit on LinkedIn: <https://www.linkedin.com/in/lalitkundu/>

Tech Lead Blueprint 10/17 - Commit To Project Success

Tech Lead Blueprint 9/17 - Tracking Progress

Tech Lead Blueprint 7/17 - Team Productivity

How To Be An Effective Tech Lead [Part 14] - Manage Expectations

As a tech lead, you will have a ton of things to do and not a ton of time. Because of this, you need to be crystal clear about what you're working on, why you're working on it, and when you're going to have that work done. This lesson teaches you:

- The danger and hugely negative consequences of mismanaging expectations
- Proactive mechanisms you can use to maintain alignment around expectations
- How to properly react and communicate when expectations are falling through

How To Be An Effective Tech Lead [Part 12] - Foster Trust

Trust or social capital is the primary currency you need to get anything done as a tech lead. This lesson teaches you:

- Why fostering trust is so important for team efficiency, explained through a simple example
- How to build up trust when things aren't going perfectly (which will inevitably happen to you as a tech lead)
- How to build up trust when things are going well, taking full advantage of positive momentum

Learn how to build deep relationships fast here: [\[Masterclass\] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)

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

How To Be An Effective Tech Lead [Part 10] - Be An Excellent Communicator

One way to envision your role as a tech lead is that you're the "glue" that holds the team together. The core way that glue manifests is through your communication. This lesson teaches you:

- Why excellent communication is vital towards "conducting the orchestra"
- How to communicate empathetically
- How to communicate clearly
- The right amount to communicate (it's often higher than you think)

Turn yourself into a communication master with our course: [\[Course\] Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)

How To Be An Effective Tech Lead [Part 9] - It's All About The Team

The best tech leads are selfless, not selfish. But what exactly does that mean? This lesson teaches you:

- The proper mindset to have as a tech **lead**
- A simple mental model to understand your overall goal as a tech leader
- How to divide up work as a tech lead
- What sort of tasks you should take on within a project as a tech lead

How To Be An Effective Tech Lead [Part 5] - Think High-Level, Plan Long-Term

As a software engineer, it's way too easy to get lost in the weeds, fixating on details that ultimately don't matter. As a tech lead, you need to avoid rabbit holes like the plague. This lesson teaches you:

- The overall mindset tech leads must have when planning through and executing a project
- What it actually means to see the forest, not just the trees, with a detailed example from Jocelin's past
- How to own the overarching goal behind a project or workstream
- How to thoroughly think through dependencies

The Really Important Job Interview Questions Engineers Should Ask (But Don't)

Basic questions that engineers should ask when interviewing at any company. 

From the Posthog blog: <https://posthog.com/founders/what-to-ask-in-interviews>

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.