Hey readers! Two quick things today.
1. Reader Survey
I’ve been at this newsletter game a little over a month now, and would like some feedback on how I’m doing so I can create a *extremely marketing voice* Great Customer Experience.
I’ve been getting some great emails, and keep those coming, but please take this 8-question 5-minute survey so I can get a better sense for:
The correct frequency/delivery of the newsletter
A very high-level overview of audience
Your direct feedback of what you like/don’t like about it
Here it is: https://forms.gle/jJG9ax6awZxtw6J69
The Google form doesn’t collect any personal details (i.e. email, etc.) and I’ve tried to keep it as sparse as possible. It should take no longer than five minutes, ten if you want to write a really long note.
2. New Blog Post: Type Hints in Python
I’ve finally had time to some real technical blogging, and done a write-up/exploration of type hints in Python, a big language feature that’s starting to be much more widely adopted.
Here’s the blurb:
Since the release of Python’s type hints in 2014, people have been working on adopting them into their codebase. We’re now at a point where I’d gamely estimate that about 20-30% of Python 3 codebases are using hints. Over the past year, I’ve been seeing them pop up in more and more books and tutorials.
However, there’s still a lot of confusion around what they are (and what they’re even called - are they hints or annotations? For the sake of this article, I’ll call them hints), and how they can benefit your code base.
When I started to investigate and weigh whether type hints made sense for me to use, I became super confused. So, like I usually do with things I don’t understand, I decided to dig in further, and am hopeful that this post will be just as helpful for others.
And here’s the post.