When teenagers pull away from their families, parents usually blame it on the phones. But the real issue is a sudden shift in how you listen to them. This can help you: 🧵
During the 2023 U.S.-China nuclear talks, America proposed missile-launch notifications, a nuclear crisis hotline, and processes to limit the use of outer space for military conflict. China declined all of those. Blame the U.S. if you wish (do we always keep our word?), but that is what happened. China also broke off meaningful arms control talks.
Racism today: when a white person faces accusations of wrongdoing, the accusation is against per alone. When a black person faces accusations, racists use that to cast aspersions against blacks in general.
AI companies make for flawed messengers on this subject: they can reasonably be accused of marketing, of blame-shifting, of regulatory capture, and more.
I think it’s entirely plausible that screens have a real negative effect on teenagers, but studies can’t find them because (a) the effects need not be dose-dependent (maybe two hours on your phone isn’t worse than one hour), and (b) given that everyone else is on social media, giving it up can have a negative effect.
The level of academics that those students know is very low because the parents have basically abandoned that and said, "I care all about the life skills." For parents who really care about academics, those kids crush it.
Whether American teenagers should be harassed after 10 p.m. by engagement-baiting push notifications ought to be a matter for Congress, not the social media cartel.
Thinking Forth by Leo Brodie. I used to have this habit where I learned various programming languages. To challenge my perspective, I chose languages from families and paradigms that were fundamentally different from what I already knew. Occasionally, I stumbled upon greatness. Thinking Forth presents programming as a creative process, and it delivers those lessons in an entertaining and pedagogical way. The book is particularly strong on software analysis and design, but it's the execution and technical writing that brought the book to my top five. This is the book for anyone writing about software — Leo's way is the way to do it.
Multi-Paradigm Design for C++ by James O. Coplien. Twenty years after reading this, the core techniques are still with me. These are commonality analysis, where the purpose is to identify families of systems, and variability analysis, which focuses on capturing the domain parameters that vary. In essence: the foundation of great software design.
When a company fails, most people blame the CEO. I generally blame the board. Because the board's job is to make sure the right person's running the company, and if they're failing, help the person.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.