-
I think since the list is growing long, I think we need categorization for these and a short description on what these podcasts are about. Also mentioning the frequency of episodes. I will start with podcasts I know about. Need help from you guys to categorize other podcasts. Thanks. Please feel free to raise a PR.
-
inactive-user
edited
5 months ago
|
link
| on:
Collection of Important Podcasts for Software engineers
Would you consider breaking the podcasts down into categories, or expanding on what areas, topics, and expertise each offers? Otherwise it’s just a big list of sometimes descriptive names.
Edit: which I would contribute to, but I don’t listen to tech podcasts at this point, so at best I could just copy/paste whatever their website says. If you’re a long time listener, your summary is much more valuable, and really the core value here in my approximatarion.
-
-
BTW I suggest that you post the link to your github repo rather than referencing it in the text.
Also, I submitted a PR with my favorites :)
-
-
-
-
@rshetty is unable to edit it because the story’s been posted for more than six hours. I can’t edit the url because it never had one. That’s an odd limitation that might just be an oversight of a corner case, so I’m going to think on it before maybe I reverse it.
And, yeah, mentioning me or messaging me here or on IRC is the way to get attention to things that need tweaking.
And Why Are Computers, though inactive, is good enough that I’d add it to the list. :)
-
Although I don’t usually do podcasts, a description like this is a sure way to convince me to try one:
“Chris Patuzzo tells the story of creating the Sentient programming language, with diversions into NAND to Tetris, self-enumerating pangrams, the boolean satisfiability problem, and The Witness.”
-
-
-
-
-
nickpsecurity
5 months ago
|
link
| on:
Common patterns for building resiliency in distributed systems at Scale
A lot of that looks like what’s in this book by Nygard. Anyone wanting to learn about that stuff will find in there both patterns to use and reasons why they should strongly consider using them.
-
-
Agreed. I skimmed a lot of IT books but it was one of few I actually bought. Great writing on how to apply the patterns, too.
-
-
-
I’m not a fan. I remember it as being what felt like “common sense” combined with some ideas that I think are bad. Of course, common sense means “lessons that took me years to learn”. No book is all good advice. Part of the learning process is implementing ideas that aren’t yours and learning when they are applicable and when they aren’t.
My biggest problem with “Release It!” was it felt more like “all good engineers do X”. Best practices never are. They are good ideas in a certain context. Sadly, most tech thought leaders teach them as absolutes.
-
It was kind of like a cookbook. Context is also important. He usually said what they were good for doing, though, along with examples of why. I figured people could make contextual decisions that way.
-
-
-
Finished on Emotional Intelligence - By Daniel Goleman A must read.
Into thin Air - By Jon Krakauer Book is absolutely amazing
Playing around with Elixir on Exercism.io: https://exercism.io/tracks/elixir