3 ms·
The comment was about code working when you first run it--not exactly where input outside your control comes in. Also, you'd be surprised how much types can cat
by ahmedalsudani 8y ago
The comment was about code working when you first run it--not exactly where input outside your control comes in. Also, you'd be surprised how much types can catch, but feel free to completely ignore my opinion if that suits you ¯\_(ツ)_/¯
- revvx 8y agoIn my experience, a sufficiently rich type system is extremely similar to TDD in this regard. Both give you super fast feedback and a lot of issues can be solved before you finally launch your software for the first time. But neither will save you from bad design or misunderstanding your requirements.
- ahmedalsudani 8y ago+1. I think that's exactly the right way to think about types. They're like integration tests you pay for with some upfront thought about your design (and fighting type system complaints).