News for hackers. Stuff that matters.

A comment on Things we learned about LLMs in 2024. Parent comment

Re:Things we learned about LLMs in 2024 by dartos on Tuesday December 31, 2024 @06:49PM (#42562757)
Right, but using git is a team wide thing.

I can’t use perforce while my company is on git.

But if I do or do not use an LLM to assist me while coding, my team is unaffected.

If someone liked jetbrains, but your team used neovim, would you force them to use neovim?

[ Parent | on HN ]
Re:Things we learned about LLMs in 2024 by Kwpolska on Wednesday January 01, 2025 @03:42AM (#42564775)
Editors may also be a team decision in some places. Some teams are using features unique to one IDE, for example.
[ Parent | on HN ]
Re:Things we learned about LLMs in 2024 by chikere232 on Wednesday January 01, 2025 @04:30AM (#42564976)
it can be a team decision, but it's a bad one
[ Parent | on HN ]
Re:Things we learned about LLMs in 2024 by dartos on Wednesday January 01, 2025 @09:41AM (#42566252)
Then that tooling is required, like visual studio is a common one I know about in windows land.

Though nobody should care if I edited my text files with neovim as long as I still used the same toolchain as everyone else.

[ Parent | on HN ]