✦ YOUR BLOG, YOUR RULES ✦ FEDERATED & FREE ✦ NO ALGORITHMS, JUST VIBES ✦ OWN YOUR CORNER OF THE WEB ✦ ACTIVITYPUB + ATPROTO ✦ TAKE YOUR FOLLOWERS ANYWHERE ✦ THE WEB IS YOURS AGAIN ✦    ✦ YOUR BLOG, YOUR RULES ✦ FEDERATED & FREE ✦ NO ALGORITHMS, JUST VIBES ✦ OWN YOUR CORNER OF THE WEB ✦ ACTIVITYPUB + ATPROTO ✦ TAKE YOUR FOLLOWERS ANYWHERE ✦ THE WEB IS YOURS AGAIN ✦   

Slop too fast

by eeg and chreese

The thing about slopcoding is that you can build an entire app like this without caring about what the point is. Who is it for? Who cares! Whereas coding by hand slows your mind enough for it to meander. New ideas naturally come to you while in the process of coding whatever's in front of you.

And then your time on earth isn't infinite, so before setting down the path of building that really neat feature, you ask, “Do I even need this feature? Will anyone actually use it?” And then you hone your vision for the product in real-time, as you're making it (if you're doing this kind of cowboy coding to begin with).

This isn't that surprising – we all know AI rots brains. But in this way, slopcoding again quietly undermines the process of product-making. While making the creation of (slop)code near-frictionless, it vastly increases friction for thinking through code.

Comments