4 ms·

> You're finding bugs because you're using the language like a QA tester instead of the way its intended. What do you think this means? Are the bugs there or n

> You're finding bugs because you're using the language like a QA tester instead of the way its intended. What do you think this means? Are the bugs there or not?

fragmede 1y ago
Not all bugs are equal though, and if I'm only going to run across the bug when I'm standing on my head the third Wednesday of the month while singing Poker Face, it's a bit less concerning than one that happens only on days that end in "Y".
- happytoexplain 1y ago
  So we shouldn't learn about them? They're offensive to enumerate? No, they're useful to understand.
  - fragmede 1y ago
    So we should put them into the bug tracking system and prioritize them accordingly. They're very useful to understand, but if one costs $100 every time it happens but it only happens once a year, vs a different bug that costs $1 every time it gets hit, but it happens every day, which one should get fixed first?
- motorest 1y ago
  I think you're showing some despair in trying to avoid addressing the fact that there are indeed bugs. There is nothing suggesting bugs are obscure or random. You have a list of examples. Is it hard to acknowledge the problems are there? What exactly makes you feel threatened or personally attacked by a bug tracker?
  - fragmede 1y ago
    I think you're reading a lot more emotion than exists into my comment. Despair? lol I'm just pointing out that QA testers (and good ones are worth their weight in gold) find bugs by doing things must users wouldn't even consider doing. https://news.ycombinator.com/item?id=25851770 https://news.ycombinator.com/item?id=25851770
FreakLegion 1y ago
Which ones are bugs? I read the first few sections and glanced through the rest, but it's a long notebook. There were runtime-specific implementation details, operator precedence, genuine language footguns (like scoping rules), but no bugs that I saw.

4 ms·

> You're finding bugs because you're using the language like a QA tester instead of the way its intended. What do you think this means? Are the bugs there or n

by motorest 1y ago

> You're finding bugs because you're using the language like a QA tester instead of the way its intended. What do you think this means? Are the bugs there or not?

fragmede 1y ago
Not all bugs are equal though, and if I'm only going to run across the bug when I'm standing on my head the third Wednesday of the month while singing Poker Face, it's a bit less concerning than one that happens only on days that end in "Y".
- happytoexplain 1y ago
  So we shouldn't learn about them? They're offensive to enumerate? No, they're useful to understand.
  - fragmede 1y ago
    So we should put them into the bug tracking system and prioritize them accordingly. They're very useful to understand, but if one costs $100 every time it happens but it only happens once a year, vs a different bug that costs $1 every time it gets hit, but it happens every day, which one should get fixed first?
- motorest 1y ago
  I think you're showing some despair in trying to avoid addressing the fact that there are indeed bugs. There is nothing suggesting bugs are obscure or random. You have a list of examples. Is it hard to acknowledge the problems are there? What exactly makes you feel threatened or personally attacked by a bug tracker?
  - fragmede 1y ago
    I think you're reading a lot more emotion than exists into my comment. Despair? lol I'm just pointing out that QA testers (and good ones are worth their weight in gold) find bugs by doing things must users wouldn't even consider doing. https://news.ycombinator.com/item?id=25851770 https://news.ycombinator.com/item?id=25851770
FreakLegion 1y ago
Which ones are bugs? I read the first few sections and glanced through the rest, but it's a long notebook. There were runtime-specific implementation details, operator precedence, genuine language footguns (like scoping rules), but no bugs that I saw.