The assumption is that they almost certainly did not have the sample size to justify two decimal places. If they want two decimals for aesthetics over properly honoring significant figures then it calls the scientific rigor into question.
But they say "26.08% increase (SE: 10.3%)", so they make it clear that there's a lot of uncertainty around that number.
They could have said "26% (rounded to 0 dp)" or something, but that conveys even less information about the amount of uncertainty than just saying what the standard error is.
They could still have gone for one decimal. Or possibly even none, considering the magnitude of the SE, but I get that they might not want to say "SE: 10%".
The second decimal point doesn't essentially add any information because the data can't provide information at that precision. It's noise but being included in the summary result makes it implicitly look like information. Which is exactly why including it seems a bit questionable.
That's not the major issue with the study, though, it's just one of the things that caught my eye originally.
Heyo appreciate the kind words! I'm Daniel, Kiet's cofounder. The animation was a free component built by Nandi (https://twitter.com/learnframer) at LearnFramer. I can only pretend to be as creative as him – definitely check out his stuff.
You're missing the parent's point. It's not about lacking a change control process, but about having the ability to instantly change the state of a flag when necessary. Moreover, these two can coexist effectively.
With Continuous Delivery you should be able to roll back the deployment. If the last change is the only one you need to revert. Of course that stops working when you share the flag system across teams with separate milestones. Your guys are gonna want to flip toggles while my guys are thinking about flipping others.
2. At runtime, I use the material-color-utilities library[1] to generate a whole color theme based on that one root color. The applyTheme method puts the theme into CSS variables on the body like --md-sys-color-primary: #c72320; and so on for each color token.
3. In tailwind.config.js I set the colors to point to those variables, for example "primary": "var(--md-sys-color-primary)", and so on for the rest of the colors.
Using this approach I can remap colors at runtime for whole subtrees by simply overriding the CSS color variables.
You might want to look into using giscus[1] for a commenting system on your blog. All it needs is a public GH repository to host the discussions, after which you simply embed a script into each blog post, and visitors will be able to leave a comment using their GH account.
reply