Parent's profile shows that they are an experienced software engineer in multiple areas of software development.

Your own profile says you are a PM whose software skills amount to "Script kiddie at best but love hacking things together."

It seems like the "separate worlds" you are describing is the impression of reviewing the code base from a seasoned engineer vs an amateur. It shouldn't be even a little surprising that your impression of the result is that the code is much better looking than the impression of a more experienced developer.

At least in my experience, learning to quickly read a code base is one of the later skills a software engineer develops. Generally only very experienced engineers can dive into an open source code base to answer questions about how the library works and is used (typically, most engineers need documentation to aid them in this process).

I mean, I've dabbled in home plumbing quite a bit, but if AI instructed me to repair my pipes and I thought it "looked great!" but an experienced plumber's response was "ugh, this doesn't look good to me, lots of issues here" I wouldn't argue there are "two separate worlds".

▲

7 hours ago | parent | next [-]

[deleted]

▲

ModernMech 6 hours ago | parent | prev | next [-]

> It shouldn't be even a little surprising that your impression of the result is that the code is much better looking than the impression of a more experienced developer.

This really is it: AI produces bad to mediocre code. To someone who produces terrible code mediocre is an upgrade, but to someone who produces good to excellent code, mediocre is a downgrade.

▲

jasondigitized 3 hours ago | parent [-]

Today. It produces mediocre code today. That is really it. What is the quality of that code compared to 1 year ago. What will it be in 1 year? Opus 6.5 is inevitable.

	▲	AstroBen 33 minutes ago \| parent \| next [-]
		It produces the same quality code as it did years ago. The difference now is that it tends to function Still bad code though And by bad I'm not making a stylistic judgement. I mean it'll be hell to work with, easy to add bugs, and slow to change
	▲	ModernMech 2 hours ago \| parent \| prev [-]
		That's what they've been saying for years now. Seems like the same FSD marketing. Any day now it'll be driving across the country! Just you wait! -> Any day now it'll be replacing software developers! Just you wait! Frankly, the same people who fell for the former are falling for the latter. Rather, to me it looks like all we're getting with additional time is marginal returns. What'll it be in 1 year? Marginally better than today, just like today is marginally better compared to a year ago. The exponential gains in performance are already over. What we're looking at now is exponentially more work for linear gains in performance.

▲

jasondigitized 3 hours ago | parent | prev [-]

Except I work with extremely competent software engineers on software used in mission critical applications in the Fortune 500. I call myself a script kiddie because I did not study Computer Science. Am I green in the test run? Does it pass load tests? Is it making money? While some of yall are worried about leaky abstractions, we just closed another client. Two worlds for sure where one team is skating to the puck, looking to raise cattle while another wants to continue nurturing an exotic pet.

Plenty of respect to the craft of code but the AI of today is the worst is is ever going to be.

	▲	AstroBen 27 minutes ago \| parent \| next [-]
		Have a read of this: https://martinfowler.com/articles/is-quality-worth-cost.html
	▲	crystal_revenge an hour ago \| parent \| prev [-]
		Can you just clarify the claim you're making here: you personally are shipping vibe coded features, as a PM, that makes it into prod and this prod feature that you're building is largely vibe coded?