2 ms·
This article starts with this section about how easily we can trick ourselves and ignore clear evidence of something: > But Cialdini’s book was a turning point
by simonw 1y ago
This article starts with this section about how easily we can trick ourselves and ignore clear evidence of something:
> But Cialdini’s book was a turning point because it highlighted the very real limitations to human reasoning. No matter how smart you were, the mechanisms of your thinkings could easily be tricked in ways that completely bypassed your logical thinking and could insert ideas and trigger decisions that were not in your best interest.
The author is an outspoken AI skeptic, who then spends the rest of the article arguing that, despite clear evidence, LLMs are not a useful tool for software engineering.
I would encourage them to re-read the first half of their article and question if maybe they are falling victim to what it describes!
Baldur calls for scientific research to demonstrate if LLMs are useful programming productivity enhancements or not. I would hope that, if such research goes against their beliefs, they would chose to reassess.
(I'm not holding my breath with respect to good research: I've read a bunch of academic papers on software development productivity in the past and found most of them to be pretty disappointing: this field is notoriously difficult to measure.)
- Beijinger 1y agoMan, I have no idea of programming and I wrote a hackernews clone in one day with chatgpt.
- Beijinger 1y agoWhy the down vote? It is true. I took a template (very few of the code should be the same), added language support, included RSS feeds. Here it is: http://news.expatcircle.com/ http://news.expatcircle.com/ (registration does not work. Have to upload the latest version. This thing is not really live yet. I will make it available on my github). BTW, VS Studio is the best software MS ever produced.
- vouaobrasil 1y agoI think the question of whether LLMs are useful for software engineering is not the right question at all. The better question should be whether long-term LLM use in software will make the overall software landscape better or worse. For example, LLM use could theoretically allow "better" software engineering by reducing bugs, making coding complex interfaces easier --- but in the long run, that could also increase complexity, making the overall user experience worse because everything is going to be rebuilt on more complex software/hardware infrastructures. And, the top 10% of coder use of LLMs could also make their software better but make 90% of the bottom-end worse due to shoddy coding. Is that an acceptable trade-off? The problem is, if we only look at one variable, or "software engineering efficiency" measured in some operational way, we ignore the grander effects on the ecosystem, which I think will be primarily negative due to the bottom 90% effect (what people actually use will be nightmarish, even if a few large programs can be improved).
- simonw 1y agoIf we assume that LLMs will make the software ecosystem worse rather than better, I think we have two options: 1. Attempt to prevent LLMs from being used to write software. I can't begin to imagine how that would work at this point. 2. Figure out things we can do to try and ensure that the software ecosystem gets better rather than worse given the existence of these new tools. I'm ready to invest my efforts in 2, personally.
- vouaobrasil 1y agoI would rather not play the prisoner's dilemma at all, and focus on 1 if possible. I don't code much but when I do code or create stuff, I do with without LLMs from scratch and at least some of my code is used in production :)