> You will send out some C signals. That’s inevitable. We all did. Never, never send out the same C signal twice. And make sure the balance of the signals are that you are a B.
This bit is important. It's not great if a new hire nukes production, but it doesn't preclude them from being a B or A.
Additionally being considered a C isn't necessarily a blame game. If an employee nukes production multiple times, they may not be in the right headspace to work at that company, through no fault of their own.
I've actually run into this in the wild, with regards to sales forecasting. A program we were using returned zero if the error bars on a forecast were over 100%. For example, selling somewhere between 1 and 7 units, but averaging 3.
Returning 3 was "wrong", but infinitely more correct than retuning 0.
I occasionally put on a (human-made) podcast for the word-sounds rather than the content. I can imagine others do the same without caring whether it is human-made.
Once you get a byte-by-byte duplicate, you can start refactoring into idiomatic Rust. Convert pointers to references, rip out unsafe blocks, and let Clippy go ham.
This bit is important. It's not great if a new hire nukes production, but it doesn't preclude them from being a B or A.
Additionally being considered a C isn't necessarily a blame game. If an employee nukes production multiple times, they may not be in the right headspace to work at that company, through no fault of their own.