There is the notion of equitable estoppel, that would *perhaps*, depending on the facts, apply which stops a defendant, who for instance concealed or committed certain acts of fraud, from raising the statute of limitations defense.
The paper is _the_ reminder of the promises we owe to future selves and generations. Its value lies in the People's strength to enforce it by exercising the obligations and rights it describes.
In some (EU) countries, as a public officer/agent you can actually get prosecuted (civil or criminal proceedings per case), in cases of blatant or willful incompetence. (Think of the levels of gross wanton disregard/negligence.)
(There is also the legal vehicle of insubordination.)
The bar is high, of course, and yet people have historically managed to get prosecuted, lose their jobs, and go to prison.
I think the problem in the U.S. is, ironically, the power of police unions in a fragmented police force (city, territory, county, etc.) ecosystem, coupled with the lack of unified, express state and federal statutes to enforce a standard of care and competence.
Add to that that peace officer-specific state statutes (e.g., describing manslaughter while on duty) are written in such a way that, as a matter of law, it becomes a herculean task to tick all the boxes to successfully preserve a conviction on appeal. It is truly troubling. (I am hopeful, as this can be solved by the U.S. legislature, which I think we have a lot of reasons to demand to be done.)
100% this: if you go every axis of what differentiates staff from senior one will see deep down it is about asking questions: either yourself or helping others ask the right questions (e.g. mentoring, impact/are we solving the right problem, etc.)
It used to be illegal to bribe. Used to... Make a law impossible to enforce, and you suddenly transform the act to a totally legal one, at the expense of people losing trust in the system (specifically the U.S. Supreme Court and Congress). And at some point, the system breaks.
I had the same question, but I can only speculate at the moment.
The cynical part of me thinks in a similar line: create an artificial differentiation and push people to upgrade.
If anyone has any real clues that they can share pseudonymously, that would be great. Not sure which department drove that change.
This. The industry is a hot-pot of gut feelings/seat of my pants mixed with true engineering and mathematical rigor.
It is all hit or miss. Everyone claims they do high-quality, critical software in public, while in private, they claim the opposite, that they are fast and break things, and programming is an art, not math.
And then you have venture capital firms now pushing "vibe coding."
Software development is likely the highest variance engineering space, sometimes and in some companies, not even being engineering, but "vibes."
It is interesting how this is going to progress forward. Are we going to have a situation like the Quebec Bridge [https://colterreed.com/the-failed-bridge-that-inspired-a-sim...]. The Crowdstrike incident taking down the whole airspace proved that is not enough. Market hacks in "decentralized exchanges," the same. Not sure where we are heading.
I guess we are waiting for some catastrophe that will have some venture capital liable for the vibe coding, and then we will have world wide regulation pushed on us.
Veteran Cryptographer and Distributed Systems Engineer with multiple large-scale, high-value distributed systems delivered. (incl. byzantine fault tolerance & consensus protocols.) Experience bringing secure and private machine learning to production, from low-level code to engaging B2B customers and directing projects on a global scale (U.S., Europe, Asia). Passionate about leading, mentoring, and providing high-impact.
I agree. [Unless fully adopted by a serious game engine, of course.]
Rust's "superpower" is substituting critical C++ code in-place, with the goal of ensuring correctness and soundness. And increasing the development velocity as a result.
This comment might not be liked by the usual commenters in these threads, but I think it is worth stressing:
First: I have experience with Bevy and other game engine frameworks; including Unreal. And I consider myself a seasoned Rust, C etc developer.
I could sympathize with what was stated by the author.
I think the issue here is (mainly) Bevy. It is just not even close to the standard yet (if ever). It is hard for any generic game engine to compete with Unity/GoDot. Nevermind, the de facto standard of Unreal.
But if you are a C# developer and using Unity already, and not C++ in Unreal, going to a bloated framework that is missing features that is Bevy makes little sense. [And here is also the minor issue, that if you are a C# developer, honestly you don't care about low level code, or not having a garbage collector.]
Now if you are a C++ developer and use Unreal, they only point to move to Rust (which I would argue for the usual reasons) is if Unreal supports Rust. Otherwise, there is nothing that even compares to Unreal. (That is not custom made game engine.)
Edit: to augment the sibling comment.