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

I'm opening VSCode less and less every day

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 29 posts

Re: I'm opening VSCode less and less every day

#11

Post by surprisefox »

bellowsgulch wrote: post #6

Who are you people not writing code? There isn’t a single SOTA model on the market that writes code as nicely as I write it. I can only suspect these people saying they write no code have zero taste, because that’s the only way I can understand accepting the unsophisticated garbage these models produce.

Interesting take and I don't want to dismiss your experience but it's not mine.

15+ years writing code and refining it, learning. Is AI code as good? Definitely not. Is it 80-90% or the way there with correct linting, agent setup and rules? Absolutely.

It's quality vs speed vs cost adage

Re: I'm opening VSCode less and less every day

#15

Post by othmanosx »

bellowsgulch wrote: post #6

Who are you people not writing code? There isn’t a single SOTA model on the market that writes code as nicely as I write it. I can only suspect these people saying they write no code have zero taste, because that’s the only way I can understand accepting the unsophisticated garbage these models produce.

I still believe that I can write better code compared to what the AI can produce. But is it really... cost-effective? Probably not.

Re: I'm opening VSCode less and less every day

#16

Post by al_borland »

PaiDxng wrote: post #4

AI allows developers to write less code, but it shouldn't make us understand less. If you miss writing code, it just means you still truly care about the craft itself.

> it shouldn't make us understand less

The understanding derived from actually writing the code and making it work is much different and deeper than looking at code written for you, looking at it, and thinking, "yeah, that seems like it makes sense".

Even if I spend a significant amount of time reviewing the code to try and understand every line that was used, I don't necessarily understand why it was chosen, what were the alternatives, what would the trade offs of those alternatives be, what seems like it should work but actually wouldn't, how something might break if a little part is missing... These are all things that are better understood when actually writing the code.

Post reply on HN