I am not sure I agree 100% with this.
I am not sure I agree 100% with this. If both people are working on a really hard problem and the argument is based on theory, then yes, you should be kind. But if a colleague routinely creates more work for you and he thinks he is a competent programmer when not, then being kind will only further stroke his ego. I am literally facing this at work. One of my colleague has an opinion on everything. Its quite frustrating because he is neither the most experienced person in the topic nor is he any good. I literally caught him using an if else statement for check whether a dictionary contained a key when one line would have done. Its programming 101, pick up a book and you will learn it in chapter 3. But he goes on saying he has 5 years in this industry... I am like okay bro. How he got a job is beyond me. In the end, kindness is a tool in EQ. You should use it when needed and be stern when another approach calls for it. Hiding your dissatisfaction just to be kind will do the company long-term dis-service. Especially to the code base.
Posted by 20andup on May 13, 2015, 2:11 AM
Tags
Related issues
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments
hackernews (Other)
The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
I am not sure I agree 100% with this.
I am not sure I agree 100% with this. If both people are working on a really hard problem and the argument is based on theory, then yes, you should be kind. But if a colleague routinely creates more work for you and he thinks he is a competent programmer when not, then being kind will only further stroke his ego. I am literally facing this at work. One of my colleague has an opinion on everything. Its quite frustrating because he is neither the most experienced person in the topic nor is he any good. I literally caught him using an if else statement for check whether a dictionary contained a key when one line would have done. Its programming 101, pick up a book and you will learn it in chapter 3. But he goes on saying he has 5 years in this industry... I am like okay bro. How he got a job is beyond me. In the end, kindness is a tool in EQ. You should use it when needed and be stern when another approach calls for it. Hiding your dissatisfaction just to be kind will do the company long-term dis-service. Especially to the code base.
Comments (0)
No comments yet. Start the discussion.