What is concerning to me is how many people in this comment section have little to no reading comprehension if they even read the site at all. The site is clear of what exactly they are calculating and how (in a specific and narrow way - whether you agree with it or not).
There should be some kind filter/litmus test to prevent people commenting here if they didn't view/read the site first [1]. It will save the rest of us some time reading alot of these garbage comments[2].
[1]: yes I know this is hard problem to solve (if solvable at all), but my general point stands. HN comment quality is steadily degrading because people cant be bothered to RTFA
[2]: Probably should just stop coming here in the first place
> Few engineers could reliably build the software locally; debugger usage was rare (I ended up writing the team's first how-to guide in 2024); and automated test coverage sat below 40%.
A key clue and explains why so much of what Microsoft puts out is garbage. Wow.
No, the OP is right in this case. Did you read TFA? It was "peer reviewed".
> Worryingly, each of these submissions has already been reviewed by 3-5 peer experts, most of whom missed the fake citation(s). This failure suggests that some of these papers might have been accepted by ICLR without any intervention. Some had average ratings of 8/10, meaning they would almost certainly have been published.
If the peer reviewers can't be bothered to do the basics, then there is literally no point to peer review, which is fully independent of the author who uses or doesn't use AI tools.
Yeah, this is not a new concept and I remember seeing one of his videos that explains this concept really well. Here the relevant video from 9 years ago for those uninitiated:
No please don't do this. I have lost count how many times I tried to follow a link only to get a 404 page. If there is an issue where the app gives the user an error, show the error details & context directly and list the possible mitigation steps right then and there.
A URL with specific content is just another thing that now needs to be maintained along with the code and failure modes.
This is easily bypassed and/or worked around. What is to prevent an indefinite investigation? The FBI D.B Cooper case was open for decades, for example.
The flash is QSPI, so its not really on die flash with a real flash controller. There is some QSPI cache but it’s really a band-aid solution to not having the real thing. People around the net don't seem to understand the difference and it can be very misleading.
I use "Todo Tree" in VS Code which is one of my mandatory extensions wherever I go. Super useful for not only tag highlighting, but as a general bookmark system inside the codebase.
I also find this super annoying. In C++ land, Microsoft solves this problem by having "natvis" [0] files which allows you to have custom representations of complex & deeply nested objects. Unfortunately, most third-party debuggers don't support it. And like you said, any non-trivial program in Rust is basically not parsible without digger though 50 layers of nested abstractions.
Slightly off topic: Does anyone know of a good/fast hash function (similar to this) for use in 32bit embedded systems (such as Cortex-M, TriCore, C2000, etc)?
Linux will never get popular in the mainstream until the Linux community ditches the obsession with doing things through the command line. The second you need to open the terminal to do something useful, you already lost.
There are many reasons why Linux is not popular, but the over reliance on commandline is a obvious one I rarely hear people mention.