
Giving someone a broad software problem is a little like asking them to plant a tree. In today's episode, we talk about how different mental effects can cause variance in decision-making for complex and compound decisions. Thanks to today's sponsor: Sentry Sentry tells you about errors in your code before your customers have a chance to encounter them. Not only do we tell you about them, we also give you all the details you’ll need to be able to fix them. You’ll see exactly how many users have been impacted by a bug, the stack trace, the commit that the error was released as part of, the engineer who wrote the line of code that is currently busted, and a lot more. Give it a try for yourself at Sentry.io Get in touch If you have questions about today's episode, want to start a conversation about today's topic or just want to let us know if you found this episode valuable I encourage you to join the conversation or start your own on our community platform Spectrum.chat/specfm/developer-tea 🧡 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/
اگر پخش یا دانلود این قسمت خراب است، به مدیر اطلاع دهید.
In this special series on Developer Tea we're talking about the different ways that software information flows, and how that informs our decisions when constructing our software Today's Episode is Brought To you by:…
The things that seem to cause procrastination is value. Either in the outcome of the work or in the future state getting in the way of the tasks at hand. That's what we're talking about in today's episode of Developer…
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 going to talk about recognizing our own faults when we look back on a…
We write tests for our code because it gives us another angle to understand the code and ends up being more efficient for most types of projects. It also has an effect on the way we actually write the software, but…
In today's episode, we're talking about a different kind of change. Instead of updating beliefs incrementally we're going to look at ways to approach change at a scaled level both in your work and in your life. Today's…