Developer Tea

Developer Tea exists to help driven developers connect to their ultimate purpose and excel at their

Episodes

Total: 602

Changing our minds on a belief or issue that we stand by is not easy and as humans but is required o

🎟Upcoming EventsWanna get your hands on the hottest #JavaScript tech?Reserve a spot at #JSNationLiv

In today's episode, we're talking about goals and what we tend to give up in order to reach those go

In today's episode, we're talking about balance as it relates to decision making. We'll dig into two

A useful default is an action you can take on a regular basis that you expect to provide some level

How can you write a pull request that's productive? in today's episode, we're talking about how to b

What does it mean to collaborate as an engineer with other engineers? In today's episode, we're talk

How do our brains and our minds perceive code? In today's episode, we're talking about what code is

When you think correlation and causation you might think of graphs and research. As one data point c

What effect does your value system have on your personal and professional growth? In today's episode

Productive Self-Sabotage

2020/5/8

We often don't know about all of the failures that exist, but what causes failure? The path to succe

In today's episode, we're doing a visualization exercise. Grab a piece of paper and pen or pencil an

The average engineer hears this over and over, "question your assumptions." In today's epi

When do you walk away from a problem to find the solution? In today's episode of Developer Tea, we'r

What are your default problem solving strategies? In today's episode of Developer Tea, we're talking

What makes up the orders that we follow? In today's episode, we're talking about truths about the wo

In today's episode, we conclude the conversation with Dan Heath, author of a new book , Upstream. In

In today's episode, we sit down with Dan Heath, author of a new book , Upstream. In this part 1 of t

Protecting Uncertainty

2020/4/20

At some point our knowledge runs out, but even more perplexing is the ability to look forward in tim

If you had to define learning to an engineer, you'd probably mention some type of fact memorization