The cost of "realizing"[1] a bad idea went from 10 BTC to 1M sats.
The filtering function of that barrier to entry went away and where we were previously protected by that filter, as there must have at least been a few people (investors) thinking that something were a somewhat good idea, and willing to put money to it, now there is no such barrier to entry anymore and we're exposed to everything.
The problem isn't the slopbuilders. It's our lazy asses not capable or willing to do the real research into how good a product is. Many of us still are tempted to give publicity to absolutely terrible ideas, and often worse implementations. And no, you cannot get help from a bot if you're not capable of clearly formulating what subjectively equals "good enough" for you. Also, note the usage of the word subjectively - your standards aren't mine.
So then, I think that there's a combination of [1, 4, 5] that I align with.
quoted because let's be real, most of the software we see built nowadays have both execution and architecture errors in their exponent. Iterative software engineering only works if you have been able to rid yourself of these structurally, by making a robust framework to catch them early. The basic anti-yolo narrative I'd guess. ↩
I'd rewrite
5as:The filtering function of that barrier to entry went away and where we were previously protected by that filter, as there must have at least been a few people (investors) thinking that something were a somewhat good idea, and willing to put money to it, now there is no such barrier to entry anymore and we're exposed to everything.
The problem isn't the slopbuilders. It's our lazy asses not capable or willing to do the real research into how good a product is. Many of us still are tempted to give publicity to absolutely terrible ideas, and often worse implementations. And no, you cannot get help from a bot if you're not capable of clearly formulating what subjectively equals "good enough" for you. Also, note the usage of the word
subjectively- your standards aren't mine.So then, I think that there's a combination of
[1, 4, 5]that I align with.quoted because let's be real, most of the software we see built nowadays have both execution and architecture errors in their exponent. Iterative software engineering only works if you have been able to rid yourself of these structurally, by making a robust framework to catch them early. The basic anti-yolo narrative I'd guess. ↩