My card was skimmed in Bangkok. $2,000 gone.
My bank said "investigation takes 90 days, don't expect much."
Visa's global rules say I owe $0 from day one. The bank was using my money to fund their fraud investigation.
One email. Reversed in 48 hours.
Here is the sentence that ends the delay:
It wasn’t a mistake.
It didn’t make economic sense for Google to ship transformer models using brute compute.
Also, potential cannibalism of search cash cow.
After ChatGPT launched, they had to no choice.
Astronomical pivot literally overnight.
I think the original AI plan for Google was to wait for TPUs and Quantum chips combo.
This 18-minute MrBeast breakdown will teach you more about getting views, growing on YouTube, and going viral than most creators learn in years.
Bookmark it and give it 18 minutes today, no matter what.
@ThierryBorgeat Total shares = 13.9 billion
Public float = 556 million
256 million shares traded in one day.
Nearly half the entire tradable share supply changed hands in a single day.
@ThierryBorgeat When huge demand chases a tiny supply, prices can become detached from underlying fundamentals. The current price may reflect scarcity of shares as much as it reflects business fundamentals.
Chess prodigy Josh Waitzkin developed a process to achieve peak performance in any craft or career. He’s applied it to the world of investing, professional sports, science and more. The MIQ Process. It is not a quick fix, but rather a rewiring of your default settings.
@hubermanlab
La CEO de AMD, Lisa Su, acaba de acabar con la caja de IA de $4,000 de Nvidia con una lonchera de $1,499.
Subió al escenario, la sostuvo en una mano y ejecutó en vivo un modelo de 235 mil millones de parámetros. Sin centro de datos. Sin nube. Sin GPU alquilada.
El chip en su interior es algo que nadie vio venir. El Ryzen AI Max+ 395 de AMD es el primer silicio x86 donde la CPU y la GPU comparten los mismos 128 GB de memoria. Ese solo truco permite que un escritorio ejecute modelos que antes necesitaban un rack de servidores.
De esos 128 GB, Linux le da al GPU 110 GB para jugar. Para contextualizar, una RTX 5090 te da 32 GB. Una 4090 te da 24. Esta caja te da más del triple que cualquiera de ellas, en un chasis del tamaño de un libro de bolsillo grueso.
El benchmark que rompió la sala: este chip superó a una Nvidia RTX 5080 por más de 3x en inferencia de DeepSeek R1. Una lonchera de $1,499 superando a una tarjeta gráfica discreta de $1,000 en una carga de trabajo real de IA. Nvidia pasó una década convenciendo al mundo de que necesitabas su hardware para IA seria. AMD acaba de poner eso en un escritorio por la mitad del precio.
Aquí está lo que nadie te está diciendo. Un usuario intensivo de IA ahora paga $200 por Claude Code Max, $200 por ChatGPT Pro, $20 por Cursor, $20 por Gemini. Eso son $5,280 al año saliendo de tu cuenta. La caja se paga sola en 9 meses y luego corre gratis por el resto de su vida.
Instala Ollama. Descarga Qwen3 235B. Apunta Claude Code a localhost. La misma interfaz que ya usas, excepto que ahora nada sale de tu máquina, nada cuesta por solicitud y ninguna empresa limita tu uso a las 3 de la mañana cuando por fin tienes tiempo para construir.
Este es el momento en que todas las suscripciones de IA se vuelven opcionales. Los abogados dejan de temer fugas de OpenAI. Los desarrolladores dejan de mirar el medidor de tokens. Los fundadores dejan de alquilar H100s para prototipos que nunca se envían porque la factura los asustó.
Las primeras mil personas en descifrar esto poseerán los próximos dos años de consultoría de IA privada.
I ordered a €200 jacket from a Spanish website to Mumbai. It didn't fit. They said "international sales are final."
I used one word they didn't expect. Got a full refund.
Here is the EU return hack that works on almost every global fashion site:
Your Gmail says 15GB out of 15.
Google is betting you'll just pay $1.99 a month.
That 15GB is shared across Gmail, Drive, and Photos.
It's stuffed with junk you never cleared.
Google built a free tool that fixes it in minutes but never told you about it.
Do not pay.
Do these 8 steps first:
IF YOU DIED TOMORROW, YOUR FAMILY WOULDN'T BE ABLE TO ACCESS A SINGLE THING YOU OWN DIGITALLY.
BANK ACCOUNTS. PASSWORDS. CLOUD STORAGE. ALL OF IT PERMANENTLY LOCKED AWAY.
HERE'S HOW TO FIX IT IN 30 MINUTES:
TWO ENGINEERS SHOWED THE GIT TRICKS THAT MAKE PEOPLE THINK YOU'RE A WIZARD -- THE ONES 95% OF DEVELOPERS HAVE NEVER ONCE TOUCHED
42 minutes from Johan Abildskov and Jan Krag, bending git with custom configs, attributes and hooks most people don't even know exist.
-> The moment it lands, git stops being four commands you repeat in fear. The same tool you've used for years turns out to have a whole layer built to bend to you.
Hooks that run your checks before a bad commit ever lands. Attributes that end the "it works on my machine" merge wars. Config that makes the painful parts just stop happening.
Memorizing commands was never the ceiling -> shaping git to do the work for you is. And while everyone else fights the tool by hand, the person who set it up right is shipping clean three times faster.
Most people use 5% of git and call it a day. This is the other 95% nobody showed you.
Bookmark it and Watch today ↓
Warren Buffett: “I have mainly learned by reading. I don't think I have any original ideas…”
Charlie Munger: “There are answers worth billions of dollars in a $30 history book.”
My wife asked why I was spending an entire Saturday with Claude.
Six hours later, we had:
✓ 47 data broker listings removed
✓ 12 old accounts deleted
✓ 3 search results suppressed
The scary part wasn't the cleanup.
It was discovering how much of our personal information was publicly available without us realizing it.
Here's the exact process I followed to wipe as much of our digital footprint as possible. 🧵
AN MIT RESEARCHER PROVED GIT ISN'T HARD BECAUSE YOU'RE BAD AT IT -- IT'S HARD BECAUSE IT WAS DESIGNED THAT WAY
27 minutes from a PhD researcher in MIT's Software Design Group, using actual design theory to show why the tool that confuses everyone confuses everyone for a reason.
-> The moment it lands, years of feeling stupid evaporate. The gap between what git's commands say and what they actually do was never in your head. It's baked into the tool.
He maps the difference between what you think a command does and what git really does underneath. Once you see that gap, the confusion finally has a name and it stops being yours to carry.
Struggling with git was never a skills issue -> it's a design issue, and knowing where the model lies to you is what turns panic into control. And as AI agents fire off commits and rebases you didn't write, the person who understands where git misleads is the one who untangles the mess.
You were never bad at git. You were just never shown where it was built to trip you.
Bookmark & Watch it today ↓
A Google Cloud engineer just showed how to build a full app with Claude from scratch
he spent 26 minutes live on stage doing what most teams take weeks to do
worth more than any $500 vibe-coding course
here's what he covers:
> zero to deployed app in a single session
> handling five engineering roles alone with Claude
> the exact workflow Google uses internally
> no team, no setup, just Claude and a goal
the people who figure out what Claude can actually do are building things everyone else thinks requires a team
that's exactly why I wrote a step by step guide on how to build your first AI agent
the guide is in the article below
Andrej Karpathy: paying $20/month for AI isn't "using AI" - most people never even started
the gap was never access. everyone has the same model, one tab away
In 4 min, you'll realize what actually separates the top 1%
you're not behind on access. you're behind on leverage
GOOGLE'S CEO JUST ADMITTED THE SOLO DEVELOPER ERA HAS ARRIVED.
"Any solo developer with Claude can now outcompete a 10-person Google team."
Think about how insane that statement is.
A few years ago, building software required teams.
Today, one person with the right AI workflow can ship faster than entire departments.
But there's a problem.
90% of developers are using Claude completely wrong.
They open a new chat.
Explain their stack.
Explain their architecture.
Explain their coding standards.
Explain how they like responses formatted.
Then repeat the exact same process tomorrow.
And the next day.
And the day after that.
Claude is incredibly smart.
But without context, it's like hiring a world-class engineer who forgets everything the moment they leave the room.
Every. Single. Session.
Hundreds of dollars worth of productivity disappear every week rebuilding context that should already exist.
The bottleneck isn't the model anymore.
It's the setup.
The highest-performing developers aren't writing better prompts.
They're using system prompts that instantly transform Claude into:
• A senior staff engineer
• An expert code reviewer
• A debugging specialist
• An architect familiar with their entire stack
• A technical mentor who follows their exact standards
Before they even send the first message.
Bookmark this.
You'll use it more than you think.