It's the vibe coders who would love to pretend that the opposite end of the spectrum from them is "artisinal coding."

They honestly have no idea what "software engineering" in a professional context even looks like. So they come up with this prattle.

▲

winternett 8 minutes ago | parent | next [-]

The jargon is getting more & more obtuse every year...

Also, a major feature of "vibe coding" now is the rough edges on UI design that don't make sense at all... It's pretty obvious that code bases aren't evolving because these systems can't handle complex prompts while retaining features from prior releases, and it seems like functional testing for releases has now become the kid who can't speak that fell down a well... Oh well.

▲

Eisenstein 5 hours ago | parent | prev | next [-]

Blaming people who use technology to make a valuable process accessible to themselves and then invoking a a no-true-Scotsman in order to defend the status quo is a good example of a lack of soft skills.

▲

JohnLeitch 4 hours ago | parent | next [-]

But the process is still inaccessible to them, provided we consider achieving reliability and security goals of said process. And no, this is not "no true Scotsman;" "vibe coded" software is demonstrably inferior in numerous ways, and outright dangerous in some contexts. No number of carefully scripted demos or PR campaigns is going to change this reality.

▲

sillywabbit 4 hours ago | parent | prev | next [-]

Trotting out fallacy names on regular basis isn't going to win you any points.

▲

themafia 4 hours ago | parent | prev [-]

> make a valuable process accessible to themselves

I am directly calling into question the "value" of that process. It's also becoming increasingly clear that these tools just whitewash away the copyrights of the materials they were trained on and still mostly reproduce when asked. This would then actually be the destruction of value.

> invoking a a no-true-Scotsman

I did not. This is in response to an article. It demonstrates a clear lack of understanding of professional software engineering and instead imagines that writing a good spec is all there is to actually do. It displays a definite lack of understanding of the fundamentals of engineering or of profitable business.

> is a good example of a lack of soft skills.

You seek appeasement instead of understanding and you call into question my skills? I see now what you think this forum is for.

	▲	Eisenstein 21 minutes ago \| parent \| next [-]
		> I see now what you think this forum is for. Calling you out for being overly critical is not 'seeking appeasement'. I am calling your skills into question -- why shouldn't I? Your soft skills seem to consist of attacking people when you don't like what they have to say.
	▲	4 hours ago \| parent \| prev [-]
		[deleted]

▲

4 hours ago | parent | prev [-]

[deleted]