[HN Gopher] One Week of Bugs (2014)
___________________________________________________________________
One Week of Bugs (2014)
Author : defaulty
Score : 81 points
Date : 2021-08-27 16:38 UTC (6 hours ago)
(HTM) web link (danluu.com)
(TXT) w3m dump (danluu.com)
| dhosek wrote:
| The iOS mail app has had the inbox bug for years, where it
| displays the unread messages app before it downloads the messages
| and sometimes retains it after the messages have been read.
|
| That said, some bugs in Music that I thought would never get
| fixed (they were there for years also), did eventually get fixed,
| so I can keep some semblance of hope.
| dbt00 wrote:
| (2014), I believe.
| thetwentyone wrote:
| Looks like that's correct though things have been reorderd
| since the original:
| https://web.archive.org/web/20141202041102/https://danluu.co...
|
| Without that context, some of the criticisms seem unfair (like
| Julia being version 0.3 and rapidly iterating; 4 years before
| its late 2018 1.0 release).
| dang wrote:
| Added. Thanks!
| brian_cloutier wrote:
| Even if you don't intend to publish your list I highly recommend
| keeping a note of every bug you run into.
|
| Once you're looking for bugs you'll start to notice them
| everywhere. I've built up a lot of habits around reloading and
| restarting various screens on my phone that were completely
| invisible to me until the list I was keeping caused me to start
| paying attention:
| https://twitter.com/bmc_/status/1309209159695388672
| dang wrote:
| A couple of small past threads:
|
| _One Week of Bugs (2014)_ -
| https://news.ycombinator.com/item?id=22094844 - Jan 2020 (5
| comments)
|
| _Why is software so buggy?_ -
| https://news.ycombinator.com/item?id=15838200 - Dec 2017 (1
| comment)
| jjoonathan wrote:
| Bug amnesia is very real! As technologists, I feel it is
| important for us to cultivate the skill of noticing and
| remembering bugs, because the default seems to be that we apply
| all of our expertise and faculties to develop workarounds and
| then we internalize the workarounds and forget about the bugs.
| This is fine for lone-wolf tasks but leads to all sorts of
| mismatched expectations in groups.
|
| Installing linux is my go-to example. To the intuition of a
| typical technologist, it's a trivial and highly reliable task.
| Whenever I go through the exercise in TFA and force myself to
| actually pay attention to the places where I must apply expertise
| to work around issues that would otherwise be extremely difficult
| to navigate, I usually count around 5 showstoppers and a dozen
| minor bugs. Things like "the install instructions say to hold
| down F2 or F10 to get into the BIOS, but per the blink-and-
| you'll-miss-it BIOS info page it's actually F11 and if you
| actually hold it down the stuck-key detection ignores it so you
| have to spam-press the key instead." The world is full of these
| things and it's easy to lose sight of them if you don't force
| yourself to remember.
| [deleted]
| jraph wrote:
| Sorry for the curse, but...
|
| > and if you actually hold it down the stuck-key detection
| ignores it so you have to spam-press the key instead
|
| Fuck this shit. How many pointless boots I triggered just
| because I could not manage to get the right key to be pressed
| at the right time? This is so pointless, so much time lost on
| this for nothing.
|
| Just show the one key I should press at what time and give me
| feedback when you understood I wanted to do this.
|
| Now my strategy is to spam the whole Esc + Fn keys row and
| delete, rinse, repeat until it computes.
| yjftsjthsd-h wrote:
| Something I really love about thinkpads is that they have
| that big blue "thinkvantage" button at the top of the
| keyboard, which is totally tacky 99% of the time, but! when
| you want to get to firmware configuration, you _know_ what
| button to hit.
| jraph wrote:
| I've seen such a key on a Sony Vaio. The label was nothing
| but explicit, I actually had to look for help. But the
| button would turn the computer on, and get to the setup
| menu. Nice touch. Obviously, it was the only nice thing
| about this terrible machine but that's a different story.
| ChrisMarshallNY wrote:
| At first, I thought he was writing about bugs in his own software
| (reported issues, on which he is the assigned engineer).
|
| He's talking about bugs that he encounters, using everyone else's
| software.
|
| Yeah, this was written years ago, but it looks like things have
| not improved with age.
|
| https://youtu.be/dO9nxRjIv2A?t=90
| jldugger wrote:
| IMO, this post takes a left turn off the freeway when it segues
| into fuzz testing. Those are super effective, no doubt, but I've
| come to the conclusion that finding bugs isn't the hard part.
|
| Dan even admits fixing them is the hard part:
|
| > why don't you fix the bugs yourself? I do fix some bugs, but
| there literally aren't enough hours in a week for me to debug and
| fix every bug I run into.
___________________________________________________________________
(page generated 2021-08-27 23:00 UTC)