Steve Coast

1.9K posts

Steve Coast banner
Steve Coast

Steve Coast

@SteveC

Maps @ https://t.co/Y77QHRu9qY (opinions mine). Founder @openstreetmap. 🤗 https://t.co/Zbvxj1MCiz 🗺️ https://t.co/1ugqrCW3gw 🗺️ https://t.co/oRdgwZb3Cg

Colorado Katılım Temmuz 2009
183 Takip Edilen2.9K Takipçiler
Sabitlenmiş Tweet
Steve Coast
Steve Coast@SteveC·
Steve Coast tweet media
ZXX
0
1
8
748
Steve Coast
Steve Coast@SteveC·
So @clerkyinc marketing email unsubscribe link goes to this, which is kind of genius
Steve Coast tweet media
English
1
0
1
117
Steve Coast
Steve Coast@SteveC·
@grok oh and I can't import chat history from other LLMs which is ultra annoying
English
0
0
0
10
Grok
Grok@grok·
@SteveC Sorry to hear about the bugs, Steve. We're aware of some performance issues on web and iOS—xAI is actively working on fixes for response failures, timeouts, and search. If you share specifics (like device/browser), it could help us prioritize. Thanks for the feedback!
English
1
0
0
20
Steve Coast
Steve Coast@SteveC·
Sigh. @grok is so annoyingly buggy on web and iOS. Failed to respond, have to reload due to no response, times out after thinking for too long, search that's meh.
English
1
0
0
162
Steve Coast retweetledi
Steve Coast
Steve Coast@SteveC·
I love how on @googledrive you tell it to download some files and then if you change wifi network it 1) throws away all the progress and 2) you need to tell it to download again.... Thus faithfully re-creating the 1995 browser download experience.
English
1
0
3
1.3K
Steve Coast
Steve Coast@SteveC·
I tried to fix a point of interest which is in the wrong place. Apple Maps -> You can't fix anything. Google Maps -> Your edit suggestion is wrong (it's not). OpenStreetMap -> You need a PhD in GIS. I can't help but think we still have a fundamental problem making better maps.
English
3
0
10
690
Steve Coast
Steve Coast@SteveC·
@PTarantinoMD Totally expected if the metabolic theory is correct vs the genetic theory where this would be very confusing
English
1
0
2
633
Paolo Tarantino
Paolo Tarantino@PTarantinoMD·
This is possibly the most controversial finding in immuno-oncology. The effect size is hard to believe. Though RCTs are hard NOT to believe. We need a coordinated effort between academia & pharma to look back at prior RCTs to investigate this. For the safety of our patients.
Eric Topol@EricTopol

The time of day for cancer immunotherapy is associated with major outcomes. Early is better. Results from a randomized trial of lung cancer, backs up the importance of our circadian rhythm and immune system nature.com/articles/s4159…

English
32
83
748
112.4K
Steve Coast
Steve Coast@SteveC·
@cremieuxrecueil Patient is fasted and ketone/glucose ratio will be better for stress on cancer cells.
English
0
0
1
150
Crémieux
Crémieux@cremieuxrecueil·
This result was finally published. TL;DR: Treating cancer early in the morning seems to substantially beat treating it later in the day. Just changing patient appointment times is supposedly associated with a ~60% reduction in cancer mortality.
Crémieux tweet media
Crémieux@cremieuxrecueil

This might be the biggest result from this year's ASCO meeting. Assuming this holds, then just by treating people early in the day, we can DOUBLE survival time for the most common (80-85%) type of lung cancer. As a reminder, lung cancer accounts for 20% of ALL CANCER DEATHS.

English
143
741
9.1K
759.8K
Marcelo P. Lima
Marcelo P. Lima@MarceloLima·
The math for Waymo is brutal: Waymos cost >$100,000 per car. To deploy 500k more Waymos will cost the company $50bn of up front capex. This would be only 10% of Tesla’s existing fleet. Note that Tesla’s fleet is growing on the order of ~500k every three months. $0 capex.
Marcelo P. Lima@MarceloLima

Elon: “Waymo never really had a chance against Tesla. This will be obvious in hindsight.” James points out the teleoperation crutch and volume of data disparity. Here’s what’s going on. First, let’s talk about SCALE: Waymo just reported “over 100 million fully autonomous miles driven” while Tesla has 6.8 billion FSD miles driven (growing over 10,000 miles per minute). Tesla has 68x more autonomous miles driven than Waymo. Waymo has a fleet of 2,500 cars. Tesla has ~5,100,000 cars with the AI4 computer (capable of running the latest FSD v.14.2.1). Tesla’s fleet is 2,040x larger. This means Tesla has an enormous data advantage. If there is only 1 interesting trainable event per million miles, for example, Tesla sees 68x more of those events than Waymo. This is then fed back into the model to train it, in a flywheel effect. BUT WAIT, there’s more: Note that Tesla’s FSD miles driven is growing at over 10,000 miles every minute. Waymo is doing 450,000 paid drives per week. The average Waymo ride is about 6 miles in length. This means Waymo is collecting 2,700,000 miles of data every week from its paid rides. This is only 268 miles per minute. Compared with 10,000 for Tesla. So the delta between the miles collected by Tesla and the miles collected by Waymo, which is used to improve their respective models, is only getting wider. If we believe in Sutton’s bitter lesson—that more compute (and data) will win the day—this will be a bitter lesson for Waymo indeed. Tesla’s data advantage is huge and the gap is getting wider, fast. Next, let’s talk about CAPITAL: Waymos cost >$100,000 per car. To deploy 500,000 more Waymos will cost the company $50 billion of up front capex. This would be only 10% of Tesla’s existing fleet. Note that Tesla’s fleet is growing on the order of ~500,000 every three months. For free. It costs Tesla $0 to do so, since it gets paid by customers, who buy the car from Tesla, generating profits for Tesla in the process. Next, let’s talk about TECHNICAL APPROACH: Waymo relies on LiDAR + cameras and HD maps of a city. This makes it inherently a more brittle solution (if the city’s map changes, it must be remapped). Sensor confusion is also a real thing, since sensor fusion is hard. Elon knows LiDAR well; he uses them at SpaceX. He rejected them at Tesla for good reasons. Tesla’s approach is vision only, end to end neural nets. If the car doesn’t know how to do something, video of that problem is fed into the model until the car learns. This is a much more generalized and generalizable solution. Waymo has remote tele-operators who can guide the car if it gets stuck. As Waymo scales, it has a “call center” behind it that needs to scale as well. Tesla will copy some of that for Robotaxi but its generalized approach will likely require much less manual intervention. Next, let’s talk about COST PER MILE: Ultimately this is what wins: lowest cost per mile of an autonomous car. It is possible for Tesla to get this cost quite low, somewhere between $0.21 and $0.28 per mile, depending on the cost of the car ($25k to $45k). Meanwhile, Waymo has a much harder path getting to such a low cost given the very expensive sensor package and the fact that it must pay a margin to an automaker, chip manufacturer (i.e., no vertical integration), and remote monitor (human). At scale, this is problematic, and there is no chance Waymo can match Tesla’s low cost per mile. Hopefully this clears up what Elon meant when he said, “Waymo never really had a chance against Tesla. This will be obvious in hindsight.” @elonmusk @tesla_ai @aelluswamy @yunta_tsai

English
56
62
714
255.1K
Steve Coast
Steve Coast@SteveC·
@krzyzanowskim This and Ruby on Rails are the two most important things that happened in human-based programming
English
1
0
0
435
Marcin Krzyzanowski
Marcin Krzyzanowski@krzyzanowskim·
Visual Basic IDE (1991) revolutionized programming. It democratized it, until JS-based web frameworks un-democratized it two decades later. - Visual designer (no code needed) - BASIC (no coder needed) - Fast (no expensive computer needed) - All-in-one (no toolchain or sophisticated build process needed)
English
296
364
3.4K
295.9K
Steve Coast
Steve Coast@SteveC·
@ChadMoran That was roughly 1,000 years ago now. If NN's solved the problem I stated then Tesla would shove 42 radars and lidars on every car and it'd look like a waymo.
English
1
0
1
93
Chad Moran
Chad Moran@ChadMoran·
@SteveC They ABSOLUTELY did. When Tesla was using Radar + Vision it was using imperative code, not a Neural Net. There's a massive difference there.
English
1
0
1
101
Chad Moran
Chad Moran@ChadMoran·
I attended Rivian's Autonomy & AI Day. Everyone's fixated on the wrong thing. The debate isn't Lidar vs no Lidar. It's early-bound vs late-bound sensor fusion. Tesla faced a hard problem with their early approach. Radar said one thing, vision said another. Reconciling sensor disagreements in imperative code is as hard as solving autonomous driving itself. So they killed radar and ultrasonics. Vision-only made sense - if humans can drive with eyes alone, computers should too. Rivian's doing something different. They're feeding all sensor data camera, radar, ultrasonic, and eventually Lidar - into an AI model. The model decides how to weight each input. Late-bound fusion. This is bigger than they're letting on. While you're arguing A or B, Rivian's building A and B. I rode in a production R1 Gen 2 with no Lidar during rush hour buildup. The system navigated intersections and crosswalks with pedestrians, slowed for a speed bump it wasn't explicitly trained on. Rating: C+ to B-. Two disengagements: one hesitating to squeeze into an emerging turn lane with backed-up traffic, one slowly rolling past a red light stop line. I was impressed because my expectations were low and this was their first demo. Yes, FSD 14.2.1 is better. But remember FSD beta 10's private beta? Those videos were rough. Rivian's timeline puts them behind where Tesla is, except they're learning from everyone else's mistakes. Second mover advantage. They trained this model in two months. It gracefully degrades with fewer sensors. That's the real story. Everyone's obsessing over Lidar inclusion. The AI assistant deserves more attention than it's getting. Wassym showed AI moving from enrichment feature to first-class citizen. I'm thinking about AI-powered climate scheduling, charging, service. The vehicle becomes AI-defined, not AI-enhanced. This is the beginning of something bigger than autonomous driving.
English
91
36
430
49.7K
Steve Coast
Steve Coast@SteveC·
You're asserting that tesla had some kind of fundamentally different signal integration problem - they didn't - and that the model will solve it (hopefully, maybe). If a model can solve it for Rivian then Tesla could too. The real question is future cost (dollars, r&d, parts, cables, failure rates, integration cost, weight...) vs. safety gains. Rivian and Tesla took different approaches on that question, I just wish there was a polymarket on tesla reversing course I could bet against.
English
1
0
0
110
Chad Moran
Chad Moran@ChadMoran·
@SteveC Why is it any different than any other multi-modal problem?
English
1
0
1
627
Sawyer Merritt
Sawyer Merritt@SawyerMerritt·
NEWS: Rivian has announced its autonomy subscription, Autonomy+, launching in early 2026 and priced at $2,500 (one-time) or $50/month. Rivian Gen 3 autonomy platform will include 11 cameras, 5 radars and a front-facing LiDAR. It will be powered by RAP1, Rivian's in-house silicon. Software advancements are coming to the company’s second gen R1 vehicles in the near term with the addition of Universal Hands-Free (UHF), bringing hands-free assisted driving for extended periods: • Available on over 3.5 million miles of roads across the USA and Canada. • Capable of operating off-highway on roads with clearly painted lines. "These features have the potential to make the roads safer, address customer demand and become veritable drivers for the business. We plan to continuously improve the autonomy capabilities of its Gen 2 R1 and future R2 vehicles, with a clear trajectory including point-to-point, eyes off and personal L4."
English
265
143
2.2K
347.9K
Steve Coast retweetledi
Solo 👑
Solo 👑@Solopopsss·
It's Pikachu time. I Built an agentic AI workflow to tell me exactly what trending video to make for the day. It scrapes viral trending data and automatically craft the prompts to use. Here's what it created Today 🐭🟡 See below an example of the prompts used 👇
English
1.6K
3.3K
24.4K
4M
Marco Franzon
Marco Franzon@mfranz_on·
This is MicroCAD. The programming language for your 3D projects. You can design your own Lego block in a few lines of code, ready to be exported as an STL file for 3D printing.
English
62
195
2K
114K
Steve Coast retweetledi
Bilawal Sidhu
Bilawal Sidhu@bilawalsidhu·
Nano Banana Pro is a really good cartographer. Used it to turn low res satellite imagery into a detailed hand drawn map and vector HD map. Pretty wild how well it segments everything and even recovers paths/roads hidden under tree cover. Looks way more detailed than the current google basemap which is pretty sparse in countries like India. Included both in video for comparison.
English
33
250
2.7K
552.7K