11–20 of 158 posts
"that’s when it struck me. coding isn’t about the finished product. its a lot like writing. its about the process. its about how you approach a problem. its critical thinking." From a business perspective, they don't care about this. They just want it built as inexpensively as possible in a reasonable time frame. Vibe coding is here to stay.
"that’s when it struck me. coding isn’t about the finished product. its a lot like writing. its about the process. its about how you approach a problem. its critical thinking." From a business perspective, they don't care about this. They just want it built as inexpensively as possible in a reasonable time frame. Vibe coding is here to stay.
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 velocity even as little as 50%, no sane business is going to let their engineers ignore it just because it's not as fun as artisanal code.
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.
"that’s when it struck me. coding isn’t about the finished product. its a lot like writing. its about the process. its about how you approach a problem. its critical thinking." From a business perspective, they don't care about this. They just want it built as inexpensively as possible in a reasonable time frame. Vibe coding is here to stay.
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.
To each their own, of course. But > what was the point of it all if i didn’t learn a thing? Money. Freedom. Supporting a family. Doing things faster. Keeping up with changing times. etc.. There are a ton of different answers, and it depends on your goals. > coding isn’t about the finished product Again, to each their own.
I feel really sad for those who are starting out today. In many cases, especially for frontend programming, vibe coding correctly has a lot of value but it does makes you not learn anything.
Which means you remain at what I call the "vibe plateau".
One useful technique I've been telling my mentees to learn programming is to use a language where you are forced to not be able to use vibe coding such as Haskell or Rust.
But if you are in mediocre Javascript or Python land, it is a hard fight for the younger ones.
"that’s when it struck me. coding isn’t about the finished product. its a lot like writing. its about the process. its about how you approach a problem. its critical thinking." From a business perspective, they don't care about this. They just want it built as inexpensively as possible in a reasonable time frame. Vibe coding is here to stay.
I agree, and it's why I'm not worried about running out of paying work as I head into the latter half of my career.
"that’s when it struck me. coding isn’t about the finished product. its a lot like writing. its about the process. its about how you approach a problem. its critical thinking." From a business perspective, they don't care about this. They just want it built as inexpensively as possible in a reasonable time frame. Vibe coding is here to stay.
Vibe coding is a death trap for juniors just starting out, as it kills critical thinking and understanding what a computer is. And a guaranteed paycheck for people with the experience to clean up the resulting messes. I hope...
Teams will be led by one subject matter expert, and fulfilled by thousands of agents. I would not be advising anyone under 21 to become a "coder". Studying computer sceince still has value, but coding was the lowest hanging fruit for LLMs.
Once we can do LLM code reviews with high confidence and little error, coding is essentially a dead field.
The closer you are to atoms and further the way you are from bits, the better off you will be in the coming two decades as AI progresses