4 ms·

> It is rather hypocritical to put someone down for lacking knowledge; doing so implies that you are judging them as lacking knowledge. You end up doing the exa

> It is rather hypocritical to put someone down for lacking knowledge; doing so implies that you are judging them as lacking knowledge. You end up doing the exact same thing. I have never seen this done in a way that doesn't backfire. No, it's not. OP doesn't put anyone down because he doesn't communicate his attitude towards the other person. When someone tells you "Wow, you really don't know what AABB stands for? How did you pass the interview? It's like DUUH, basic knowledge." with a smug or contempt face, he's putting you down. I've met people like this and they were very very hard to work with. Other remarks I've heard are "How the fk should I know, ask the idiot who implemented that piece of shit, I would've made it so it didn't have <random bug>", or "A bunch of losers who can't code without memory leaks decided smart pointers were a good idea, so now everything is slow". I can safely say, without a doubt, these people had the worst effect on me. I avoid them at any cost. It's not my place, nor my responsibility to suffer their attitudes or help them grow out of it. I'm not their manager and I'm not their parent. They're toxic and they consume my energy and self confidence. On the other hand, when someone counters someone else's bold claims of confidence or idiotic remarks with a puzzled look like "I'm wondering if you really know what you're talking about", he's not putting the other person down.

monk_e_boy 9y ago
I worked with a guy who thought all my code was shite. Now. I'm pretty tolerant. So I did what anyone in my situation would do. I installed a debugger and stepped through his code until I found some pretty glaring security flaws (escaping POST input should be pretty high on your priority list) and fixed them for him. Quietly. I explained what the problem was and why I fixed it. So I thought we were on the same team... but no. He insisted that I was incompetent. It took me a couple of days to think of something and then to implement it. I took some of his code, renamed a couple of variables and then pretended it was mine and asked him for his opinion. He emailed me back telling me exactly how shit it was and how I was beyond help as a coder. I took this evidence to his manager. The three of us sat down and I showed the code I wrote. My boss explained how it was wrong, the bugs, the mistakes. He went to town. Then I did my pathetic grand reveal. Yeah. It's your code, cut and paste from the codebase. I changed these variable names (HeLovedCamelCase i_prefer_underscores) could you accept that you have a problem with me, not with my code. This is simply a vendetta against me ... respond now please. The look on his face. He didn't work there the next day. Although there was a big hole in the wall where his fist entered and exited. The business didn't exist the next month. Turns out that someone who would employ someone like that isn't the best person to run a business. Life is full of surprises. Or lessons. Or something. If you haven't watched the detectorists. You should. It's the most beautiful nerdy show about something that isn't coding. https://www.youtube.com/watch?v=NgN7z0SD8v8 https://www.youtube.com/watch?v=NgN7z0SD8v8 https://www.youtube.com/watch?v=hwWv6UphTWM https://www.youtube.com/watch?v=hwWv6UphTWM
- monk_e_boy 9y ago
  Newcomers to the show will not only be treated to the finest, most beautifully understated sitcom of recent years, but also to the best depiction of male friendship anywhere in contemporary popular culture.

monk_e_boy 9y ago

I worked with a guy who thought all my code was shite. Now. I'm pretty tolerant. So I did what anyone in my situation would do. I installed a debugger and stepped through his code until I found some pretty glaring security flaws (escaping POST input should be pretty high on your priority list) and fixed them for him. Quietly. I explained what the problem was and why I fixed it. So I thought we were on the same team... but no. He insisted that I was incompetent. It took me a couple of days to think of something and then to implement it. I took some of his code, renamed a couple of variables and then pretended it was mine and asked him for his opinion. He emailed me back telling me exactly how shit it was and how I was beyond help as a coder. I took this evidence to his manager. The three of us sat down and I showed the code I wrote. My boss explained how it was wrong, the bugs, the mistakes. He went to town. Then I did my pathetic grand reveal. Yeah. It's your code, cut and paste from the codebase. I changed these variable names (HeLovedCamelCase i_prefer_underscores) could you accept that you have a problem with me, not with my code. This is simply a vendetta against me ... respond now please. The look on his face. He didn't work there the next day. Although there was a big hole in the wall where his fist entered and exited. The business didn't exist the next month. Turns out that someone who would employ someone like that isn't the best person to run a business. Life is full of surprises. Or lessons. Or something. If you haven't watched the detectorists. You should. It's the most beautiful nerdy show about something that isn't coding. https://www.youtube.com/watch?v=NgN7z0SD8v8 https://www.youtube.com/watch?v=NgN7z0SD8v8 https://www.youtube.com/watch?v=hwWv6UphTWM https://www.youtube.com/watch?v=hwWv6UphTWM

monk_e_boy 9y ago
Newcomers to the show will not only be treated to the finest, most beautifully understated sitcom of recent years, but also to the best depiction of male friendship anywhere in contemporary popular culture.