
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! Today's Episode is Brought To you by: Linode Instantly deploy and manage an SSD server in the Linode Cloud. Get a server running in seconds with your choice of Linux distro, resources, and node location. Developer Tea listeners can get a $20 credit and try it out for free when you visit: linode.com/developertea and use promo code: developertea2019 P.s. They're also hiring! Visit https://www.linode.com/careers to see what careers are available to you. 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 today's episode, we're going to talk a little bit about belief. Often this word is used and abused as something more than it is. In today's episode we're going to reinvigorate your appreciation for the word blief and…
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…