Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- It would be interesting to see the linked talk "Useing You're Type's Good", but it seems to have been deleted.by normie3000
- I was curious about codeberg.org as an alternative to Github for opensource work. They had voted on an LLM policy and decided against vibe-coded repos while allowing some AI use. This got me thinking how I want to use AI and if it fit with their policy.
The best I could figure is that I like to start with requirements, use AI to discuss and settle on its high level design and specific aspects of its implementation. I may or may not read all the code, but the key thing is even if I didn't read the code in advance, doing so would not be a surprise and I'd know what it was doing and how it was doing it because those were things I decided during the up-front conversations and not left as an open exercise for the AI. And coming back to the codeberg.org vote I can guess that it was elements like these that they wanted to guard. They don't want repos whose owners don't know what the code does in a technical sense or how it's constructed etc. There's likely other things too like seeing text that doesn't read like people wrote it and I find that tiring to read (in a literal way, I get drained from reading too much of it) and endorse minimizing that.
Another thought was that my ever long search for better and better programming languages was that if I have a clear vision of what I want the language should have the least friction to write it down. Some languages that feel closer than others were Elm, Elixir, F#/OCaml, Pony, Rust, Kotlin, Go. Only a couple of these are my languages I'd regularly used but would prefer to have my AIs write in them. For web I'd probably also accept Vue, Svelte, or (simple) React. In particular using Go for mini back-ends is particularly effective as the coding style tends to be regular and boring which minimizes differences between human and machine written styles. So in a sense giving specs at multiple levels of abstraction and detail is the perfect high level language I'd been wanting.
by karmakaze - I think the employment thief point is always misstated.
We invented compilers, word processors, templated document generation, code generators, DSLs and things like that which were all labour reduction technologies for describing systems and information. These were net positives for society but wiped out full administrative and technical professions.
The issue is the impact that technology has on society. It should used to free up more time for enriching humanity with art, music, sciences, mathematics etc. But what really happens is they are used entirely for concentrating wealth by taking revenue and reducing employment, leaving functional people unemployed, destitute and in debt to the people who have the wealth concentration.
At this point it's morally objectionable on all grounds.
A second point, which should be considered an addition to the article is that AI coding shapes thinking based on its capabilities, not the user's intent. I see this a lot. If the objective is to do thing X because it aligns with a well-researched strategic analysis, it may not align with that. People are happy to be pushed to do thing Y which is a totally different thing because they are being slowly gaslit into accepting the mediocrity that the model promotes. This leads to poor business outcomes. And all this is hidden and written off because everyone needs to be seen as AI thought leaders at a high level because that's what keeps the stock going up and engineers are being rated on delivery, not on ROI.
Everthing is fucking broken.
by sdcfgy - I am not sure if I am more tired of people building with AI or people complaining about people building with AI. If you really that bothered, there is nothing stoping anybody from keep doing things the good old way... What's the big deal?
- My say about this
1. I think most of us know the same thing is occurred when first compile came into the market (Most of them hated it saying 'High Quality ASM code would be only generated by humans' . Moving forward asm hasn't dead but we are only using it only at critically. I think we will do same with LLMs we use what useful and Move forward.
2. Life's isn't just always staying in front of a box and writing some code. If AI does the job of creating useful code with quality i would be more than happy since i could get start to work on more abstract things like Arts and Humanity. which for our growth is essential as you can see the current society is currently disdain.
Finally to conclude don't try to interrupt the flow just accept it and move forward.
Life is SHORT
by Regex777 - I like coding. You can take away my AWK and C, Bash and Go and Javascript (yes I even enjoy coding Javascript unironically, sue me. I like making self-contained HTML5 one-file-and-offline tools for fun) only from my cold, dead hands. But don't we get one of these articles like once a week at least? It's getting kind of tiresome.
Like, I get the idea, I really do, but is there a need to announce it to the winds so often? Is this a pride thing?
by falsaberN1 - I don't like AI coding, but I can't say it's not useful. Most of the arguments in this article can be disarmed by taking the abstraction "one step up". LLM generated modules and software, microservices, whatever your level of abstraction... now need to be composited together. You go and deal with higher order problems, factories, generation, etc.
Is it a way to develop critical bits of code, depths of your business logic? Absolutely not. Can it solve a lot of boilerplate and support logic? Absolutely yes.
Seeing "AI Companies as Bad Actors"... can't fully disagree there. There's far too many far too dodgy things about these businesses, and I trust them as far as I can audit them (not very far). And the missing argument's the cognitive decline of using these things to think for us. I try to keep myself sharp by still manually doing a fair amount of things in my life. I refuse to automate _everything_ - especially the stuff I do for fun. Having an LLM manage hobby-adjacent stuff is a quick trip to burnout land, especially once fixing the thing becomes "the hobby"... and it does.
by tinthedev - > Code as Art
Code is code.
Code can be art, code can also be simply a tool to reach a goal.
If you want to create art, do it with your own two hands and your brain.
If you want to just Do The Thing, codegen it. No one cares. In before "Except your users having to use your vibeslop" FYI your Hand-Crafted Artisanal Code will still have bugs, so it's a moot point.
Heck, the very first thing the author does is links to another one of his own blog post where the above points are explicitly stated and explained, then restates at the end of the paragraph that there are no valid arguments for this one. So why keep beating this dead horse? Especially as the opener of the article.
This kind of mindset baffles me.
by dev0p