Colon cancer is now:
- No. 1 cancer killer of men under 50
- No. 2 cancer killer for women same age.
Here is what research says can stop it:
1. It begins as one silent polyp that grows for 10 years without a single symptom.
The most important technology problem of the next 5 years:
Creating a broadly accepted standard for agents to identify themselves to service providers, so that providers can adjust the way they interface with clients (as compared to human-based traffic).
In the interim (i.e., for the next 6 months), there will be a cat-and-mouse game that agents will play -- to circumvent detection and maintain their product's utility during this growth phase.
However, this will only be a stopgap and it will not be the terminal state of the world.
One of the most compelling parts about working at an ElonCo was the agility to pivot to whatever the most important problem was.
One day I said: I wasn’t hired to go after spam, but a tsunami is coming and I’m going to drop everything to focus on that.
The org is so flat and agile that your title is basically meaningless. Anyone can sound the alarm about a problem and solve it themselves—or rally the team to join them.
This is how startups work but it’s very hard to make it work in a larger company.
When I started my first job in 2010, I bought a few books. One of them was Hackers & Painters by @paulg. I was a recent graduate, just starting my career.
In the book, Paul wrote something that has stuck with me ever since: “If you have two choices, choose the harder.”
The idea is that the gains from doing hard things compound over time. When there are two paths in front of you, taking the harder one will cause you to learn more from it in the long run.
That sentence stuck with me so much that, even 16 years later, I still follow that advice. It has helped me a lot throughout my career, and I’m trying to teach the same thing to my two kids. That a comfortable life is often built by doing hard things, putting in the effort, and learning how to solve problems.
Elon’s advice to 20-year-olds on surviving the AI era:
Get as broad-based an education as possible: arts, sciences, engineering, and wide general knowledge.
Why?
AI and robots will fulfill almost any request immediately.The edge won’t be doing the work. It will be knowing what to ask for. The broader your knowledge, the better your questions.
(source: CGTN)
Even the best models train on a lossy residue of the world. Language is not reality; it is a slow social compression of it. Spoken English carries tens of bits per second of new information, well below a 56k modem. Text is denser but still a thin pipe. Almost everything a nervous system registered never entered the corpus.
Give a model the uncompressed stream—electromagnetic waves and force, not tokens—and the first problem is no longer prediction but what to treat as a unit.
Tokens are an accident of human writing. A mind that saw the raw field would invent its own compression: events, invariants, causal structure, geometries we do not yet name.
Everything you want is on the other side of not giving a fuck, asking again, and taking another shot. Life gives you endless lottery tickets to try and you only need one win to change your life forever .
Delegate coding. Never delegate understanding.
If code was previously your source of truth for managing understanding, then you need a new source of truth artifact. If code-centric workflows were how you developed that understanding, then you need new workflows.
.@JensenHuang on how setbacks create opportunities:
"One setback after another, we shook it off and skated to the next opportunity. Each time, we gain skills and strengthen our character. No setback that comes our way doesn't look like an opportunity these days. The world can be unfair and deal you with tough cards. Swiftly shake it off."
I've seen young senior software engineers who don't know what a thread is anymore. They thought I was talking about Threads from Meta.
Their brains are being "Clauded”.
Yes, some coding is so boring you shouldn't care. But good engineers still need to know the design choices, or they might just be meat proxies for prompts.
"Software Engineering is Dead, English will be a coding language"
Who's gonna tell this podcasters about:
Database, GPU, Cores, Docker, Kubernetes, Kafka, Redis, Cloud Infrastructures, LLM Inferencing, model fine-tuning, model deployment, model monitering, model versioning, model rollbacks, servers, serverless architectures, load distributions, cron jobs, rate limiting???