Skip to content
Two More Guidelines for Better Feedback Loops (Part Three) episode artwork

Dec 13, 2019 19 min

Two More Guidelines for Better Feedback Loops (Part Three)

from Developer Tea Hosted by Spec

Developers tend to create process for themselves and a shared process with a team, but what defines whether or not a process is useful? In today's episode, we're talking about feedback loop processes and the reality of their usefulness. 🙏Thanks to our Sponsor: GiveWell Giving is hard. When you donate, how do you know what a charity can actually accomplish with your money? Givewell, is solving that problem by connecting your money with charities that will see the direct impact of your dollars spent. Visit GiveWell.org/DeveloperTea to find out about effective charities and get your donation matched up to $1,000. 🧡 Leave a Review If you're enjoying the show and want to support the content head over to iTunes and leave a review! It helps other developers discover the show and keep us focused on what matters to you. 🍵 Subscribe to the Tea Break Challenge This is a daily challenge designed help you become more self-aware and be a better developer so you can have a positive impact on the people around you. Check it out and give it a try at https://www.teabreakchallenge.com/.

Episode details come from the podcast's RSS feed.

Embed this episode

Are your processes useful? In the last couple of episodes, we've been talking about feedback loops and in today's episode we're continuing that discussion and zooming out to make sure our feedback loops are proving useful.

Ready to play

Two More Guidelines for Better Feedback Loops (Part Three)

0:00 19:33

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of Developer Tea?

This episode is 19 minutes long.

When was this Developer Tea episode published?

This episode was published on December 13, 2019.

Can I download this Developer Tea episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.