101–110 of 158 posts
Earlier quoted context omitted.
I'm using AI for grepping, analyzing flow, finding cross-project dependencies, etc. It provides a significant speedup. But the generated code is mediocre at best. Changes look like patches on fabric, not woven threads. AI generates too much redundant code.
How do you use AI to grep?
> coding isn’t about the finished product. its a lot like writing This doesn't seem applicable in most contexts. Yes, when I'm coding for fun or purely for learning the finished product is less relevant... but I'd guess the vast majority of code that is written is for a business that _only_ cares about the product. Code is an implementation detail. If (and this is a _big_ if) AI-based coding can increase developer ve…
It’s worse. Code is a liability.
One problem I have is that AI is writing code I don't understand completely, yet I'm still responsible for it. Vibe coding seems like an echo from the future.
> code I don't understand completely, yet I'm still responsible for it. Is this different than any given library?
For a more comprehensive treatment of this insight, see: Programming as Theory Building by Peter Naur
But hey, I'm getting old, it is what it is.
> as i was lying in bed on a sleepless night. i realized i hadn’t learnt a new concept in weeks. i had built a few useful apps with ai, but a nagging question kept me awake - what was the point of it all if i didn’t learn a thing? A succinct post illustrating that vibe coding is to become a cog that will be the first to be replaced by the AI you use. It's a temporary, automatable job--like entering a career in wareho…
With that framing, I suppose "vibe-coding" would be in a similar realm to "button pushing" or "lever pulling" or "handle cranking".
There's often a transitional period where the task exists and needs to be done... but without enough human thought and judgement it's only temporary, and ends when it becomes cheap enough to hook up a motor or actuator.
> as i was lying in bed on a sleepless night. i realized i hadn’t learnt a new concept in weeks. i had built a few useful apps with ai, but a nagging question kept me awake - what was the point of it all if i didn’t learn a thing? A succinct post illustrating that vibe coding is to become a cog that will be the first to be replaced by the AI you use. It's a temporary, automatable job--like entering a career in wareho…
Earlier quoted context omitted.
What is coding without critical thinking? I never vibe coded, and I don't understand this trend AT ALL. I read how copilot and such are detrimental to critical thinking, and I am even consciously scaling back on copilot use now whenever possible, and prioritizing Google search, reading documentation, blog posts and stackoverflow now.
Every time I've tried to get LLMs to create something they quickly get to the point where they fail miserably. It can do boilerplate, it can do straightforward things which have been done a billion times, it can come up with 50 ideas 10 of which are decent and not obvious... but it can't go beyond a certain complexity, it can't use mildly obscure libraries, it can't get major versions of libraries straight, it invent…
If it's really "boilerplate", nobody should need to get a half-regurgitated approximation out of a statistical model.
Instead there should be a default implementation someone can choose until they need to customize, or a generator-script as part of the project, etc. Sometimes what people want is already right there in the docs, but nobody bothered to look.
This. This times a thousand. Every problem I overcome is a lesson learned that enriches my life and makes me more valuable. The results are nice but it's the journey and understanding that matter to me. There's more value in having a team of people who understand the problem domain so deeply that they can create a computer system to automate the solution. When things go wrong, and they will, you have to have the unde…
There is no inherent honor in toil.