Blogged: I Don’t Want to Read What You Didn’t Write blog.colinbreck.com/i-dont-w…

Imagination brings us closer to reality. Fantasy pulls us further away.

I feel like all my writing skills is gone. I feel like I am totally clueless and blank. In other words, everything is totally normal. That's how writing always feels. Good writing anyways...

Have you ever let AI write (or rewrite) any part of your tech blog posts? If so, please answer these quick questions, totally anonymously. It should take less than 3 minutes. forms.gle/3zYuANeuCdcmFt9D9

“AI is helping me write better and faster, but I’m fed up with reading almost anything written by AI.”

Less than a month later, a new record for the largest Powerwall VPP event On Tuesday, 85,000+ Powerwall owners across California dispatched more than 600 MW to the grid, helping to meet peak demand

Now all of our vehicles can provide home backup - Powerwall + your car can power your home for multiple days during an outage. Clean, quiet, low maintenance, and saves money on your bills - no reason to buy a generator ever again.

A painful part of working with your data has always been that your live data and historical data are stuck in separate systems: the order a customer just placed lives in your database, while their last five years of orders sit in a data lake in S3. And answering a real question usually needs both at once (is this a normal purchase for them, or should we flag it?), and to do that you had to move the data together first, copying history out of the data lake into your database (or the other way around), because the database couldn’t read it where it lived. That meant guessing ahead of time which data you’d want, keeping a second copy of it all, building pipelines to move it, and constantly syncing so the two didn’t drift apart. A lot of plumbing, and slow going, all before you could answer one question. And even then, the answers were only as fresh as your last sync. That now changes with Aurora PostgreSQL, which can call your live data and historical data in S3 together, in a single query. No copying, no pipelines to keep in sync. And it’s fast, because we’ve built in DuckDB, a popular open source engine that’s really good at reading and analyzing data right where it’s stored. DuckDB reads the open formats like Parquet and Iceberg already sitting in your data lake, so there’s nothing to convert or move. As folks build AI agents into their apps, the data their agent needs will depend on the task in front of it. Being able to query that specific data live, instead of copying it over just in case, is gonna be a big help for builders. aws.amazon.com/blogs/aws/ama…

It is funny that people now think the use of an em dash automatically means the text was generated by an LLM, like humans have never used the em dash.

It has become clear to me that aging itself does not bring wisdom. It often brings regression to childishness, dependency & bitterness over lost opportunities. Only those who are still intellectually, emotionally, spiritually growing inherit the richness of aging.~James Hollis

The most valuable decisions give you zero feedback @tobi explains ... "Intuition is actually the most valuable when there isn't direct feedback." Wait, what? "If there's many choices, like there's five things that look like good paths to go forward, and any of them has rapid feedback, everyone goes to that." "That is what we call short-termism, right?" But there are many ways to improve the company (and yourself). "Many of them involve long-term investment, refactoring, potentially going into a new market, potentially saying no to going into obviously new markets and actually doubling down and going deeper on our current market. Or we could do what increases the stock value. By the way, this one has a daily ticker and rapid feedback." so in this sense, it's the absence of rapid feedback can be a strong signal. "I find a very high correlation between the right path and the ones that don't have feedback loops attached."

The largest residential virtual power plant event in history Combining output from Powerwalls and other batteries, Tesla and @Sunrun delivered 580 MW to the grid – 517 MW of that came from 110,000 Powerwalls across California

If left was right and right was left, who'd be left to say what's right?

On Labor Day, the charging peak load was 116 cars plugged in at once, at 11.4 MW. All electrical loads will eventually transition to solar + storage. The giant fusion reactor in the sky is free.

Tesla virtual powerplant grid stabilization system

It’s a hot night in California - dispatching nearly 500 MW right now from our VPP fleet to support the peak. tesla.com/vpp/california

They make you the problem because you are pointing to the problem.

Code generation is solved. Any recent model can emit code. Code verification (that includes testing) is not. The verification harness is the software factory.

Every penny matters for Robotaxi scale, including charging. We're using public Superchargers where we can, especially at night when utilization is low. We're also building dedicated Robotaxi Superchargers: back-to-back sessions, low-cost real estate close to demand, low capex. Dispatching Robotaxis to charge uses the same Trip Planner fundamentals we've been refining for over a decade. They're plugged in manually, but that's just for now. On public Superchargers, cars with passengers take priority. Our Robotaxis are more flexible. We'll keep building out Superchargers for Robotaxi demand + improving Robotaxi orchestration as we learn and the fleet scales.