Most of the time when we're writing code, we think about what the code is meant to do for us, we think of it as an offensive response to what we're solving, but what if we think of our code as a defensive strategy?

Your perspective is centered on now. It's very hard to imagine that the now, will soon be considered the past.

It's easy to imagine a duel system. A duel sense of identity - The impulsive side of us and the thoughtful side and it can change the way we think about how we work as engineers.

Think back to the times you learned your most important lessons. What exactly was the teacher?

When do you expect to achieve your goals? When do you expect to have the feeling that you have arrived?

What is it about engineering that you love? What keeps you coming back to work? In today's episode, we're talking about why we continue to be engineers.

In today's episode, we're continuing the conversation from our last episode and talking about what you can do once you admit that you don't know an answer to a question as a developer.

How will you handle the pressure of not knowing something?

Your actions and beliefs have a strong relation to each other. In today's episode, we're talking about how beliefs are formed.

Today, we're answering a listener question from Saul: How do you communicate a technical solution to a non-technical team member? Specifically, when that team member needs to be involved in making a decision that has technical implications?

When you are solving difficult problems, the questions you ask can help determine the path you go down to solve those problems.

At the youngest stage of your career you are most likely to quit. In today's episode, we're providing encouragement to those new developers for when the career decision gets tough.

What does it take to change your mind? Most of us haven't thought about that before and often times, it's hard to remember the last time we changed a belief or significant behavior.

How important is learning in your career? In today's episode, we're talking about the importance of both learning and play in the development of your career.

What are you willing to give up for your goals?

What does it mean when we use the term "balance"? In today's episode, we're talking about balance as it relates to decision making.

What is a useful default and when can they lead you astray?

One of the most frustrating things developers can face is writing a bunch of code, working hard on features and then waiting around for PR reviews. In today's episode, we're talking about how you can submit PRs better so reviews go quickly and smoothly.

What does it mean to collaborate as an engineer with other engineers? In today's episode, we're talking about the pull request process and the lack of attention it seems to get from engineers.

How does our brain perceive code in our environment and how does our mind make meaning out of our code?