13 ms·
Believe it or not but good typed languages with a lot of compile time checks are probably one of the main reasons why TDD is not that big. Sure, these won't cat
by jdmoreira 6y ago
Believe it or not but good typed languages with a lot of compile time checks are probably one of the main reasons why TDD is not that big.
Sure, these won't catch logic errors but most developers don't write that much heavy logic code anyway. And the senior developers are capable of writing mostly straight forward code that it’s easy to debug.
- JMTQp8lwXL 6y agoType-checking, while helpful, can't always catch logical programming errors that result in user-facing bugs. We would have observed a marked increase in software quality with the advent of typed languages, but we haven't. Quality depends on more than just a typed language, whether that be unit tests, integration tests, etc.
- jdmoreira 6y agoI strongly disagree having years of experience in both Objective-C and Swift codebases / products
- JMTQp8lwXL 6y agoDisagree on general software quality? I've been an iOS user for about a decade now. Seen a couple of 'bad' (extremely buggy) apps here and there, but the quality seems relatively constant over time (possible sample bias).
- jdmoreira 6y agoGreat product teams will build great products independently of Objective-C or Swift but you will need much less resources to deliver on the same quality using swift and modern frontend architectures. I would also doubt the majority of apps in the Appstore today are using swift at least in the sense that I mean it. It’s not enough to use swift you actually need to know how to model your problem well using its type system and that takes experience. A lot of devs simply focus in solving narrow problems without giving much thought to how much more strict they can be with the language.
- bufordtwain 6y agoIf you have a logic error what's to prevent you from making the same error when writing the test?