ABOUT THIS EPISODE
In our first episode, we give an overview of what we are talking about, when we say, that code is communication. It’s neither detailed, nor even complete, but touches on the most important aspects of communicating through code.
English
United States
TRANSCRIPT 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
SEARCH PAST EPISODES
Search past episodes of Code is Communication.
OTHER EPISODES IN THIS PODCAST
In order to communicate efficiently through your code, you have to know your language, it’s features, and idioms.
This time we exploring types as means of communication.
If you’re getting value from this podcast and would like to support it, you can do that by becoming a patreon.
It helps us make time for more of these conversations.
Naming things is one of the most difficult things in software development. In this episode we discuss traps, antipatterns, and guidelines.
You might notice, that we are getting more relaxed on the microphone. We hope, you have just as much fun, as we had.
This time we talk about design patterns in the context of communication through code. And about a lot of other things. This reflects very well, what well applied design patterns are: something, that can ease your cognitive load, without being noticed much.
To compensate for the audio mishap on my …
Disclaimer: The podcast and artwork embedded on this page are from Erik Larsson & Christof Donat, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
EDIT
Thank you for helping to keep the podcast database up to date.
