3 ms·
I can see this being very useful in teams. Hell, its even useful for a single developer as a form of future documentation. I generally write code today and thin
by cdnsteve 11y ago
I can see this being very useful in teams. Hell, its even useful for a single developer as a form of future documentation. I generally write code today and think, when I read this in 6 months and have no memory, how can I help my future self? For new code bases I'll be adding this.
- zyxley 11y agoI've been very happy about more interpreted languages adding optional typing for exactly this kind of reason.
- jiaweihli 11y agoFor dynamically typed languages, using a popular type annotation syntax (e.g. rdoc for ruby, closure compiler for javascript) and an IDE (like Intellij) can give you 80% of the benefits of type safety by doing code inspection on-the-fly and warning you when it finds incorrect types. The main downside is no compiler safety net when you try to refactor code.
- pauleveritt 11y agoI'm the author of the article. When I gave a preview of this at the PyRVA meetup, I gave this exact illustration, even using "my future self". So...jinx. :)
- cdnsteve 11y agohaha maybe we're twins!