Slop is not necessarily the future
greptile.com
Slop is not necessarily the future
1–10 of 512 posts
Re: Slop is not necessarily the future
#2Re: Slop is not necessarily the future
#3The 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.
Re: Slop is not necessarily the future
#4Re: Slop is not necessarily the future
#5Re: Slop is not necessarily the future
#6[flagged]
Re: Slop is not necessarily the future
#7Re: Slop is not necessarily the future
#8Good 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.
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 does not matter as much.
Re: Slop is not necessarily the future
#9People forget that good engineering isn't "the strongest bridge", but the cheapest bridge that just barely won't fail under conditions.
Re: Slop is not necessarily the future
#10If "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 if we built things that are meant to last? Would the world be better for it?