bobmarleybiceps
Joined 1 year ago
Joined 1 year ago
Big O is sort of like <=. little o is sort of like <.
On the other hand, I do some stuff with physics simulations and LLMs will spit out arrays like
static constexpr std::array<int, Q> cx{0, 1, 0, -1, 0, 1, -1, -1, 1};
static constexpr std::array<int, Q> cy{0, 0, 1, 0, -1, 1, 1, -1, -1};
static constexpr std::array<real_t, Q> w{ real_t(4) / 9, real_t(1) / 9, real_t(1) / 9, real_t(1) / 9, real_t(1) / 9, real_t(1) / 36, real_t(1) / 36, real_t(1) / 36, real_t(1) / 36};
static constexpr std::array<int, Q> opp{0, 3, 4, 1, 2, 7, 8, 5, 6};
and it's like ??? I know what these are for, but I have no clue if any of the numbers are right :-)
- In a lot of fields, the "deliverable" could just be a git repo. - Results could / should be more reasonable to update as possible issues arise. - Peer review is pretty busted in a lot of fields, so a humongous number of papers get through that have pretty glaring issues.
The combination of being incentivized to spew out nonsense papers + academic publishing institutions liking to get more papers to sell to libraries + government funding being partly chosen by academics who are also part of the problem.
void func(var1, var2) int var1, char* var2. { ... }
perhaps some legacy from that? Probably not, but just first thing that popped into my head since it feels similar :shrug:
(Though it could turn into "nvidia pay lots of people to use LLMs to make non-portable, tightly coupled backends to _even more_ open source projects")