If he had time to consistently rewrite all of the code to a better standard that the entire team produced while also covering what he him...
If he had time to consistently rewrite all of the code to a better standard that the entire team produced while also covering what he himself was responsible for, he was probably working in hell. That shouldn't be possible unless the code was generally pretty bad. > Also, during planning and architecture discussions he wouldn't say a word, just go and rewrite everything we discussed. Wild-assed speculation here, but if he didn't think that the rest of the team would listen to his expertise (which you admit was strictly dominant over the rest of the team) and didn't think they were qualified to argue with them about it or teachable enough to learn from him - that could lead to a strategy of silence and just fixing it after everybody else was done. There are some things that one just can't argue about with some people without it being a complete waste of time. If he was basically running the show and ultimately responsible for the high quality of the product, IMO he probably should have been tested as the manager of the team. Being able to dictate the standards of the final product would remove the need to argue, and require the team to learn what he wanted them to learn. > I left for another team after about 3 months of this. If you were consistently wrong in your disagreements with the best member of the team and instead of using that as motivation to improve, it simply resulted in (traditional anti-egghead/smartypants) rage at the person who had the nerve to be better than you at everything, it was probably better for everyone.
Posted by pessimizer on Jun 24, 2015, 2:51 PM
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.5,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?
If he had time to consistently rewrite all of the code to a better standard that the entire team produced while also covering what he him...
If he had time to consistently rewrite all of the code to a better standard that the entire team produced while also covering what he himself was responsible for, he was probably working in hell. That shouldn't be possible unless the code was generally pretty bad. > Also, during planning and architecture discussions he wouldn't say a word, just go and rewrite everything we discussed. Wild-assed speculation here, but if he didn't think that the rest of the team would listen to his expertise (which you admit was strictly dominant over the rest of the team) and didn't think they were qualified to argue with them about it or teachable enough to learn from him - that could lead to a strategy of silence and just fixing it after everybody else was done. There are some things that one just can't argue about with some people without it being a complete waste of time. If he was basically running the show and ultimately responsible for the high quality of the product, IMO he probably should have been tested as the manager of the team. Being able to dictate the standards of the final product would remove the need to argue, and require the team to learn what he wanted them to learn. > I left for another team after about 3 months of this. If you were consistently wrong in your disagreements with the best member of the team and instead of using that as motivation to improve, it simply resulted in (traditional anti-egghead/smartypants) rage at the person who had the nerve to be better than you at everything, it was probably better for everyone.
Comments (0)
No comments yet. Start the discussion.