When I talked about the minimal reproducible paradox in a previous post, I meant an example that other people can run or compile. That is one way to tell other people how to reproduce an issue, and it is also the easier way, because everything is contained in one example, and hopefully the issue can be reproduced in a single step. The other way is to clearly state the steps for reproducing an issue, such as this report. This requires more work of the reporter, but is also an effective way.
One common mistake, however, is that users often provide insufficient information when describing the steps to reproduce an issue. They do not intentionally omit the information, but assume the missing information is “obvious”. For example, this morning I tried hard to investigate the issue rstudio/bookdown#474, because it looked so weird to me. My instinct told me this issue could not possibly happen, because it definitely should not be the default behavior of the function. I had a hard time thinking about possible reasons (sort of like this), and tried to reproduce the issue following his steps. But I could not reproduce it.
Eventually I was told that he changed the value of a default argument, which I could not possibly figure out from the verbal description of how to reproduce the issue. Then all mysteries in my mind were gone.
So he thought it should be obvious to me that the argument took a different value. No, it was not. Please do not make this assumption when filing issues.
To clarify, I’m not blaming this user. I can totally understand it. Many users do the same thing. The problem is that there are so many possibilities for software to screw up, so you have to describe everything clearly to eliminate as many possibilities as possible.
Donate
As a freelancer (currently working as a contractor) and a dad of three kids, I truly appreciate your donation to support my writing and open-source software development! Your contribution helps me cope with financial uncertainty better, so I can spend more time on producing high-quality content and software. You can make a donation through methods below.
-
Venmo:
@yihui_xie, or Zelle:xie@yihui.name -
Paypal
-
If you have a Paypal account, you can follow the link https://paypal.me/YihuiXie or find me on Paypal via my email
xie@yihui.name. Please choose the payment type as “Family and Friends” (instead of “Goods and Services”) to avoid extra fees. -
If you don’t have Paypal, you may donate through this link via your debit or credit card. Paypal will charge a fee on my side.
-
-
Other ways:
WeChat Pay (微信支付：谢益辉) Alipay (支付宝：谢益辉) 
When sending money, please be sure to add a note “gift” or “donation” if possible, so it won’t be treated as my taxable income but a genuine gift. Needless to say, donation is completely voluntary and I appreciate any amount you can give.
Please feel free to email me if you prefer a different way to give. Thank you very much!
I’ll give back a significant portion of the donations to the open-source community and charities. For the record, I received about $30,000 in total (before tax) in 2024-25, and gave back about $15,000 (after tax).