Live data from Hacker News

Slop is not necessarily the future

greptile.com

501–510 of 512 posts

Re: Slop is not necessarily the future

#501

Earlier quoted context omitted.

> Majority of AI text, music, images, videos and code is indistinguishable and you use it every day. I really don't think this is true. If it was, we'd be able to point to countless examples of things assumed not to be AI that actually were, but there's a dearth of such examples.

Examples _are_ countless. Look around yourself - it's simply indistinguishable. Videos are still not quite there, the biggest telltale is how short they are, but we are very very close.

> Examples are countless

Then you should be able to name at least one.

Re: Slop is not necessarily the future

#502

Earlier quoted context omitted.

I think camp 1 would rather see ten useless things than one useful thing.

100% not what Camp 1 is or does. Their #1 goal is make it work. It is your #1 priority. So quite the opposite, Camp 2 will spin and make 100 "useful" (not) abstraction with the slickest imaginable code doing things you go "OMFG, how on Earth did you come up with this, insane" while during that development Camp 1 shipped 37 new features for its customers

Except one of those features has a security flaw and whoops now your entire customers file got leaked onto the darknet.

Re: Slop is not necessarily the future

#503

Earlier quoted context omitted.

I'm in camp 1 too. I've maintained projects developed with that mindset. It's fine! Your job is to make the thing work, not take on its quality as part of your personal identity. If it's harder to work with, it's harder to work with, it's not the end of the world. At least it exists, which it probably wouldn't have if developed with "camp 2" tendencies. I think camp 2 would rather see one beautiful thing than ten use…

> I think camp 2 would rather see one beautiful thing than ten useful things. Unashamedly, I would, but this is a false dilemma. We can have ten beautiful and useful things. The thing that drives the camp 2 folk crazy is that often it would have taken no extra effort (or perhaps even less effort overall) to make a good version of the thing but the people who made thing simply couldn't be bothered. The attitude you're…

>the people who made thing simply couldn't be bothered.

There is nothing I despise more than someone who doesn't care.

I remember reviewing code once, a C++ class that allocates new objects on the heap, but was lacking cleanup code to delete these objects.

"It doesn't matter if the memory leaks. Those methods rarely get called."

And he was right, during the lifetime of the application it would've likely leaked only kilobytes worth of memory. But it would've taken very little effort to write cleanup code.

I believe those that take no pride in their work will never amount for anything more than mediocrity.

Re: Slop is not necessarily the future

#504

I find most developers fall into one of two camps: 1. You treat your code as a means to an end to make a product for a user. 2. You treat the code itself as your craft, with the product being a vector for your craft. The people who typically have the most negative things to say about AI fall into camp #2 where AI is automating a large part of what they considered their art while enabling people in group #1 to iterate…

[flagged]

Re: Slop is not necessarily the future

#505

I find most developers fall into one of two camps: 1. You treat your code as a means to an end to make a product for a user. 2. You treat the code itself as your craft, with the product being a vector for your craft. The people who typically have the most negative things to say about AI fall into camp #2 where AI is automating a large part of what they considered their art while enabling people in group #1 to iterate…

> No one has ever made a purchasing decision based on how good your code is.

Another perspective: if the quality of your code has no bearing on the quality of the product, then your code/produce clearly isn't doing much useful, and perhaps we could do without it.

Re: Slop is not necessarily the future

#506
post #379

At this point I can't help but conclude that to a certain class of writers, "economic incentives" are a form of benevolent god who will surely, inevitably make things better in directions they care about, and those who believe this also believe the overwhelming and constant evidence to the contrary of their position is just a temporary anomaly Whatever the hell economics was supposed to do, right now it seems to be c…

But the free market! How could it be possible that the free market does not result in utopian society??? There MUST be a mistake

Re: Slop is not necessarily the future

#507

Earlier quoted context omitted.

Code quality is a side-effect of caring. The most important part of product design is caring at all levels. However it's caring about the external details that is the most important. Coding language is largely a function of the population of good coders in your areas. Code evolvability is almost entirely subjective.

> Code evolvability is almost entirely subjective Explain how? Code evolvability is one of the extrinsic quality markers ( https://www.pathsensitive.com/2023/07/the-11-aspects-of-good... ). If it's easy to add new features without creating bugs, the code is evolvable. Else, it's not. Does not seem very subjective.

Let's take two code bases. A 40 year old legacy Cobol monstrosity being maintained by a staff of well trained engineers that are engaged. The second an idiomatic Haskell application written simply and to the highest standards, but with a staff of junior engineers that specialize in imperative programming. The Cobol code base is much more evolvable. The staff can effectively make changes because they deeply know the product.

Evolvability is not an intrinsic feature of the software. It is a synthesis of culture, talent, passion, and code style.

Re: Slop is not necessarily the future

#508

Earlier quoted context omitted.

A safety factor of 1.0 means “the structural integrity of this construct will meet the expectations of intended use with no issues.” A safety factor of 1.7 means “if this construct is used in a way that is 70% more abusive than anticipated, the structural integrity should remain in tact.” You’re hand-waving enough here that you have the luxury of agreeing or disagreeing with me, well-played. Your initial response was…

This thread started because of "the cheapest bridge that just barely won't fail" My point was that safety factors are a part of this. A safety factor of 1.0, designing bridges so that they can perfectly withstand the expectations of intended use, means that some unacceptable % of those bridges will fall down in practice. In other words, it's true that you can explain safety factors as: > Assuming perfect construction…

Nobody in the US builds anything (permitted) with a SF factor of 1.0. Doesn't happen.

Re: Slop is not necessarily the future

#509
post #370

Earlier quoted context omitted.

"Show me your code and conceal your data structures, and I shall continue to be mystified. Show me your data structures, and I won't usually need your code; it'll be obvious." Lots of people try to make their code better by revising their procedures and don't even think about changing their data model, and generally fail. You might not be able to change your data model without changing your code, but they're differen…

Or not using the data model properly, zero foreign keys in databases, no triggers checking column contents etc. "We'll do it on the app level". sigh

No, that part is just smart. Databases have terrible support for nontrivial datastructures, doing everything at the app level is the only reasonable response.

Re: Slop is not necessarily the future

#510

Earlier quoted context omitted.

This thread started because of "the cheapest bridge that just barely won't fail" My point was that safety factors are a part of this. A safety factor of 1.0, designing bridges so that they can perfectly withstand the expectations of intended use, means that some unacceptable % of those bridges will fall down in practice. In other words, it's true that you can explain safety factors as: > Assuming perfect construction…

Nobody in the US builds anything (permitted) with a SF factor of 1.0. Doesn't happen.

Yes, because it would fall down (sometimes, often enough that regulatory bodies forbid it)
Post reply on HN