3 ms·
Hypothetically, given developer tooling, which would you prefer to make sure your code is as correct and robust as possible? 1. Language with strong type featu
by ActorNightly 4y ago
Hypothetically, given developer tooling, which would you prefer to make sure your code is as correct and robust as possible?
1. Language with strong type features.
2. Testing packages that automatically include fuzz tests and null tests to ensure correct behavior?
Granted most of my experience in production level software involves backend services, which essentially means json transformations 95% of the time, Ive rarely ever seen an error that results in the service saying everything is ok but returning a wrong result. For example in the case of null fields, something downstream fails and errors out - this is easily caught by testing.
- Gunax 4y agoWell I would prefer to have both. I don't think we need to choose. However, I think tests are high-maintenance. Often they consume the same amount of time to write as the actual business code. I don't know how automatic null checking tests would work. Wouldn't you need to specify what happens if a null is input? In contrast, I find the cost if typing very low for the value it delivers. Unless the code is very ephemeral (like a one off script) then I highly prefer typing.