My experience is that while I do things when developing that are basically typos and would be caught by a compiler, those errors are nearly always trivial and loud, and are generally caught and fixed before anybody else sees them.

The bugs that make it to production, in my experience, tend to be faulty logic or bad assumptions and would not be caught by a compiler.

I'm wondering how universal my experience is…

3
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Mark IJbema

@noelrap having worked with both ruby and c# I'd say quite a few. But not which are caught by just turning types on. You need to lean into it and really use them.

My easiest example is have a type for each id (like user id, so that you cannot compare user_id with todo_id).

I'm not sure how hard this would be with rails though

1
1y
Caleb Hearth :d6:

@noelrap I see undefined method for nil and missing key errors all the time

1
1y
Brian Marick

@noelrap Bug classification studies used to be popular (funded by the military, mostly) and they generally found the most *costly* bugs in production were of your “faulty logic or bad assumptions” sort. (Because of the terminology of the day, these were frequently called “requirements errors” or “specification errors”.) I did a survey of such papers when I was doing my MS in early ‘80s.)

0
1y
Replies