Comment on blastQR: send files completely offline over QR codes. Up to 1.4 MB/s
You are viewing one comment and its replies. View all comments · View the comment above
You are viewing one comment and its replies. View all comments · View the comment above
Comments
Not using AI for writing code in late 2026 makes sense only for learning purposes. To not “vibecode” is unjustified self inflicted pain otherwise. Good use of AI with latest models generate better and more maintainable code. I do not see how that is unfortunate. Bad practices and old bad models were indeed an issue. Now things have changed.
Better and more maintainable is absolutely false!
We’ve been told to use AI at work. Most are using Claude but some are using other agents. Across the board the code these things shit out is an over engineered, unmaintainable mess! I’m not the only one on the team who thinks this either. We are starting to have conversations about appropriate use of AI and making sure to keep the code under control.
Same at my work. It spewing out junk is a sign of missing context. If you feed it good examples first of what you expect it to produce and make it keep documentation for the future whenever you notice it has made a mistake, you can get some really really good results, but you have to train it and treat it like an apprentice who would also make mistakes, otherwise you are completely correct, yes.
I use AI at work. The use of AI requires knowledge and projects structured around the use of AI. If you do it properly, AI code is much better (100% clean code architecture adherence, tdd with >90% coverage, deploy gates on quality and security, easy dependency upgrade). Since we started using AI properly our codebase quality skyrocketed. Less bugs, more features, less insecure code. You do not know how to use AI properly. That is fine, most don’t, we are discovering how to use a new tool that change every week now. That does not mean the problem is the tool.
‘Artificial Intelligence’ is a marketing label for a pseudoscience, and has been since the term was conjured in 1956.
LLMs are competency solvents and credibility chippers, and anyone who persists in labelling them as anything adjacent to intelligence must be quarantined from any decision making process which affects anyone not similarly cognitively impaired.
Skill is attained through use over time, and LLMs haven’t been available long enough for anyone to have attained anything close to a competency that can reasonably be applied to an environment other than a vacuum sealed laboratory.
People need some way to refer to the technology when it might be used beyond the context of language. Just be happy they’re not calling it a neural network in the common parlance anymore.
My textbook from ‘92 has a big preface that explains how the theory of mind the phrase “neural network” came from has been debunked for 20 years and they’re only using it as the title of the book and in the text because it’s the name of the technology.
Fine, but most people talk about AI, and AI datacenter, and AI coding to refer to LLM, so it is what I use, well knowing we are talking about LLM. And while I grant you that the entire software development world is not ready for LLM, having spent decades optimizing for people writing software, there is a lot that we learned in the last year of consistent use applied to software development.
LLM exhibiting true intelligence or the appearance of intelligence is inconsequential if the final result mimics the reasoning capabilities of humans working on software.
Cope
[deleted]
lmao
Sign in to comment. Sign in