My CS101 prof would give 50-100 line blocks of code, and hidden in them somewhere would be something like:

    if(condition); {
        some stuff
    }

Note the semicolon after the if-statement.

The tests became games of "find the semicolon or = in place of ==". Ugh.

A lot of these are cases where I've seen actual bugs. Popular ones are >= 0 checks, dumb assumptions about overflows and null derefs, and the always popular "use an int when it should be size_t".

What is your main programming language; in which you do most of the work?

Compilers are increasingly optimizing out UB, recently fixed a problem where `std::unique_lock` was optimized as it was referenced from an `std::thread` defined at the top of the class. The future is now!

only useless if you never make a mistake ever. This shows what you should be vigilant for (alternatively , an argument for using a language with more checks)

As someone on HN once said (in jest), it's easy to write bug-free C, you just need to never make a mistake ever and spend a million hours auditing it.