3 ms·
You really shouldn't call people "fucking stupid" for making mistakes in code. They're clearly not stupid, they're writing complex computer code for a big proje
by flumbaps 13y ago
You really shouldn't call people "fucking stupid" for making mistakes in code. They're clearly not stupid, they're writing complex computer code for a big project. Calling them "fucking stupid" is as much a lie as throwing out empty compliments, and just as counter productive. Smart people don't need to be beaten into shape, just like they don't need to be mollycoddled. If you're being abusive in the workplace, it's because of your own emotional needs, not the people you're being abusive to.
If someone commits code that is fucking stupid then by all means call the code fucking stupid. But then actually take the time to identify the cause for the mistake. Is that programmer following best practises? Are they being careless? Are they working on something they don't have the expertise for? Are they spread too thin? If you identify the problem you can try to fix it. Instead of abuse, you should be giving clear and direct instructions on how to not make mistakes like that ever again. If you call someone "fucking stupid" then you incorrectly identify the problem and, moreover, you're being abusive, which can be very harmful.
- scotty79 13y agoWhen you do stupid thing do you carefully watch out to exclaim "I did a fucking stupid thing!" instead of "I am so fucking stupid!"? Calling someone stupid after he did something stupid is different than calling him that as a main point of his semiannual performance review.