When IT folks say devs don’t know about hardware, they’re usually talking about the forest-level overview in my experience. Stuff like how the software being developed integrates into an existing environment and how to optimize code to fit within the bounds of reality–it may be practical to dump a database directly into memory when it’s a 500 MB testing dataset on your local workstation, but it’s insane to do that with a 500+ GB database in production environment. Similarly, a program may run fine when it’s using a NVMe SSD, but lots of environments even today still depend on arrays of traditional electromechanical hard drives because they offer the most capacity per dollar, and aren’t as prone to suddenly tombstoning when it dies like flash media. Suddenly, once the program is in production, it turns out that same program’s making a bunch of random I/O calls that could be optimized into a more sequential request or batched together into a single transaction, and now it runs like dogshit and drags down every other VM, container, or service sharing that array with it. That’s not accounting for the real dumb shit I’ve read about, like “dev hard coded their local IP address and it breaks in production because of NAT” or “program crashes because it doesn’t account for network latency.”

Game dev is unique because you’re explicitly targeting a single known platform (for consoles) or targeting for an extremely wide range of performance specs (for PC), and hitting an acceptable level of performance pre-release is (somewhat) mandatory, so this kind of mindfulness is drilled into devs much more heavily than business software dev is, especially in-house dev. Business development is almost entirely focused on “does it run without failing catastrophically” and almost everything else–performance, security, cleanliness, resource optimization–is given bare lip service at best.

Why make a better UI when it’ll probably introduce a slew of new bugs?

I think it’s because Spotify frequently includes the same song as being on multiple albums separately–for example, if a band has a greatest hits album, Spotify considers the greatest hits album as a different song, even though it’s identical to the song on the original album.

You know it’s coming. Why would a streaming company want a consumer buying one month, binging a single show they’re interested in, then immediately cancelling the subscription after, when you could guarantee a 6- or 12-month revenue stream for them?

It’s free*, insanely easy to set up, you don’t have to worry about port forwarding or ddos or hosting fees, has powerful moderation tools, and there’s a plethora of easy to deploy bots that help manage permissions and automate routine tasks. Literally, if it had a proper web-accessible forum similar to phpBB, it would be perfect.