Comment by nik282000
1 day ago
It's weird how lazy people are unwilling to take the advice:
> Stop using the lazy answer box, it will make you lazy.
1 day ago
It's weird how lazy people are unwilling to take the advice:
> Stop using the lazy answer box, it will make you lazy.
To me, it is not the right advice. "Stop using that tool, that tool will make you lazy" means we would be digging holes by hand instead of using shovels, then excavators.
The "lazy answer box" is a tool, learn to use the tool, understand its limitations, as act accordingly. If you prefer not to use it because you like coming up with answers yourself, because it is against your principles, or because you can do better without it, that's fine. Hand tools still have a place in the workshop after all, and craftsmen know to use them. But if AI is helpful to you and lets you spare some cognitive load for other tasks, by all means use it, it would be stupid not to.
Can we explore the digging holes analogy a bit more?
Digging by hand with a shovel involves
1. Assessing the terrain and checking any documented or obvious obstacles (subsurface water, gas, electricity etc)
2. Planning the approach to digging the hole, most efficient angle, and ensuring that collapse doesn't occur
3. Organising disposal
4. Digging the hole
5. Dealing with any unforeseen issues (old tree roots, old foundations etc)
This is exactly the same whether digging by hand or using an excavator. The excavator isn't automating stages 1, 2, 3, or 5. It's just speeding up the 4th stage and only if there aren't stage 5 issues present.
LLMs when employed in a manner on the extreme end of the vibe coding spectrum are automating every stage of the process. If the excavator was hooked up to an LLM and left to run all stages of digging (extreme vibe digging?), I'd argue that yes, the operator is becoming lazy, and is running a very dangerous operation.
I think most people try the "extreme end" of vibe coding -- "Claude, write me an app to do X" once or twice and realize that doesn't really work -- to get it to work reliably you basically have to write a ROADMAP.md that details each step in a fair amount of detail -- pretty much the same work you'd have to do to hand a project off to a human intern.
3 replies →
> LLMs when employed in a manner on the extreme end of the vibe coding spectrum are automating every stage of the process
And when you have a backhoe, you can skip a lot of those things, too. It's bad, sure.. but so is skipping a lot of the important parts when using AI.
Most people don't even know to call before they dig, that's why there are public awareness campaigns about it. Most people don't consider any of the things you mentioned when digging a hole. Organizing disposal, really? Most people don't think that far ahead and dump the dirt right next to the hole.
With current LLMs, the excavator in your example would be the one to spend 90% of the time sitting there and doing steps 1-3, and possibly asking for permission to call for an inspection or a team of professionals should these steps reveal 4 cannot be done safely.
In theory, you take the same amount of time, and because step 4 is so fast you can spend more time on the steps before and after, and finish with a better result.
Over in the "AI is not a tool" post there's this comment: https://news.ycombinator.com/item?id=50063732
Which says that it's a tool for querying and summarization, but not a tool for reading or writing, because it helps you to do something different from those.
(Yes I know, don't cross the streams. I just thought it was a shame for this nice distinction to languish over there when you need it over here.)
Is lint a tool? If so, what's wrong with treating Claude as an ungodly-effective lint? You don't have to one-shot everything, or anything at all. You can ask for as much help or as little help as you need.
Another way to look at it: when I'm using Claude to write application code, I'm engaging with the machine and the work product in a different way. I'm not "programming" anymore, so OK, maybe it's reasonable to say Claude isn't a programming tool. Instead, I'm doing something new, something that perhaps we don't have a verb for yet. Whatever that verb is, Claude is a tool for it.
The problem is that while it is entirely possible in principle to use AI as a tool, not a surrogate, the actual interfaces to widely available AI models constantly push their users towards delegating their thinking to AI, rather than assisting their thinking. I constantly have to stop Claude from just doing the thing for me instead of presenting me with options or evidence and letting me choose how to proceed.
One thing I am trying to do is "Discovery" session in the start, where I try to give my AI all context it needs to achieve the task, ask it questions for other things I might have missed, and for what they expected then go for it. Seeing outstanding results (Not plan mode but actual discovery)
I guess my counterpoint is bluntly - no-one will not be using the tool at their day-job.
It requires so much extra discipline to think for yourself and not use it, you will be forced to use it in your job or be seen as a Luddite and your ability to think for yourself in the domain will diminish over time - your domain thinking muscle will gradually atrophy from lack of use.
Why would any of us bother thinking hard, when there is no financial incentive to doing so ?
Your analogy fails with shovels and excavators .. because General synthetic intelligence is not a single purpose narrow 'tool'. near-future AI is equivalent to an alien intelligent species competing for resources, or equivalent to a cheaper smarter non-human 'outsource worker'.
I am actively trying not to use it at my day-job, and I am a (mainly) computational physicist. My mother tongue is not English, I live in a country where the language is neither my mother tongue nor English, and I still don't use AI for writing emails or other documents. It is going OK so far. However, if significantly more powerful AI is developed, I think that we'll have much more serious problems than using or not-using AI in our job.
I'm not sure why you say the analogy fails just because general AI has more applications than excavators. A tool is still a tool, regardless of how much human effort it replaces.
"Calculator" used to be a job title. Now it's a machine. In the same way, "construction worker" may one day be a machine. "Software engineer" may one day be a machine. "Engineer" in general may one day be a machine. This forum seems to think that if humans are not required to think hard about existing problem domains, something terrible will happen.
At the end of the AI revolution, thinking may become something like physical exercise -- something we do because it's fun, and keeps us healthy and attractive, not because it's required.
To be clear, I do think that AI poses a potential risk to humanity. But imo "we won't have to think as hard" is not a risk; it's a benefit.
4 replies →
'Why would any of us bother thinking hard, when there is no financial incentive to doing so ?'.
Do you really think so? What a depressing view and simply, for many people I'll bet, totally wrong. But that's just my view. I'm working hard on something at the moment and, sure there's a financial incentive but it's the thought of a successful resolution of the project that is the deeper incentive.
In the context of education, your analogy doesn't work. We still have physical education in schools because, even though people can now use automated tools for physical work rather than doing it by hand, it is still useful for people to be physically fit.
A wheelchair is also a tool! A very efficient one too! People claim they've 2x'd their energy efficiency by not ever walking or standing, and they are much more happy now that they don't need to suffer the pain of walking! I'm thinking of amputating my feet just to make footoids seethe more!
A car is exactly what you describe, and even the fitness nuts use them.
It is actually a great example. Slobs use them just to avoid a 5 minute walk, even though walking is cheaper and faster. Reasonable people will take their into account their time, money, health and circumstances to choose whether to walk or to drive. And some crazies think cars are evil and will walk for hours and put themselves in danger instead of driving.
Same idea with AI. One one side, some people will turn off their brain and let the AI take control, on the other side, others will spend hours searching what a simple prompt can get them in seconds. Reasonable people are in the middle.
The obligatory Deus Ex Machina: Mechanical Apartheid cinematic trailer:
https://youtu.be/D7XCAgj0TtI
It's a tool that promises that you can be lazy. That's, like, the whole schtick. Of course people will be lazy using it, even if they don't intend to.
And in much of the industry, using LLMs is regressing into what I've heard be jokingly called "yes engineering," where you give an LLM-generated plan the lightest of skims (if that) and just hit allow or yes with auto mode or whatever.
I don’t think that’s “the whole shtick” anymore than it is for something like cars. There are valid ways to use it as a tool to provide net new value, and inevitably a whole bunch of people will end up using it as a lazy machine anyway, especially if their country/society benefits from people using it that way (Americans in both cases).
This was literally George Jetson's job on The Jetsons: pushing a button on the computer RUDI while it did all the work. The joke being that he works 4 hours a day, 2 days a week pushing a button and complains about being tired when he gets home, because that's how the future will be: full of unimaginable leisure.
As alienating and stultifying as this work seemed, however, The Jetsons is still an optimistic future compared to the one we're getting: when George is fired, RUDI intervenes on his behalf and gets him rehired. I don't see Claude doing that for me; its raison d'être is ensuring I'm put out of work.
I use it as a hybrid of that I guess: I prompt some simple tool into existence, iterate a bit, then I look at the code, am very dismayed and spend more time than it might have taken me to build from scratch to refactor it.
It solves a huge motivation problem for me though, because having a working prototype of something I want is a lot. Especially when it's something I never did, where I cannot imagine the end result fully, or estimate my own ability to get there. But if I can see the thing in action, while I may look at the code (and my own skills) and realise it would take me months to make it something I could share with others, I at least know there is a destination.
Not to mention how it surfaces all sorts of issues I didn't think of, so I'm basically prototyping v2 before I ever fully built v1, and so on, until it kinda settles.
I guess I'm lucky I don't do it professionally :P