> Is this just a huge boon to those too lazy to learn? And what does that mean for later security and tech debt issues?

In the same way that GPS is a boon to people too lazy to learn celestial navigation or read a paper map.

In the same way that word processors are a boon to people too lazy to use a typewriter and white-out.

In the same way that supermarkets are a boon to people too lazy to hunt and gather their own food.

In the same way that synthesizers are a boon to people too lazy to hire a 40-piece orchestra.

In the same way that power drills are a boon to people too lazy to use a hand crank.

Those are all false equivalents. The GP speaks of "democratization of learning", which had already happened. It's more akin to if I said "now people can finally vote" when remote voting expanded to civilians. It's not like people couldn't have voted before, and in fact it had only a modest impact on turnout.

Then people would ask "is this just a huge boon to those too lazy to vote?", and the answer would be "no actually, voting is still a thing where one must do their own thinking."

If anything, it's a boon to people too lazy to drive, similar to LLMs being a boon for those too lazy to type.

Think about having to assemble a car (you can find specs and tutorials online, say) and then drive it, or asking engineers and mechanics to assemble it, and then using the car assembled by others to go for a drive.

You can always ask ChatGPT how to dissasemble and assemble you shiny new Ford F-150. /s

Too lazy to learn is a bit harsh and your statement lacks empathy.

Coding has been free to learn for a long time and the quality of education resources has only improved overtime. But that does not mean it’s easy and it doesn’t decrease the time to learn.

I’ll use myself as an example. I’m pretty creative, I have a lot of ideas and interests, but I struggle a lot with the logic and syntax of coding. I find it interesting at the surface level but every time I’ve tried to learn I just can’t get it to click. And, to be frank, I don’t find it very enjoyable.

But at the same time I have random website and app ideas quite frequently. I’ll use apps that have terrible UI/UX and imagine ways it could be better or maybe even design something in Figma if I’m feeling frisky. But actually making an app? Always just way too out of my wheelhouse. Plus I work 40-50 hours a week and prioritize socializing on the weekends, a lot of those ideas have to be relegated to just ideas on a list in Obsidian. Does that make me a lazy person? Maybe to you but I don’t think of myself that way.

The tools available now have unlocked something new for me. My ideas can start to come to life because the coding part doesn’t hold me back anymore. I’ve made silly websites with domains I’ve owned for years. I’ve made apps that solve an annoying issue I’ve had forever like a file media viewer app for my iPhone since file viewing sucks with Files/Preview and every app on the AppStore is infested with ads and didn’t fit my use case. I just for fun made an app that can play against me in MTG by using the continuity camera from my iPhone to my Mac to read the playing field.

I get where you’re coming from but you probably think every vibe coder is lazy because you’re good at coding. Not everybody has the talent/time/desire to learn how to code. Does that mean we can’t let our ideas come to life?

Honestly stories like yours are the best part of this whole AI revolution. It’s genuinely cool that the technical barrier is no longer killing creative ideas. You’ve essentially skipped the "coder" stage and jumped straight to orchestrator (Product Owner + QA rolled into one), with AI acting as the diligent junior dev. That is a totally valid model

The only downside is that sooner or later, you hit the scaling trap. When a project grows from a silly website into a real product with users, not understanding how exactly the AI stitched those code blocks together becomes a critical risk. AI is great at putting up walls and painting facades, but the foundation (architecture and security) still needs human verification, especially once other people's data gets involved

> The only downside is that sooner or later, you hit the scaling trap.

Which they might be able to overcome faster with the help of AI, again.

Trying to fix broken architecture with the same AI that wrote it leads to recursive technical debt. AI can rewrite code, but it cannot make strategic decisions if the operator doesn't understand the problem. In the end, instead of a fix, you get a Big Ball of Mud, just built 10x faster

You, like most hacker news folks, likely are too rich to imagine the type of person who can’t spend hours every day learning a billion different difficult things. Some folks have to work menial jobs, take care of their kids, and fix their leaky roof themselves.

Bad assumption. I taught myself to code in the early 2000s while scrapping by earning just above minimum wage in Vancouver, one of the most expensive cities in the world.

So uh, you would be hard pressed to be more wrong. And I used free resources.

as a software developer with a life after work, I don't have time to learn to be a mechanic either. So I don't claim to be one without having done the work.