I think at least half of the software developers out there simply don't test their code in the final product (or at all). And why would they when their revision is being reviewed in a pull request?
Bug Blindness
111–120 of 263 posts
Re: Bug Blindness
#112Reading the first part of the article I thought it was about real bugs and I was like "Wow we are surrounded by hundreds to thousands of bugs a week, but are blind to them somehow".
Re: Bug Blindness
#113Does having a website with no set-width and unusable without reader mode counts as bug blindness?
Re: Bug Blindness
#114Is that why your blog is plain white text on a black background, so it's less buggy?
Re: Bug Blindness
#115Earlier quoted context omitted.
This sounds like "Smart person who has little technical experience and might have cognitive decline from age". The world is fully of people who's intelligence is legitimately lower than you might expect.
> The world is fully of people who's intelligence What an example of a sentence a person *whose intelligence is lower than you might expect would write. I can only imagine this was intentional.
Could you clarify? Are you using the typo as this basis, or something else?
Re: Bug Blindness
#116I think there are two opposite causes here: either an overly-aligned or completely unaligned mental model. For developers, bug-blindness tends to be because their mental model is so close to the system's model that both have the same blind spots, and the developer can't effectively think outside the system (the classic "QA walks into a bar, orders 0 beers, orders -1 beers, orders 0.999 beers" vs "customer walks into…
> You don't need to understand the system if you abandon the assumption that the system was designed to be understood.
This applies to software engineers too. Especially now there's claude to help them complete the tickets without understanding the system.
Re: Bug Blindness
#117I think there are two opposite causes here: either an overly-aligned or completely unaligned mental model. For developers, bug-blindness tends to be because their mental model is so close to the system's model that both have the same blind spots, and the developer can't effectively think outside the system (the classic "QA walks into a bar, orders 0 beers, orders -1 beers, orders 0.999 beers" vs "customer walks into…
It's still a wild logical leap to me that we went from this observation, that maybe the bottom half of users never learn how the software works, to the idea that we should build software that is actively learning-hostile. In the old era, we established consistent UI patterns: this kind of button does X, this kind of button behaves like Y, here are the tools to solve your problem. Maybe not everyone learned the patter…
I cynically ascribe that to a change in the market/ecosystem, from "personal computer as democratized means of production" to the (more profitable) "device we control to sell content and subscriptions to you".
Re: Bug Blindness
#118I'm with danluu on this, at least as far as the headline, and not actual details. I run into 10 to 20 software bugs a day (feels like more). If it wasn't for the all the private data I'd leak I sometimes wish I could just put my phone and computer on screen capture for a week, with input data (keyboard/mouse/touchpad/screen) and then come back and post the 100 bugs I hit that week. I've run into the MacOS one mention…
> I've run into the iOS keyboard only using 80% of the width of the phone (all the keys smaller).
Are you sure you're not triggering the compact width keyboard?
Re: Bug Blindness
#119I think there are two opposite causes here: either an overly-aligned or completely unaligned mental model. For developers, bug-blindness tends to be because their mental model is so close to the system's model that both have the same blind spots, and the developer can't effectively think outside the system (the classic "QA walks into a bar, orders 0 beers, orders -1 beers, orders 0.999 beers" vs "customer walks into…
> "Google Docs added some kind of delay such that the typing you do into the title box right after you open the doc gets overwritten"
GitHub also introduced this feature recently in the New Issue GUI.
Re: Bug Blindness
#120What does the author have a against a text size that’s readable?