@noelrap I work with numbers a lot. In my experience, most bugs come from not dealing with nil as a possible value.

Another “issue” is dealing with nil values where it can’t logically be nil.

3
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Abdullah Esmail

@noelrap I feel like one of the mostly overlooked benefits of a type system is that it tells you where you’re doing extra work unnecessarily.

1
1y
Mark IJbema

@aesmail @noelrap Microsoft has retrofitted null-anotations to C# which one could gradually introduce. We implemented this on a codebase of a few hundred thousand lines and caught quite some bugs (though not very bad ones as the product was humming along on production -- but that might just be because bad ones were already fixed after production crashes)

1
1y
Noel Rappin

@aesmail nil is almost it's own category -- a lot of typed languages still let you have nil problems, and it's not actually that hard to mitigate them in Ruby.

0
1y
Replies