If "good code" == "useful code", then yes. People forget that good engineering isn't "the strongest bridge", but the cheapest bridge that just barely won't fail under conditions.
What would happen if we made bridges to last as long as possible, to withstand natural disasters and require minimal maintenance? What if we built things that are meant to last? Would the world be better for it?
Slop is not necessarily the future
11–20 of 512 posts
Re: Slop is not necessarily the future
#12Re: Slop is not necessarily the future
#13Good code wasn't winning even before the ai slop era! The pattern was always: ship fast, fix/document later, but when "later" comes "don't touch what is working". To date nothing changed yet, I bet it won't change even in the future.
I was told by an exec...once a company or technology implements something and gets mindshare, the community (including companies) moves on. Competition is essentially dead for that segment given there is always outward growth. With that being said, AI enables smaller players to implement their visions with enough completeness to be viable. And with a hands off approach to code, the underlying technology mindshare doe…
Re: Slop is not necessarily the future
#14If "good code" == "useful code", then yes. People forget that good engineering isn't "the strongest bridge", but the cheapest bridge that just barely won't fail under conditions.
That can't be right? What about safety factors
Re: Slop is not necessarily the future
#15If "good code" == "useful code", then yes. People forget that good engineering isn't "the strongest bridge", but the cheapest bridge that just barely won't fail under conditions.
What would happen if we made bridges to last as long as possible, to withstand natural disasters and require minimal maintenance? What if we built things that are meant to last? Would the world be better for it?
Re: Slop is not necessarily the future
#16If "good code" == "useful code", then yes. People forget that good engineering isn't "the strongest bridge", but the cheapest bridge that just barely won't fail under conditions.
> the cheapest bridge that just barely won't fail That can't be right? What about safety factors
Re: Slop is not necessarily the future
#17Re: Slop is not necessarily the future
#18If "good code" == "useful code", then yes. People forget that good engineering isn't "the strongest bridge", but the cheapest bridge that just barely won't fail under conditions.
What would happen if we made bridges to last as long as possible, to withstand natural disasters and require minimal maintenance? What if we built things that are meant to last? Would the world be better for it?
You'd have a better bridge, at the expense of other things, like hospitals or roads. If people choose good-enough bridges, that shows there is something else they value more.
Re: Slop is not necessarily the future
#19If "good code" == "useful code", then yes. People forget that good engineering isn't "the strongest bridge", but the cheapest bridge that just barely won't fail under conditions.
What would happen if we made bridges to last as long as possible, to withstand natural disasters and require minimal maintenance? What if we built things that are meant to last? Would the world be better for it?
We only recently figured out how to reproduce Roman concrete.
We’d have more but a lot were blown up during WWII.