The reason I get so annoyed about people pitching LLMs as a way to 'democratise programming' or as end-user programming tools is that they solve the wrong problem.
The hard part of programming is not writing code. It's unambiguously expressing your problem and desired solution. Imagine if LLMs were perfect programmers. All you have to do is write a requirements document and they turn it into a working program. Amazing, right? Well, not if you've ever seen what most people write in a requirements document or seen the output when a team of good programmers works from a requirements document.
The most popular end-user programming language in the world (and, by extension, the most popular programming language), with over a billion users, is the Calc language that is embedded in Excel. It is not popular because it's a good language. Calc is a terrible programming language by pretty much any metric. It's popular because Excel (which is also a terrible spreadsheet, but that's a different rant) is basically a visual debugger and a reactive programming environment. Every temporary value in an Excel program is inspectable and it's trivial to write additional debug expressions that are automatically updated when the values that they're observing change.
Much as I detest it as a spreadsheet, Excel is probably the best debugger that I have ever used, including Lisp and Smalltalk.
The thing that makes end-user programming easy in Excel is not that it's easy to write code, it's that it's easy to see what the code is doing and understand why it's doing the wrong thing. If you replace this with an LLM that generates Python, and the Python program is wrong, how does a normal non-Python-programming human debug it? They try asking the LLM, but it doesn't actually understand the Python so it will often send them down odd rabbit holes. In contrast, every intermediate step in an Excel / Calc program is visible. Every single intermediate value is introspectable. Adding extra sanity checks (such as 'does money leaving the account equal the money paid to suppliers?') is trivial.
If you want to democratise programming, build better debuggers, don't build tools that rapidly generate code that's hard to debug.
@CM30 Interesting... Nintendo says the new design for DK is actually based on a different, older design of DK.
I wonder if we're going to get some backstory about him "abducting" Pauline? That could be very interesting.
@CM30 Computer programmer. I love when social networks are federated, it totally makes more sense than centralized when it comes to socialization.
@256 I can only imagine how cool it would look to have a 9-monitor #Windows98 setup with CRTs of different sizes, in a half-organized manner (like the setup in #CloudyWithAChanceOfMeatballs)
@DrewNaylor @256 Or maybe 10, for discovering that it cannot handle any more 😆
@admiralwonderboat This is one of the reasons I haven't tried listening to YouTube at night 😆
The word "idea" sounds like "idiate". I'm reminded of this a lot now.
WordNet (r) 3.0 (2006) (wn)
ideate
v 1: form a mental image of something that is not present or
that is not the case; "Can you conceive of him as the
president?" [syn: imagine, conceive of, ideate,
envisage]
@royal I like this idea.
This shouldn't be necessary.
https://arstechnica.com/ai/2025/03/cloudflare-turns-ai-against-itself-with-endless-maze-of-irrelevant-facts/
This is terrible stuff. Have your projects been affected?
https://thelibre.news/foss-infrastructure-is-under-attack-by-ai-companies/
#ai #enshittification #foss
Hello there!
I boost a lot of posts, but I have a few things to say every now and then.
I am largely fine with boosting posts from people I disagree with even on significant, dividing issues. I usually don't, however, if they actively advocate for these ideas... so it goes :/
#Christian #coding #HaikuOS #Linux #privacy #FOSS #Fediverse #SmashBros #SSBU #LegendOfZelda
#fedi22
Note: social.librem.one doesn't support DMs