As a consumer of software, everywhere you look, there’s slow software that the creator is claiming is fast because the creator is touting some slop benchmark, e.g., here’s one of multiple examples I saw yesterday, and of course low-quality software that doesn’t work is more common than ever.
But, as a builder of software, it doesn’t matter that almost all of these projects are vibeslop, that other people are out there shoveling out huge piles of crap and calling it gold. You can build things like pgrust or other projects that would’ve been too large to really be feasible in the past and, if you do a reasonable job with testing and benchmarking, that stuff can actually be good-enough quality to use.
If I were writing it, I would say “we can be more ambitious with the software we build” and not “we should”, but Malis has been casually chatting with me when he’s said this, so maybe he would say the same in an actual post; don’t read too much into should vs. can here. What’s interesting to me is how capabilities have advanced such that we can do a lot more.
Want to know when stuff like this is published?
Sign up for my email list.
About JUSTIN HARTER
Justin has been around the Internet long enough to remember when people started saying “content is king”.
He has worked for some of Indiana’s largest companies, state government, taught college-level courses, and about 1.1M people see his work every year.
These days he lives and works in West Michigan.