If I had to push a fix to prod ASAP, I'd personally rather it take more time but go in production safely. Especially in a case like that with not enough testing

If I had to push a fix to prod ASAP, I'd personally rather it take more time but go in production safely. Especially in a case like that with not enough testing to really be sure if everything's okay or not, the stricter the compiler the better. And if I had to train employees, I'd rather them fight the compiler more in the beginning but write better code later, than be able to write code quickly but make a horrible mess. I've seen the "fast and loose" approach fail miserably and turn into a nightmare enough times that I now advocate for strict languages whenever I have a say in things. (which is why, with the state of programming languages right now, I will almost never suggest zig or go for a project). I think developers in generals should trust themselves less, to be honest. I feel like it would avoid a lot of issues down the road.