Nope. It looks like you are waiting for a new Hollywood film about war in Iraq instead of reading and watching evidence. You cannot even open the Wikipedia.
So what? I can inspect downloaded code and find the backdoor, or a trojan, or an error. I did it few times already in last 30 years. If you cannot do that doesn't mean that nobody can. But I cannot do that with `curl | bash`.
GPL folks are completely OK with something like Copylot when GPL license is obeyed, so all emitted code, generated by AI trained on GPL code, is licensed under GPL again. It's not OK to call our code as «public code» and ignore our license.
Equality is very important concept in mathematics, because it allows to manipulate formulas by rules. When formulas are manipulated, it's important to keep them as small as possible, because it's hard to manipulate a wall of text. Instead of short sequence of formulas, which you can write and verify quickly, you will have lengthy books, like written by ancient mathematics.
For example, command line tools, which are used often, also have cryptic one-symbol options, like `tar xzf`, which looks like formulas, for same reason: to be able write, manipulate, and check them quickly. However, most command tools are distributed with a built-in help or manual for these cryptic options, while most formulas are not. IMHO, we need something like «formulapedia», with manuals for most popular formulas.
Spacetime is not a physical thing. It is a 4D array of measurements: `[x,y,z;t]`, a collection of frames in a simulation. It's important to simplify calculations, to predict something, but it connected to reality in same way as height field (a 2D array of height measurements) connected to Earth. Height field is just numbers, while Earth is a planet full of rock, water, sand, air, etc. You cannot study geology by studying height fields.
«Situation» in Ukraine is at mid-WWII level (1942), so plant the wheat. It will be tough to produce and export wheat in Ukraine for next two years at least.
It looks like risk planning was not done by your project manager. Risk planing includes risk prediction, calculation of possible time and/or monetary damage, risk reduction. For example, if we see that Foo can cause problem in near future with probability of 10% and can delay project with 5 members by 3-40 days, then average risk of lose is `0.1 * (40 - 3)/2 * 5 = 9.25` man-days. If we can reduce risk probability by factor of 10 by spending 2-man days of work early (1 man day of project manager + 1 man-day of a developer), then we will reduce cost to `0.01 * (40 - 3)/2 * 5 + 2 = 2.925` man-days, so 6.325 man-days are saved.
It's known as «the bus problem». Peer review is used to address this, to make someone else a bit more familiar with your code, so he will be able to help you when you are overwhelmed and need help (or when you hit by a bus). Also, built-in documentation, run books, guides, and automated test cases are very helpful for those, who are not familiar with your code base. It reduces job security tough. (I hit by that multiple times, because, for management, it feels like good developers and good administrators are doing nothing or constantly pick-up very easy tasks to do).
So you spent 40 minutes on a bug instead of whole week? Why?! Just use concise and vague descriptions of your work, like "day 1: trying to reproduce the bug", "day 2: investigating root cause of the bug", "day 3: fixing the bug", "day 4: testing the fix", "day 5: performing release of the fix", and so on. They are very short and fast to type, so you will have lot of free time to do an actual work.
SAFe is for managers, Agile is for developers. As developer, you don't need to know SAFe and it rituals. SAFe is not heavy weight, it very lean for the problem it solves.
> It somehow promises to combine bottom-up agile with top-down date-based delivery commitments then hand-waves away the collision of these intractable approaches,
It OK to fail few early goals or dead-lines until right pace will be found.
Security is a tradeoff between usability and safety. In this case, the author of ring received a suggestion from Rust security group to yank old, unsupported versions to be on the safe side, which created usability problems with ring. Security-minded people are OK with that, while security-ignorant people are not.
It looks like author of ring library tries to protect their user base from security vulnerabilities, but hit by bug(?) in cargo, which changed from warning to error for yanked libraries. Anyway, no promises until API version 1.0.
Rust doesn't have GC, but it has very good automatic memory management. GC or memory management doesn't make programs immune to buffer overflows, which is the most common security vulnerability these days, while use-after-free is at 4th place.
Moreover, I try to embedded documentation and diagnostic/debugging tools, such as meaningful error messages and traces, into code. Usually, debugging takes 3x more time than coding, so it is very profitable to reduce debugging time from the very beginning.
Also, I'm automating branching, building, testing, merging, committing, releasing procedures, so for me, it feels like a game: read a ticket, make a branch, write a test case, write the business code, update documentation, tests are OK? -> merge and commit, update resolution comments, send ticket for review and manual testing, next ticket. Of course, it works only when the whole team works the same way and each member of the team plays his/her role properly.
AI shows signs of general intelligence (e.g. can generate proper text in generated pictures) after about 20 billion of parameters. IMHO, 1 trillion of parameters can be enough to simulate human-like behaviour after reading lot of text, watching of lot of video, and playing lot of games and robotic simulations. It will be able to understand commands, understand video and audio from cameras, will be able to control equipment and robots, e.g. to repair itself, to reach a goal.
British nation and Great British Empire is not a same thing. Italians and Holy Roman Empire is not a same thing. Erzyas, Finns, Mokshas, Tartars nations, etc. and Russian Empire is not a same thing.
Native Russians (русичи, "sons of Russia"), were citizens of the town of Russia (now Old Russa, but old town was near to shore), which was on Russia river (now Porussia river). At times of Plague of Justinian, they abandoned their town and spread at large territory from the Caspian Sea to Spain. At about the same time Volyn` Kingdom, last kingdom of all Slavs, was broken into pieces, so tribes were left without a ruler. Nine eastern Slavic tribes and Russians are formed (Kievan) Russia. Later, Russia was broken into pieces (Red, White, Black Russia). Much later, Moscow kingdom captured Kyiv, so Petro I added "tsar of all Russia" to his title, then Catherine the great, born in Prussia, forbid to accept all official letters without "to Imperator of Russia" in the title, so Moscow kingdom changed it name to "Russian Empire", but instead of "R-oo-s-ia" they call themselves with foreign accent: "R-uh-ss-ee-ya". (Use Google Translate to check original pronunciation in various Western languages and in Russian language).
Trident is an anchor, symbol of Christianity, like cross or fish. The cross is the top part of an anchor, while the anchor itself is in the lower part. Anchor has such complex geometry because it weaved from wire. Similar anchors in full form can be found on some rare ancient Greek coins made in Khersones seaport (now Sevastopol). The anchor is similar to the symbol used by Rurik dynasty, so they liked it.