I'm fairly new to smoking and am about to do my first bacon. I'm looking at the amazingribs bacon recipe for a 1 3/4 inch thick 3 pound belly. It says to cure in the refrigerator for 3-4 days, but when I use the amazingribs "Calculator" it indicates only 1.5 days. Most other websites talk about 5 to 7 days or even longer. This is confusing. Could someone give me some guidance?
Thanks
1.5 days seems like not enough to me. Did you get your ppm of nitrite in properly? I had that pop on me a couple times and re-entered and then it was better.
I'm sure more experienced folks will be along in a bit to give some more advice. Looking forward to learning along with you.
Last edited by Sweaty Paul; February 20, 2021, 05:52 PM.
Ok, I see the problem. You HAVE TO move the PPM slider. You can move it back to 125ppm, but if you don't move it to a new value, it doesnt see the ppm value and calculate correctly. Once I did that, it gives 4.1 days.
A UI that relies on people reading everything is not well designed, though. To the user, It appears a value is set, but if the form doesn't actually read it until you move the slider... that's a code/UI issue; you should not need to adjust it if you actually want that setting.
Also, there's no reason for it to be a slider. Like everything else, it should just be a text box, though I understand that the slider keeps people from typing "125ppm" in.
If you enter in values and hit tab (or click to the next form field to enter something there), you get to the thickness value.
If you then type in 1.75 for the thickness (in this case) and simply scroll down without hitting tab, you see 1.4 days because it hasn't picked up the new value of 1.75. it's still using the default value of 1.
If you hit tab, it enters the value of 1.75 and updates correctly.
Basically, it's reading values when the focus changes from one form field to the next. But the thickness field is the last one and there's no reason for the user to hit tab to get to a new field or to click anywhere.
The problem is that since there are default values, the calculator returns a result using those which is fine, until you get to the last field.
There are two possible solutions:
1. Leave the values blank in each form field so that it cannot calculate a result (and thus show a confusingly incorrect result) and read the new value on change (i.e. when the value is changed, even if the user never tabs to a new field).
OR
2. Add a "Calculate it!" button that updates the form with the new values and calculates a result.
Last edited by rickgregory; February 20, 2021, 07:17 PM.
Interesting. I tried it on safari and chrome on my Mac. Didnt try the iPhone.
If I were building that, I'd simply leave the fields blank and read values on change, vs having default values that will almost certainly need to be changed anyway
You seriously need to make this bacon. It's not hard. And it is so worth it. It's one of those processes that mostly just takes time. And for your patience you are rewarded with some the most delicious, homemade smoky bacon you'll ever taste.
Bacon
Comment