<p><span class="h-card" translate="no"><a href="https://mastodon.social/@tintvrtkovic" class="u-url mention">@<span>tintvrtkovic</span></a></span> <span class="h-card" translate="no"><a href="https://floss.social/@gwidion" class="u-url mention">@<span>gwidion</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@ancoghlan" class="u-url mention">@<span>ancoghlan</span></a></span> Ignoring the implementation language, I find that well-typed code is done so primarily within the domain of the problem being solved. That is, the types come naturally from the problem. </p><p>This is opposed to fiddling around with code that's operating at a lower "Pythonic" level. For example, making a data-structure "list-like" is often more of an incidental implementation detail that might not be that important in the big picture.</p>
