3 ms·
An engineer getting up to speed on a 10 year old web app that uses dynamic types will likely have a very different opinion. No types anywhere, so making a chan
by lurking_swe 1y ago
An engineer getting up to speed on a 10 year old web app that uses dynamic types will likely have a very different opinion.
No types anywhere, so making a change is SCARY! And all the original engineers have usually moved on. Fun times. Types are a form of forced documentation after all, and help catch an entire class of bugs. If you’re really lucky, the project has good unit tests.
I think dynamic typing is wonderful for making software quickly, and it can be a force multiplier for startups. I also enjoy it when creating small services or utilities. But for a large web app, you’ll pay a price eventually. Or more accurately…the poor engineer that inherits your code in 10 years will pay the price. God bless them if they try to do a medium sized refactor without types lol. I’ve been on both ends of the spectrum here.
Pros and cons. There’s _always_ a tradeoff for the business.
- rhubarbtree 1y agoI think you’re right. But most startups aren’t building for 10 years out. If you use a lot of typing, you’ll probably die way before then. But yeah if you’re building a code base for the long term then use types unless you’re disciplined enough to write comments and good code. As for refactoring, that is exactly what test suites are for.