Live data from Hacker News

The AI coding trap

chrisloy.dev

421–424 of 424 posts

Re: The AI coding trap

#421

Every day I think to myself: "Just fake it like you want to be here for 30 more years and then you can retire." I have been working in machine-learning for 10 years. I am tired of the computer. I am tired of working. I just want to lay in the grass.

Can you work less (maybe for some time)? Getting yourself bigger chunks of free time might help. All the best!

Re: The AI coding trap

#422
post #239
post #222

Earlier quoted context omitted.

Yes, open source works whose licenses constrain derivative works.

Some licenses do. In my experience AI coding is not going to spew out a derivative of another project unless your objective is actually to build a derivative of that software. If your code doesn't do the same or look the same it doesn't really meet the criteria to be a derivative of someone else's. I mostly use Cursor for writing test suites in Jest with TypeScript, these are so specific to my work I don't think it's…

> unless your objective is actually to build a derivative of that software

The objective of a for-profit corporation may well be to build a derivative of free software, benefitting from the work volunteer engineers put into it. Previously, if that software is GPL, it would imply a clean-room reimplementation of a massive codebase. With LLM laundering, relevant companies could as well simply claim “we got this from copilot” and they would be right (note that they don’t need to have used an LLM—the mere legality of these license-laundering LLMs means you can simply copy this from a GPL codebase and claim that an LLM output it due to its non-deterministic nature). This goes contrary to the promise of copyleft licenses that volunteer contributor work will remain to benefit the public and could not be expropriated this way, which led to OSS explosion in the first place.

Re: The AI coding trap

#424
post #323

Broadly the critique is valid where it applies; I don’t know if it accurately captures the way most people are using LLMs to code, so I don’t know that it applies in most case. My one concrete pushback to the article is that it states the inevitable end result of vibe coding is a messy unmaintainable codebase. This is empirically not true. At this point I have many vibecoded projects that are quite complex but work p…

Can you share any of those projects with us?

Here's one. https://doofmovies.com/ With this project I'm sort of playing a game where I want to see how long I can go without finding out what language the backend is written in. I still don't know.
Post reply on HN