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?

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?