We all have different experiences coming into development, and today we talk with Ali Spittel, a software engineer at Dev.to, director at Women Who Code - DC and lead instructor at General Assembly.

Do you trust yourself to know what you want?

In today's episode we're talking about two habits that successful software engineers employ when facing a problem.

What do you do as a developer?

In today's episode, we continue the discussion with Bryan Helmig, CTO of Zapier

In today's episode, we talk with CTO and co-founder of Zapier, Bryan Helmig about the different challenges he faced when starting Zapier and the challenges he's facing today.

In today's episode, we're talking about the habits of successful engineers.

In today's episode, we're going to talk about the different stages of stress and how we can better manage our influence in the job when we're experiencing a stressful situation.

In today's episode, we're talking about solving problems by subtraction vs. additive solutions.

One of the most valuable things you've got is the first part of your working day. In today's episode, we're talking about the best use of those first hours in your day.

One of the barriers to connecting with your career purpose is fear. In today's episode, we're going to talk about working toward your goals knowing that fear will be there with you.

In today's episode, we dive into the rest of the communication model we started discussing in the previous episode in this series.

In part four of our discussion on how we construct software, we're discussing a theory of communication, and how it applies to code. This is a two-part episode (A and B) - subscribe so you don't miss the second half!

In today's episode, we discuss factors that lead to decision variance when constructing software.

In today's episode, we're going to talk a little bit about belief.

In this special series on Developer Tea we're talking about the different ways that software information flows.

In today's episode, we're talking about specific reasons why we may be running into procrastination in our jobs.

We recommend structured retrospectives. Identify things that went well and things that didn't go so well during a project or given week.

Today, we're talking about risk compensation.

Most of the changes you make as a developer are incremental. That's what we're talking about in today's episode.