I'm just going to answer this one candidly. Yes, you are doing something wrong. Immediately: the commit history is useful to understand the context in which a bug was introduced, because it's the best context to understand the _reason_ the mistake was maybe, which is a really good way to prevent regressions. But more generally: when an entire industry has arrived at an accepted practice, you the junior developer (sorry, 5 years is _nothing_: you need to be told this too) have a chance to pick up on it.
Have you heard "have you played guitar for 20 years, or have you played guitar 20 times for a year?" Time only helps with accumulating wisdom if you let it.
You're right that I can't reproduce it like a phone camera could, and that the more precise you are the better (and it might be that with my eyes closed I'm doing something closer to addition in log-odds, like a separate comment responded), but this is super useful even coarsely. The visual affordance gives Bayes's theorem a physicality unlike any other tool I've found.
Seriously, though, there's one nomogram you (yes you) should know about and have it well-enough engraved in your mind's eye that you can use it with eyes closed. A nomogram for Bayes' theorem: https://www.ovid.com/journals/nejm/abstract/10.1056/nejm1975...
If you stare at the CYK algorithm long enough and see it for the dynamic programming approach it is, you'll then realize that you can do the same parallelization trick for any context-free grammar!
CRAN has very different social structures and culture than other languages' package repos. CRAN _will_ pull your package from the repository if you fail to play nice with all packages, for example. This is evidently controversial, but it's accepted practice and one possible explanation for why CRAN feels more cohesive than NPM or PyPI.
(People might not know the inside joke here, namely that WotC has in the past sent the actual Pinkertons after some people suspected of leaking unreleased cards)
I want to point out that you are posting from a 5-months old account (squarely within a time frame where LLM-powered accounts would be created), with an UUID-sounding username, claiming a 10-year-old professional history in the field, and using those credentials to bring up the possibility that a 14-year-old account claiming to be an MD with `md` in the username and _lots_ of comments is LLM-generated and asking for skepticism.
It's not particularly helpful; you could easily have done the 5 minutes of work.
Yes! That "prefeitura do Rio" huggingface URL is definitely shocking to read to this Brazilian as well (I'm assuming you and parent also are from your usernames).
I know this is irrelevant on the grand scheme of things, but that WebGL animation is really quite wrong. That is extra funny given the "ensure it has realistic orbital mechanics." phrase in the prompt.
I prescribe 20 hours of KSP to everyone involved, that'll set them right.
(Disclosure: I work on https://quarto.org, for the same company that the author of WebR works on) Thanks for sharing that PDF link. It's so good! Would you be willing to write a bit about how you produced that PDF? It's a great example of what places like CIDR should be encouraging in terms of academic publications.
(FWIW, I'm the technical lead on the Quarto project)
RMarkdown isn't going anywhere! Quarto exists to bring the RMarkdown experience that folks love to a broader set of users and contexts. It is true that we try to keep the .qmd experience in Quarto pretty close to the .rmd experience in RMarkdown, and it is true that Quarto does things that RMarkdown never will. But it's not the case that "RMarkdown is being phased out and replaced with Quarto".
This is the kind of task that LLMs are precisely terrible at; there isn't an abundance of Zod 4 examples, and the LLM will sure as shit will give you _something_ you are now by definition ill-equipped to assess.
I'm confident about this assessment because I maintain a large-ish piece of software and perenially have to decipher user reports of hallucinated LLM syntax for new features.
(I imagine you agree, so this is just to expand) a secondary, insidious issue is that administrators diffuse their rules through the bureaucracy. In the case of CS, you start seeing references to csrankings in recommendation letters for grad applications, faculty applications, or even tenure letters. At that point, it can be hard to fight against it.
(Context: I’m an IC and told my
Manager multiple times that I’d quit if they ever make me a manager)
If you truly believe that, please do yourself a favor and read “The tyranny of structurelessness” to understand what a managerless place becomes. everyone and no one becomes a manager, and there’s no explicit avenue of recourse. There’s a good reason management arises. We can discuss good management vs bad management, but pretty fundamentally there’s no such thing as “no management”.
https://cscheid.net https://github.com/cscheid https://bsky.net/profile/cscheid.net