How We Construct Software, Part 4b: Code and Communication

In today's episode, we dive into the rest of the communication model we started discussing in the previous episode in this series. 🙏 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/

There are no comments yet.

Please log in to write the first comment.