21st century calling

Why are you still coding in unsafe, primitive languages such as C and C++, both are more than 30-40 years old?
There is like zero type safety or even guarantees it works right after compiling. You could be corrupting your memory right and left and never know that as long as it compiles.

>>24
Bullshit. It's just that in your company, buggy and error-prone code is considered okay because you're so AGILE and TEST-DRIVEN. Programmers who care about getting stuff right actually need to enforce invariants at various interfaces, and contracts are one of the ways to do it.