611 karma · joined January 15, 2023
He clearly wrote it the way he did to invite an easy, comfortable interpretation, one that is blatantly contradicted by the very evidence he presents. He's rubbing our noses in our own gullibility and tendency to deceive ourselves with comfortable lies, just as the narrator has done.
All in simple, direct language. Frost sure was a sneaky one.
I reached out to a guy on 23andMe that was a DNA relative (2nd cousin) and said hi. Curious how we were related, I gave him some family names going several generations back, and asked if any of them rang a bell in his family history.
He responded quickly and said no, they did not.
Then a few weeks later I get another response. He said that one of the names had faintly rung a bell, and when he dug into it, it turned out that was the name of his mother's boss for much of her career as a secretary. His heart sank when he realized it. He and his siblings did genetic tests and confirmed that he, the youngest, was only a half-sibling. Both of the parents were deceased so there's no way to know what really happened.
After dropping that bomb in the poor guy's lap I stopped using the DNA Relatives feature.
Peter would also show up at Indian Rock sometimes, a popular outdoor climbing spot in Berkeley. He was an incredibly good climber and a friendly guy to boot. It took me a fair number of years to realize that the outgoing guy at Indian Rock was actually the founder of City Rock!
He's one of those who seems to get a lot of satisfaction from building something cool and inspiring people, without much regard for money and traditional status. We could use more people like that.
You have a choice: Fight the borrow checker on the front end until your code compiles, or chase down bugs on the back end from undefined behavior and other safety problems. No single answer there, it depends on what you're doing.
Cognitive load is a big issue. In Rust I find this comes in a couple of phases, the first being figuring out what the borrow checker does and how to appease it. The second is figuring out how to structure your data to avoid overusing clone() and unsafe blocks. It's a bit like learning a functional language, where there's a short-term adaptation to the language, then a longer-term adaptation to how you think about solving problems.
You mention doubly-linked lists, which are a good example of a "non-star" data structure that doesn't nicely fit Rust's model. But: for how many problems is this the ideal data structure, really? They're horrible for memory locality. Those of us who learned from K&R cut our teeth on linked lists but for the last 20 years almost every problem I've seen has a better option.
I can also empathize with those who consider him a whiny brat. It's hard to get someone to care about your plight when in their eyes you've achieved success. It's just different levels on Maslow's hierarchy.
Maximum number of moves scales as n^2.
Ah, you say: But such jobs don't employ many people! Most people do things that nobody cares if they're automated away. Surely we can't all be chess players or artists?
To which I say: The job market will adapt, and people will move into those jobs where customers prefer to have a human. We have no real idea what those jobs are today, but some of them might be the things you wish you had more of, but are too expensive for most of us to hire someone for. (Interior decorator? Personal chef? ...)
Without manual controls, vague promises ("puffery"?) about autonomy won't drive vehicle sales as they do today across all Tesla's models. The Robocab as shown literally cannot function (or make a dime of revenue) until they've fully solved autonomy and have convinced regulators of the same.
I'm happy for those employees but man, I also wish I could get pizza on Monday.
What looks especially bad for Crowdstrike is how many things (relatively simple things) had to fail in order for this to slip through. It's like walking into Fort Knox, grabbing a gold bar, and walking out unimpeded. A complete systemic failure.
Bottom line, if you're doing something considered relevant to the national interest then that buys you a lot of leeway.
A similar situation applies to writing. When people wrote with quills on parchment under candlelight, they did the structuring and editing in their minds beforehand. Now, word processors encourage us to vomit words onto the page and rarely do we edit them down to a similar level of quality.
It's important to realize that this is at least 100,000 times more powerful than our most powerful Earth-based narrowband emitters. So we would not detect ourselves in this search - not even close.
Moreover, we have no good reason to believe that an advanced species would have cause to radiate 1 TW into space. Our own terrestrial emissions are becoming weaker over time, not stronger, as we optimize for total system bandwidth in our communications.
So I wouldn't draw too many strong conclusions here about alien life. We are still very much searching for our lost keys directly under the lampposts.
The linear drop-off you're referring to is when we look at it in terms of field strength (in this case the spacetime strain). Since power is proportional to field squared, this implies a linear drop-off in the field. It just so happens that for GWs it's easier to detect the field, whereas for (most) EM radiation it's easier to detect power.
There are field-detection methods for EM radiation as well, which are useful for weak signals. Homodyne and heterodyne detection are good examples.
In fact this weak coupling is what makes GWs so interesting for observational astronomy: They propagate from the source to our detectors virtually unchanged. (This is in contrast to EM radiation, which is very easy to scatter.) For example the farthest we can see back with EM radiation is about 200k years after the Big Bang, when the plasma of the early universe recombined into neutral hydrogen. By contrast gravitational waves can see back to the Big Bang itself, so it is a truly unique source of information as compared with light.