> Software written by people that don't use the software themselves. It has happened to me so many times, I come across a piece of software with weird bugs or interactions that would be immediately fixed if the developer just spends 5 minutes using the software like an end user would. Dogfood all the things!

My experience is completely contrary: developers typically do care deeply about such things. The problem is rather that very commonly managers actively disallow these poor developers to apply their diligence to the software that they develop.

I really have a strong feeling that you want to participate in the ugly vendetta against software developers that has been going on for decades ("Replace all software developers"; current season: "Replace them with AI").

Don't do that. Rather fight the people who are really responsible (who are often (project) managers or Scrum masters).

I write software that we use daily, and we still find things in the wild that we would never find until the thing in the wild occurs. Luckily for me, none of these found in the wild issues interfere with people's lives and just means a file gets completed a little closer to the deadline. I'm fine with that.

Not sure if this situation falls under the "push it to prod and let the users QA it" or if this is truly edge case situations. It's easy to bash and make fun of, but I've been in the trenches of catching what is an edge case for most people but run of the mill for those providing the data to me.

I’ve been in the weird situation of working in a startup where the founder doesn’t use their own product. Needless to say I got out of there pretty quick.