I am offended by coworkers who submit incompletely considered, visibly LLM generated code.
These coworkers are dragging my team down.
180 karma · joined December 6, 2024
I am offended by coworkers who submit incompletely considered, visibly LLM generated code.
These coworkers are dragging my team down.
> 83.3% of LLM users were unable to quote even one sentence from the essay they had just written.
> In contrast, 88.9% of Search and Brain-only users could quote accurately.
> 0% of LLM users could produce a correct quote, while most Brain-only and Search users could.
Reminds me of my coworkers who have literally no idea what Chat GPT put into their PR from last week.
I mean it's even further than willful ignorance. It's delight in one's own ignorance.
To anyone reading, if you work on LLM software, I hope that your business fails.
my coworkers are increasingly ignorant about the software products they work on.
LLM-informed software development is organizationally poisonous.
Businesses selling LLM coding tools occupy the same place in my mind as drug dealers.
why are you looking for a shortcut? just do the work.
along with improving my skills in vim, this approach has made me significantly more productive and has made my code much simpler compared to when i was using LLM code generation tools.
there is no shortcut around hard work.
there is no shortcut to thoroughly interrogating the constraints of the software problem at hand.
developers who rely on LLM code generation are poor coworkers because they don't understand what they've written and why they've written it.
IMO, the authors and evangelists of Git are essentially correct when they argue about its power.
However, I think that it's extremely difficult to gain practical experience with using Git in a high-powered, high-agency way, mostly because there are a lot of abstract concepts at play and there is no easily accessible place where these concepts can be "discovered".
Basically, Git is as good as it's cracked up to be, but only if you're an expert.
If you're interested in becoming a Git expert, I cannot recommend Emacs Magit strongly enough.
If not, I think Jujutsu could be an quicker road to a high-agency version control workflow. It's at least worth considering. I feel confident that Jujutsu can succeed, in particular because of Git's harsh difficulty curve.
I'm having a hard time wrapping my mind around what specific details would cause me to choose Jujutsu over Git, in particular because of Git's industry standard status.
I think this is a very interesting concept, but I think it could go farther with some more targeted marketing along these lines. Of course, if Git power users are not Jujutsu's intended audience, then this comment may be irrelvant.
I think one of Git's great weaknesses is its unfriendliness to newcomers (jargon, deep features, lack of discoverability, lack of accessible GUI frontends), so there's probably a lot of potential for a VC solution that is easier for a newcomer to jump into.
Are there specific advantages to using Jujutsu over Emacs Magit?
All other Git UIs I've used have been severely lacking, but Magit has made me significantly more productive with Git, and has convinced me of the "magic of git".
Is Jujutsu interested in competing with this experience? Or is it intended as an alternative to the (to be clear, extremely poor) git user experiences outside of Emacs?
musk is a kleptocrat/plutocrat who did the nazi salute for the purposes of generating controversy. it seems obvious to me that he's more interested in securing the success of his ventures than anything resembling 20th century fascism.
there are a massive number of subjects which cannot be spoken about on social media without risking massive deboosting and the blacklisting of your accounts.
this censorship is directed by "former" CIA agents working at all major American social media companies. In other words, this is direct government censorship of private citizens' speech.