Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I won't be vibe coding anymore: a noob's perspective

varunraghu.com

Post reply on HN
Print view View original

81–90 of 158 posts

Re: I won't be vibe coding anymore: a noob's perspective

#81

Post by constantcrying »

josephwegner wrote: post #13

> 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…

If AI increases programmer productivity by just 5% it is easily worth it.

I have no doubt that AI, right now saves me 5% of my time. That is 24 minutes a day I am not searching for something in the documentation of some library.

Re: I won't be vibe coding anymore: a noob's perspective

#83

Post by constantcrying »

rocqua wrote: post #78
Sayrus wrote: post #31

Earlier quoted context omitted.

> even as little as 50% Depending on how you measure that velocity (e.g. including security risks, debugging capabilities, ...) even as little as 5% increase is a no brainer for a business. Whether it's AI, powerful laptops, a fully-fledged IDE, an environment with a good dev experience, anything that gives a few percent increase snowballs into millions over an entire workforce. Whether the current AI capabilities pr…

I would wager 80% of places that write software have almost trivial ways to get that 5% improvement. Between ci/cd, static checkers, upgrading IDEs, and just aligning practices between everyone, I think you can easily improve at 50% of places. Those things don't happen because the slowdown required before adoption, and the office politics of convincing everyone to make a change, and then the effort of convincing peop…

>I would wager 80% of places that write software have almost trivial ways to get that 5% improvement.

No. Because most of these changes are totally opaque, you don't know what change needs to be made and making it becomes a political problem in the organization. Giving each engineer a subscription to some service is trivial.

Re: I won't be vibe coding anymore: a noob's perspective

#84

Post by energy123 »

pests wrote: post #46
BayArea925 wrote: post #20

Earlier quoted context omitted.

Coding will not be done by juniors anymore. We are quickly progressing to humans no longer needing to learn machine langauage (syntax) and computers better developing code by interpreting human languages (english). 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…

Same promise all the no-code or low-code app builders claim. Anyone who has done a serious project with LLM help knows it is no where near able to do half the things needed to run a project.

Skill issue, you aren't vibe coding properly. I am not joking.

Re: I won't be vibe coding anymore: a noob's perspective

#85

Post by femiagbabiaka »

billy99k wrote: post #5

"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.

Virtually all businesses (even non-tech businesses) balance performance, reliability, cost, and revenue. Outages/bugs/crashes cost money, some can be fatal. They care.

Re: I won't be vibe coding anymore: a noob's perspective

#86

Post by HeyLaughingBoy »

rowanseymour wrote: post #52
billy99k wrote: post #5

"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.

Yes there are businesses (game companies?) which just want to get a thing out the door, sell it, and move on to the next thing. But I don't think that's how most software businesses function. Usually software is iterated on and maintained, and you've got a problem if nobody has invested time in understanding how that software actually works.

Maybe, but the vast majority of software isn't written by, or for, software businesses. It's written by internal teams for businesses whose main product is insurance, or retail sales operations, or cabinet manufacturing, or real estate, etc.

To quote Copilot, "According to recent data, nearly 70% of top economic performers use their own software to differentiate themselves from competitors."

Re: I won't be vibe coding anymore: a noob's perspective

#87

Post by jey »

captainkrtek wrote: post #28

Using AI to assist in locating the right library function or similar to documentation has been effective to speed up my development, but I really dislike using it to autocomplete whole functions or large swathes of code, because then I have to spend time reading and understanding code I didn't write. This doesn't ultimately feel "faster" when I own what I write.

I’ve had good results using Claude Code by specifically coaching it on how its implementation should be. It’s not always perfect and sometimes I do have to try again, but it’s remarkably effective when given enough guidance.

If only I could figure out how to reliably keep it from adding useless comments or preserving obsolete interfaces for “backward compatibility”…

Re: I won't be vibe coding anymore: a noob's perspective

#88

Post by jckahn »

magicink81 wrote: post #7

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?

Re: I won't be vibe coding anymore: a noob's perspective

#89

Post by holtkam2 »

I feel like the fundamental bottleneck of software dev velocity will be human brains ability to understand the code being made. We can’t deploy code / packages / systems / apps we don’t deeply understand, no matter if those components were written in 3 weeks by a team of devs or in 3 seconds by GPT-7, we’re still responsible for it when it gets into users hands, and we’re not gonna deploy stuff that we don’t know how it works. Because at the end of the day it’s our necks on the line if something goes wrong and we’re asked to fix it. We can’t just point the finger at AI, which means we’ll always have to understand what we’re putting out there in the world, and that’s essentially what our jobs will be in the future. The one who’s accountable for the software systems put into production.

Re: I won't be vibe coding anymore: a noob's perspective

#90

Post by karmakaze »

> 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 warehouse package handling with robots due sooner than later.

Code or code not, there is no Vibe coder.

Post reply on HN