What do you want? What would you like to accomplish in the next year? These are difficult questions to answer, and in truth, they are too simple. In today's episode of Developer Tea, we dig into questions typically asked of developers during reviews, and how to make broad questions more specific and easier to answer.

Complexity is often given a bad rap as an engineer. We're always trying to reduce complexity. In today's episode, we're viewing complexity as an expendable resource that helps us make better decisions.

What is your relationship with mistakes? The thing about mistakes is that they will always happen. In today's episode, we're talking about acceptance of mistakes and how we can behave to deal with mistakes better.

Where do you feel most limited? In today's episode of Developer Tea, we're talking about cognitive distortions and the effects these make on how we make decisions.

In today's episode, we sat down with Nicole Archambault to talk about problem solving and the steps to take when solving a coding problem. In this part 2 of the interview, we dig a little deeper into the steps of code problem solving with examples and best practices.

In today's episode, we sat down with Nicole Archambault to talk about problem solving and the steps to take when solving a coding problem. In this part 1 of our interview with Nicole, we dive into her background in tech and go over the first steps to problem solving.

There's a lot of discussion around what you should bring with you when you begin a career as an engineer, but rarely do people talk about what to leave behind. In today's episode, we're going to talk about 4 things you should leave behind when you choose to be a developer.

What happens next? This is a question that developers should be asking more frequently. If you're trying to develop a stronger sense of intuition, this episode is for you.

Humans are no strangers to being beginners. In today's episode of Developer Tea we're talking about the unique advantages we have in beginning something and how to take advantage of that opportunity.

In today's episode of Developer Tea, we're talking about how we operate as developers. How do you determine what tools or rules you apply to problems you're solving as a developer?

What exactly is a label? What is a name? In today's episode of Developer Tea, we're talking about the impact of naming or labeling our work as developers. We'll talk about why it is important to label well and why use a well through naming structure makes all the difference in our work.

What does it mean to "use" your brain, and how is that different than simply thinking? As developers we engage in thinking all the time, but how can we use our brains better when solving problems?

In today's interview with Aaron Upright, cofounder of Zenhub, we talk about being forgiving to ourselves as developers.

Aaron Upright is a cofounder of Zenhub and in this part 1 of the interview with Aaron we talk about his background, how he got going with Zenhub and what he's working on today.

We've been told all our lives that we're unique. In today's episode of Developer Tea, we're talking about the difference between being unique and being an exception.

One of the most important things you'll do as an engineer is participate in feedback sessions. In good feedback sessions things look very different than they do in bad feedback sessions. In today's episode of Developer Tea, we're talking about feedback and how to build a good feedback mechanism.

If you could pause everything right now, what would you feel the need to do?

Breaking big problems down into smaller, easier to tackle problems and in today's episode we talk about exactly why breaking down problems into small forms is effective.

What is the story of your code?

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?