// https://www.pcg-random.org/
fn pcg(n: u32) -> u32 {
var h = n * 747796405u + 2891336453u;
h = ((h >> ((h >> 28u) + 4u)) ^ h) * 277803737u;
return (h >> 22u) ^ h;
}| $appEvents = Get-WinEvent -LogName "Microsoft-Windows-Windows Defender/Operational" | | |
| Where-Object {$_.Id -eq "1123"} | |
| $allBlockedProcesses = ( | |
| $appEvents | | |
| ForEach-Object { | |
| (([xml]$_.ToXml()).Event.EventData.Data | | |
| Where-Object { | |
| $_.Name -eq "Process Name" | |
| }).'#text' | |
| } | |
From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:
There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.
That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.
$/
artifacts/
build/
docs/
lib/
packages/
samples/
src/
tests/
| namespace YourNamespace | |
| { | |
| /// <summary> | |
| /// Uses the Name value of the ColumnAttribute specified, otherwise maps as usual. | |
| /// </summary> | |
| /// <typeparam name="T">The type of the object that this mapper applies to.</typeparam> | |
| public class ColumnAttributeTypeMapper<T> : FallbackTypeMapper | |
| { | |
| public static readonly string ColumnAttributeName = "ColumnAttribute"; |