Closed vikrrrr closed 6 years ago
Uh that's beautiful! Just don't know how to go about later code changes. What I want to avoid is that people get confused when they check the code and it doesn't match with what I showed in the episode. Hum... maybe an "errata" folder or an "improvements" section in the show notes might be nice.
Come to think of it, how about a "Discussion" section where we collect those best practices and evolve the code over time. The first version of the code would always be the first link in this section and after that, we would chronologically add improvements like yours. What do you think?
Yea, we could document every change done between original and current code on a per-episode basis, with an explanation as to why each change was made and a link to the file on a specific commit.
Probably put it in the README of each episode. This also means adding an Improvements
section into SHOW_NOTES.md.
As discussed, updated the show notes and added an "errata" section. Thanks for your contribution @vikrrrr! ⭐️
No. I will always point to episode 8. Forever. ...you're right of course. 😆 Nice catch! Fixed.
Use
Option::map
instead of a match expression in theparse_month
function. Makes it more readable.Love your show BTW! :)