Live data from Hacker News

Use AI code tools as collaborators, not crutches

newsletter.oberai.dev

31–40 of 78 posts

Re: Use AI code tools as collaborators, not crutches

#31

> This is not innovation. This is a security breach waiting to happen. No, it is innovation. The problem is that innovation is often bad .

How specifically is innovation often bad? Innovation, like scientific discovery, is merely an expansion of the veil of knowledge. Specific applications may be good or bad but knowledge and processes are neutral.

Innovation usually creates losers, who formerly benefited from the less efficient system in place.

Re: Use AI code tools as collaborators, not crutches

#32
post #11

Articles like this make one think of John Henry vs. the steam drill. John Henry beat the steam drill, once, and died. Soon, there was a better steam drill. "Vibe coding" is only a few months old. ChatGPT was released less than three years ago. The singularity is just getting started. History of computer chess: - 1957 - early programs that played chess very badly. Excessive optimism - 1967 - programs that play amateur…

Did 1957 level plays a wrong move according to the rules of the games? Like moving a bishop horizontally? And randomly?

Don't forget that in, 1957, computer's performance was much lower than today's. I wonder how a 1957 approach would fare on today's computer after removing limitations based on past limitations?

Re: Use AI code tools as collaborators, not crutches

#33
post #26

Every time I see someone on HN crowing about how great so-called "vibe" coding is, I can't help by think they must be doing the lowest, most basic types of coding. I don't need AI to help me code. What I need AI to do is help me figure out new coding solutions. But all AI seems able to do is regurgitate things that other people have already done that it's ingested from the internet. I'll ask AI how to do abc , within…

In my banking megacorp, despite having officially title of senior sw engineer, coding is maybe 10% of my time spent. And its the best, most creative part I actually enjoy. Why would I give up that? No real velocity gained even if all would be 1 click away in flawless production-ready state. The real cruft of seniority is: processes, knowing right people and their buttons, politics, being there to fix obscure corner c…

Lol, are you me? Also a senior developer at a financial institution. I've maybe coded like 1000 lines in the last 2 months. I just got a ticket recently that required code and it felt like a weight lifted off my shoulders to finally be able to put hands to keyboard again.

Re: Use AI code tools as collaborators, not crutches

#34

Experienced senior developers can spot and fix the slop instantly, while still getting a 30x productivity gain, while entry level or junior devs basically only have one "Filter" by which they determine code quality which is: "Does the code seem to work?". Unfortunately "Slop" will appear to work enough of the time to fool a Junior. Also the reason Junior devs get "slop" is because their prompts are "slop". They don't…

>while entry level or junior devs basically only have one "Filter" by which they determine code quality which is: "Does the code seem to work?".

Based on my general experience with software over the last...30 years, most places must only have entry level and junior devs. Somehow despite 30 years of hardware improvement, basic software apps are still as clunky and slow as their '90s counterparts.

Re: Use AI code tools as collaborators, not crutches

#35
post #14

Experienced senior developers can spot and fix the slop instantly, while still getting a 30x productivity gain, while entry level or junior devs basically only have one "Filter" by which they determine code quality which is: "Does the code seem to work?". Unfortunately "Slop" will appear to work enough of the time to fool a Junior. Also the reason Junior devs get "slop" is because their prompts are "slop". They don't…

30x productivity gain? gtfo of here. Most things I try to use it for, it has so many problems with its output that at most I get a 50% productivity gain after fixing everything. I'm already super efficient at editing text with neovim so honestly for some tasks I end up with a productivity loss.

I can easily get a month of work done in a single day yes. So probably the 30x is about the current max, and 50x was hyperbole, because I didn't add it up before doing that post.

Re: Use AI code tools as collaborators, not crutches

#36
post #9

Experienced senior developers can spot and fix the slop instantly, while still getting a 30x productivity gain, while entry level or junior devs basically only have one "Filter" by which they determine code quality which is: "Does the code seem to work?". Unfortunately "Slop" will appear to work enough of the time to fool a Junior. Also the reason Junior devs get "slop" is because their prompts are "slop". They don't…

I've worked with some pretty smart people in my career and I've never met anyone who could do "instant" code review.

Actual code review is very slow. More often than not, you just looking for glaring mistakes, not that the code actually respect the specifications. Which results in the LGTM comment. Because you trust the other person's experience. In very critical system, change is very slow to get in.

Re: Use AI code tools as collaborators, not crutches

#37

Experienced senior developers can spot and fix the slop instantly, while still getting a 30x productivity gain, while entry level or junior devs basically only have one "Filter" by which they determine code quality which is: "Does the code seem to work?". Unfortunately "Slop" will appear to work enough of the time to fool a Junior. Also the reason Junior devs get "slop" is because their prompts are "slop". They don't…

>while entry level or junior devs basically only have one "Filter" by which they determine code quality which is: "Does the code seem to work?". Based on my general experience with software over the last...30 years, most places must only have entry level and junior devs. Somehow despite 30 years of hardware improvement, basic software apps are still as clunky and slow as their '90s counterparts.

The only thing more reckless than a junior is an LLM-empowered junior.

Re: Use AI code tools as collaborators, not crutches

#38
post #9

Experienced senior developers can spot and fix the slop instantly, while still getting a 30x productivity gain, while entry level or junior devs basically only have one "Filter" by which they determine code quality which is: "Does the code seem to work?". Unfortunately "Slop" will appear to work enough of the time to fool a Junior. Also the reason Junior devs get "slop" is because their prompts are "slop". They don't…

I've worked with some pretty smart people in my career and I've never met anyone who could do "instant" code review.

Ruling out or refining an approach on the grounds it’s unlikely to lead to a suitable outcome (fixing and removing slop) is not the same as saying this code or approach represents a good enough outcome given what we currently know about the constraints of the problem (code review)

Re: Use AI code tools as collaborators, not crutches

#39

Experienced senior developers can spot and fix the slop instantly, while still getting a 30x productivity gain, while entry level or junior devs basically only have one "Filter" by which they determine code quality which is: "Does the code seem to work?". Unfortunately "Slop" will appear to work enough of the time to fool a Junior. Also the reason Junior devs get "slop" is because their prompts are "slop". They don't…

Whenever I can't just sit down and bash out code, it's because the design is wrong. These models are bad at design. I don't see where your 30×–50× could possibly come from.

Most of the times, the only reason I have the code open is to read it. If not for the huge amount of code, I could just print it out and go on my sofa.

If I'm dealing with a difficult to implement algorithm, a whiteboard is a better help than bashing out code.

Re: Use AI code tools as collaborators, not crutches

#40

Love it. We’ve reached the no-true-scotsman part of the vibe coding hype speedrun.

I'm curious which part of the article led you to that conclusion? It seems to make a pretty reasonable distinction between vibe coding and general use AI in coding to me. It's clearly not hyping up vibe coding, or even presenting it in a positive light.

There’s an article?
Post reply on HN