Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

22 insults no developer wants to hear

Peter Wayner | April 12, 2016
Flame wars in the bug tracker might be exactly the right (harsh) feedback your code needs

“No-op”

Someone who does nothing is a no-op, in reference to a blank binary instruction that flows through the CPU without changing anything. No-ops pad the instruction stream and help with debugging. Some processors use no-op codes with clever representations in hexadecimal. (See “deadbeef.”)

“Randomness”

Some of the cleverest algorithms rely on a steady stream of completely random numbers to find solutions -- some, that is, but not all. In fact, most don't. You can see how those perturbed by perturbations in your code might label it as such. You certainly don’t want your emails, memos, or documentation to be seen as random tacking in hopes of hitting on something important. (Antonym: knowledgeable.)

[Nothing]

The only thing worse than being insulted is being ignored.

 

Previous Page  1  2  3  4  5 

Sign up for CIO Asia eNewsletters.