I once asked my brother in law (a mechanic) to help me look over and buy a new secondhand car. The car we ended up buying had good fundamentals, low cost, good brand, big trunk, high top speed.

After owning it for a while, I came to learn that it was not a great car. Things constantly broke and the repairs cost me more overall than the cost of the car. A complete disaster.

I came to realise that to a mechanic, little problems like an old fuel pump or poorly maintained engine were "easy" problems to fix. To my brother in law, what mattered was the low price and the fundamentals. Repairs, to him, were easy. To me (not a mechanic) they were expensive and inconvenient.

I think, for a developer, problems with software are a bit like this. Little things that are easy to fix can be overlooked because the grand design of the system is very clever or it has some advantage over other software like handling a particular file format, or processing a high volume of transactions.

Personally, I find it very difficult to sit down and expend the attention and effort to really look at and test my own software. I think because every little issue that I see becomes another job, another hassle, another delay in releasing. Maybe thats my "Bug Blindness", not sure if it's the same.

That is the reason why too many nerds recommended Linux as a "easy" windows alternative. What for us is easy to fix and often not even worth thinking about it, is impossible for a normal person.