Look, I have a lot of affection for dynamically typed languages. I cut my teeth on Ruby, I love Emacs Lisp, and I lead a popular dynamically-typed language. But look: if you don't want to write type annotations, you gotta write documentation. There has to be some way for someone reading the code to figure out "what is the shape of this object and what assumptions can I safely make about it" without reading the entire fucking application.
- they/he/it/(something funny)
- sarpnt.ficial.net/
trust me i do programming and music i just don't make great posts about it or complete most of it
bad git
github.com/sarpntYou must log in to comment.
in reply to @nex3's post:
here's the thing about dynamically typed languages-- they're very elegant, which is an engineering term for when something is fragile.
my last job was awful about this. no type annotations and ALSO no comments. made it nearly impossible to dive into a random file as you'd end up reading all of the surrounding functions and files in the call stack just to know what was happening.