正在加载视频...

视频加载失败

返回首页

someone just plugged a cable into a Tesla charger and turned it into a computer virus. Tobias Scharnowski compromised a Tesla Universal Wall Connector through the charging cable itself. the chain: → compromise the Tesla Wall Connector through the charging cable itself (SWCAN protocol on the Control Pilot line,...

hetmehtaa's profile picture

Het Mehta

42,730 subscribers

164,890 次观看 • 14 天前 •via X (Twitter)

科学技术新闻政治
LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

THIS CHINESE DEVELOPER TOLD A TINY AI DEVICE "I NEED A CAR CONTROL PROGRAM" - AND IT WROTE THE CODE, FLASHED THE HARDWARE AND LIT UP THE LEDS IN ONE SHOT small white screen showing "listening..." - he speaks the command out loud - the device hears it, writes the firmware, flashes the Raspberry Pi Pico and the red LEDs fire up in sequence no keyboard, no IDE, no Stack Overflow - just talking to a device that understands what he wants and builds it the breadboard on the desk is the hardware - the tiny screen in his hand is the AI that programs it - voice in, working electronics out he vibe coded the entire control system by describing it - the AI handled every line of MicroPython, every GPIO pin assignment and every LED pattern what used to require an electronics degree and a week of debugging now takes one sentence spoken out loud the people still manually writing firmware are one voice command behind
1:36

THIS CHINESE DEVELOPER TOLD A TINY AI DEVICE "I NEED A CAR CONTROL PROGRAM" - AND IT WROTE THE CODE, FLASHED THE HARDWARE AND LIT UP THE LEDS IN ONE SHOT small white screen showing "listening..." - he speaks the command out loud - the device hears it, writes the firmware, flashes the Raspberry Pi Pico and the red LEDs fire up in sequence no keyboard, no IDE, no Stack Overflow - just talking to a device that understands what he wants and builds it the breadboard on the desk is the hardware - the tiny screen in his hand is the AI that programs it - voice in, working electronics out he vibe coded the entire control system by describing it - the AI handled every line of MicroPython, every GPIO pin assignment and every LED pattern what used to require an electronics degree and a week of debugging now takes one sentence spoken out loud the people still manually writing firmware are one voice command behind

Cortex

11,462 次观看 • 2 个月前

i watched gemma 4 12b build something genuinely impressive today, and then loop itself to death right in front of me. the full run is in the video, sped up but completely uncut, watch it to the end and you will catch the exact moment it stops building and starts looping right in the middle of the work. the task was clean, build a single file gravity simulator, n-body physics, orbits, collisions, running locally on one 3090 through an agent. and for ten minutes it was a joy to watch. it reached for a symplectic integrator on its own, the correct one, the kind that keeps orbits stable instead of spiralling out. real gravity with softening, proper orbital velocities, momentum conserved on collision. the physics was right. the thing actually worked. then on the very last step, writing a few tests to prove its own code, it fell into a loop. not a crash, a loop. it started repeating itself and would not stop. ten more minutes, thirty four thousand tokens into a single answer, the same fragments over and over, until i killed it myself. so it's not that gemma can't code. it did the hard part beautifully. it cannot finish. it cannot hold a long task together without unravelling, and finishing is the entire job in agentic work. here's the part that stings. i run this exact task, same harness, same card, on the chinese open models, qwen especially, and i never see this. they build it, they test it, they stop. every single time. google has the raw capability, you can see it sitting right there in the code, and then the model loops itself to death on a task a 27b from alibaba finishes clean. open weights, apache 2.0, so much to love on paper. i just need it to know when to stop talking.
4:15

i watched gemma 4 12b build something genuinely impressive today, and then loop itself to death right in front of me. the full run is in the video, sped up but completely uncut, watch it to the end and you will catch the exact moment it stops building and starts looping right in the middle of the work. the task was clean, build a single file gravity simulator, n-body physics, orbits, collisions, running locally on one 3090 through an agent. and for ten minutes it was a joy to watch. it reached for a symplectic integrator on its own, the correct one, the kind that keeps orbits stable instead of spiralling out. real gravity with softening, proper orbital velocities, momentum conserved on collision. the physics was right. the thing actually worked. then on the very last step, writing a few tests to prove its own code, it fell into a loop. not a crash, a loop. it started repeating itself and would not stop. ten more minutes, thirty four thousand tokens into a single answer, the same fragments over and over, until i killed it myself. so it's not that gemma can't code. it did the hard part beautifully. it cannot finish. it cannot hold a long task together without unravelling, and finishing is the entire job in agentic work. here's the part that stings. i run this exact task, same harness, same card, on the chinese open models, qwen especially, and i never see this. they build it, they test it, they stop. every single time. google has the raw capability, you can see it sitting right there in the code, and then the model loops itself to death on a task a 27b from alibaba finishes clean. open weights, apache 2.0, so much to love on paper. i just need it to know when to stop talking.

Sudo su

39,719 次观看 • 2 个月前

Someone on Reddit built a real operating system using Claude. Not a browser app pretending to be one. An actual OS that runs on bare metal. It's called Fable-OS. The only interface is a sentence. No bash. No commands. You type what you want and an AI agent executes it through direct kernel syscalls. Everything runs in Ring 0. In the demo, the agent realized it didn't have a sound driver. So it found the Intel sound card, built a driver for it from scratch, and played a sound. On its own. The OS writes its own drivers. Evolves itself. The agent's tools are the kernel itself. Open source. Built because the developer got tired of people calling browser apps "AI operating systems." This one actually is.
0:36

Someone on Reddit built a real operating system using Claude. Not a browser app pretending to be one. An actual OS that runs on bare metal. It's called Fable-OS. The only interface is a sentence. No bash. No commands. You type what you want and an AI agent executes it through direct kernel syscalls. Everything runs in Ring 0. In the demo, the agent realized it didn't have a sound driver. So it found the Intel sound card, built a driver for it from scratch, and played a sound. On its own. The OS writes its own drivers. Evolves itself. The agent's tools are the kernel itself. Open source. Built because the developer got tired of people calling browser apps "AI operating systems." This one actually is.

Vaibhav Sisinty

20,562 次观看 • 1 个月前

Tesla unsupervised Tesla Robotaxi hitting and going through bollards. Is this the first recorded instance of an unsupervised robotaxi hitting an object? It was supposed to go around it. I’ve had a critical disengagement once here too with my car. Holy shit wasn’t expecting it to just go through. Luckily there was no damage to the bollards or the car. People have run them over too in front of me but wasn’t expecting the robotaxi to do it. Will this be in the NHTSA report?? I don’t think this can be considered an “accident”
1:54

Tesla unsupervised Tesla Robotaxi hitting and going through bollards. Is this the first recorded instance of an unsupervised robotaxi hitting an object? It was supposed to go around it. I’ve had a critical disengagement once here too with my car. Holy shit wasn’t expecting it to just go through. Luckily there was no damage to the bollards or the car. People have run them over too in front of me but wasn’t expecting the robotaxi to do it. Will this be in the NHTSA report?? I don’t think this can be considered an “accident”

Abhimanyu Yadav

560,418 次观看 • 20 天前

THE HEAD ENGINEER AT ANTHROPIC LEAKED A SETUP WHERE ONE FILE TURNS INTO A FINISHED PRODUCT IN 24 HOURS you hire nobody - you paste a $3.2M file into Fable 5, and the system unrolls itself from there. root → wiring → 4 branches → tests → release → back into the root in the first hour you write 4 things: boundaries, stack, roles, escalation - everything downstream is a consequence of that file. the first 5 hours the system wires itself into tools and only then decides what to build - a team would spread that across two weeks. 8 straight hours run 4 parallel branches with zero meetings - the same block a team fills with standups. by the time you finally open the diff, tests and the critic have already rejected it twice. the changelog is written by the run, not by a human from memory - so it never falls behind the code. your total involvement across the day is exactly 2 hours: the first one, and the one where you say ship it. the 9 hours you were asleep weren't downtime, they were capacity - a queue you have to launch by hand becomes your monday. and the key part: at 05:00 the report rewrites that same root - what shipped, what got rejected, what it cost. without that last line this is just a schedule - with it, the schedule improves itself. save this and paste it into Claude Code - and tomorrow starts from a better file than today did ↓
0:50

THE HEAD ENGINEER AT ANTHROPIC LEAKED A SETUP WHERE ONE FILE TURNS INTO A FINISHED PRODUCT IN 24 HOURS you hire nobody - you paste a $3.2M file into Fable 5, and the system unrolls itself from there. root → wiring → 4 branches → tests → release → back into the root in the first hour you write 4 things: boundaries, stack, roles, escalation - everything downstream is a consequence of that file. the first 5 hours the system wires itself into tools and only then decides what to build - a team would spread that across two weeks. 8 straight hours run 4 parallel branches with zero meetings - the same block a team fills with standups. by the time you finally open the diff, tests and the critic have already rejected it twice. the changelog is written by the run, not by a human from memory - so it never falls behind the code. your total involvement across the day is exactly 2 hours: the first one, and the one where you say ship it. the 9 hours you were asleep weren't downtime, they were capacity - a queue you have to launch by hand becomes your monday. and the key part: at 05:00 the report rewrites that same root - what shipped, what got rejected, what it cost. without that last line this is just a schedule - with it, the schedule improves itself. save this and paste it into Claude Code - and tomorrow starts from a better file than today did ↓

Sprytix

20,510 次观看 • 21 天前

One guy built a wedding camera app in a month and it now makes him over $1,000,000 a year. No team, no investors, no marketing budget. 100,000 downloads in the first month. Zero dollars on ads. He did not bolt marketing onto the product. He made using the product the marketing. You cannot use the app alone. The host has to pull every guest into it. One wedding is not one user. It is 200 people scanning the same code in one evening. The guest liked it at someone else's wedding. A month later he throws his own event and brings his own crowd. The loop spins for free. It does not look like an ad. To the guest it is a gift. So they install it gladly. $2 to $50 subscriptions. 5% pay. That is $100,000 a month. He did not win on budget. He sewed the growth into the product itself. Could you build the loop, or is it just luck?
0:23

One guy built a wedding camera app in a month and it now makes him over $1,000,000 a year. No team, no investors, no marketing budget. 100,000 downloads in the first month. Zero dollars on ads. He did not bolt marketing onto the product. He made using the product the marketing. You cannot use the app alone. The host has to pull every guest into it. One wedding is not one user. It is 200 people scanning the same code in one evening. The guest liked it at someone else's wedding. A month later he throws his own event and brings his own crowd. The loop spins for free. It does not look like an ad. To the guest it is a gift. So they install it gladly. $2 to $50 subscriptions. 5% pay. That is $100,000 a month. He did not win on budget. He sewed the growth into the product itself. Could you build the loop, or is it just luck?

Marlow

513,464 次观看 • 1 个月前

8-year-old from China is writing Python and automating a YouTube system that makes $10,000 a month. Game loop, replay function, player markers - found the bug himself, explained the logic out loud, fixed the line through a projector on the entire wall. That same code in a year becomes part of a pipeline that generates videos, voices them through ElevenLabs and publishes to 5 platforms simultaneously. A high schooler with a $20 ChatGPT 5.5 subscription is already making $6,000-10,000 a month - no camera, no face, no team. This kid is building the same thing but understands every line from the inside. The difference between someone who uses the system and someone who builds it - a $20 subscription vs your own engine under the hood. At 8 years old he's already on the second path.
0:22

8-year-old from China is writing Python and automating a YouTube system that makes $10,000 a month. Game loop, replay function, player markers - found the bug himself, explained the logic out loud, fixed the line through a projector on the entire wall. That same code in a year becomes part of a pipeline that generates videos, voices them through ElevenLabs and publishes to 5 platforms simultaneously. A high schooler with a $20 ChatGPT 5.5 subscription is already making $6,000-10,000 a month - no camera, no face, no team. This kid is building the same thing but understands every line from the inside. The difference between someone who uses the system and someone who builds it - a $20 subscription vs your own engine under the hood. At 8 years old he's already on the second path.

Noisy

99,268 次观看 • 4 个月前

One guy built this app in a month and now it makes him more than $1,000,000 a year. No team. No investors. No marketing department. One developer. One month. One clever idea. The app is a camera for events. In its first month it got 100,000 downloads and he did not spend a single dollar on ads. Here is how he did it because the most interesting part is the growth itself. He did not bolt marketing onto the product. He made using the product the marketing itself. After that things kick in that almost nobody figures out. 1. You cannot use the app alone. For it to work the host has to pull every guest into it. Each install drags in dozens more right away. 2. One wedding is not one user but a whole crowd at once. 200 people scan one code in an evening and install the app. No ad brings that many for the same money and here the money is zero. 3. The guest becomes the host. He liked it at someone else's wedding and a month later he throws his own event and brings his own people. The loop spins itself and for free. 4. It does not look like an ad. To the guest it is a gift not some app forced on him. So they install it gladly and all of them do. 5. It all runs on emotion. A wedding. Memories. Shared shots. People film it and show their own people and a new wave comes in. Now let us count the money plain and honest. The subscription runs from 2 to 50 dollars. Say only every 20th person pays. That is 5,000 people out of 100,000. The average check a modest 20 dollars. 5,000 times 20 is 100,000 dollars a month. More than 3,000 a day. More than $1,000,000 a year. And all of this is one guy in a month without a single dollar on ads. He did not win on budget and not on a team. He won by sewing distribution into the very use of the product. You can lift almost any product this way. Could you build something like this on your own or is it just luck?
0:23

One guy built this app in a month and now it makes him more than $1,000,000 a year. No team. No investors. No marketing department. One developer. One month. One clever idea. The app is a camera for events. In its first month it got 100,000 downloads and he did not spend a single dollar on ads. Here is how he did it because the most interesting part is the growth itself. He did not bolt marketing onto the product. He made using the product the marketing itself. After that things kick in that almost nobody figures out. 1. You cannot use the app alone. For it to work the host has to pull every guest into it. Each install drags in dozens more right away. 2. One wedding is not one user but a whole crowd at once. 200 people scan one code in an evening and install the app. No ad brings that many for the same money and here the money is zero. 3. The guest becomes the host. He liked it at someone else's wedding and a month later he throws his own event and brings his own people. The loop spins itself and for free. 4. It does not look like an ad. To the guest it is a gift not some app forced on him. So they install it gladly and all of them do. 5. It all runs on emotion. A wedding. Memories. Shared shots. People film it and show their own people and a new wave comes in. Now let us count the money plain and honest. The subscription runs from 2 to 50 dollars. Say only every 20th person pays. That is 5,000 people out of 100,000. The average check a modest 20 dollars. 5,000 times 20 is 100,000 dollars a month. More than 3,000 a day. More than $1,000,000 a year. And all of this is one guy in a month without a single dollar on ads. He did not win on budget and not on a team. He won by sewing distribution into the very use of the product. You can lift almost any product this way. Could you build something like this on your own or is it just luck?

Blaze

10,703 次观看 • 1 个月前

I BUILT GROK BOT SECOND BRAIN 26 agents, one core, running off a single rule my own memory never followed: capture everything, forget nothing, connect it before you even ask. A voice note on a coffee walk gets split into a task and an idea in under 6 seconds - the core already knows the difference between something you have to do and something you just thought of. An idea from three weeks ago gets linked to the one you just had, automatically, before you remember you'd had it the first time. That visual -the rotating profile, the 26 glowing lines firing out through the skull, each one labeled with the agent running it - isn't a rendered mockup. It's the actual runtime. Every line is a live agent doing its job in real time, right now, in your browser. This isn't a note app. Note apps hold what you give them. This is a nervous system for everything your brain was never built to hold onto in the first place. Full build - the 26 agents, how memory actually persists, what it costs to set one up for real - is in the article.
0:20

I BUILT GROK BOT SECOND BRAIN 26 agents, one core, running off a single rule my own memory never followed: capture everything, forget nothing, connect it before you even ask. A voice note on a coffee walk gets split into a task and an idea in under 6 seconds - the core already knows the difference between something you have to do and something you just thought of. An idea from three weeks ago gets linked to the one you just had, automatically, before you remember you'd had it the first time. That visual -the rotating profile, the 26 glowing lines firing out through the skull, each one labeled with the agent running it - isn't a rendered mockup. It's the actual runtime. Every line is a live agent doing its job in real time, right now, in your browser. This isn't a note app. Note apps hold what you give them. This is a nervous system for everything your brain was never built to hold onto in the first place. Full build - the 26 agents, how memory actually persists, what it costs to set one up for real - is in the article.

Aleiah

250,911 次观看 • 7 天前

An MIT professor finds the prize behind a thousand doors by opening ten. no faster running. he just skips every door it cannot be behind. the lecture is called algorithmic thinking. 6 million people have watched it, and it has been free the whole time. brute force checks every door, one by one. a real algorithm throws away half of them with every step. same answer, a thousand times fewer moves, zero new hardware. now read the post above. that is Wall Street paying $300 million for the opposite. they drilled a cable through a mountain to open the same thousand doors 3 milliseconds faster. Devadas just stopped opening most of them. that same move is every search engine, every trading model, every small AI that beats a bigger one. the edge was never the speed of the machine. it was the shape of the idea. no cable. no mountain. one better idea. a quant I know says one algorithm rewrite beat a full year of latency upgrades on his desk. they spent $300 million to run the long way faster. the shortcut has been free for over a decade.
50:28

An MIT professor finds the prize behind a thousand doors by opening ten. no faster running. he just skips every door it cannot be behind. the lecture is called algorithmic thinking. 6 million people have watched it, and it has been free the whole time. brute force checks every door, one by one. a real algorithm throws away half of them with every step. same answer, a thousand times fewer moves, zero new hardware. now read the post above. that is Wall Street paying $300 million for the opposite. they drilled a cable through a mountain to open the same thousand doors 3 milliseconds faster. Devadas just stopped opening most of them. that same move is every search engine, every trading model, every small AI that beats a bigger one. the edge was never the speed of the machine. it was the shape of the idea. no cable. no mountain. one better idea. a quant I know says one algorithm rewrite beat a full year of latency upgrades on his desk. they spent $300 million to run the long way faster. the shortcut has been free for over a decade.

Rossst.03

81,024 次观看 • 1 个月前

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.
0:47

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.

Landseer Enga

23,963 次观看 • 3 个月前

Danny Goler: "If you shine a DeWalt Laser at the wall whilst doing DMT you can see through the wall read the code to our reality" This is a reality shattering truth which could prove we live in a matrix style simulation. While under the influence of DMT, shining a low-power red laser (under 5mW) on a wall or arm reveals moving symbolic code. It appears matrix-like, resembling katakana, Hebrew, Aramaic, or alien-style writing. "You can even put it on your arm and the code changes on your arm. If your arm gets in front of where the wall is, the code is completely different." The code stays stable and solid. It does not warp or morph the way ordinary hallucinations do. Looking from different angles or moving the laser simply uncovers new layers of the same coherent code. "I can see through the wall. It's not like a hallucination. It has spatial awareness and permanence." Thousands of people have independently reported seeing the exact same thing in the same places.
4:54

Danny Goler: "If you shine a DeWalt Laser at the wall whilst doing DMT you can see through the wall read the code to our reality" This is a reality shattering truth which could prove we live in a matrix style simulation. While under the influence of DMT, shining a low-power red laser (under 5mW) on a wall or arm reveals moving symbolic code. It appears matrix-like, resembling katakana, Hebrew, Aramaic, or alien-style writing. "You can even put it on your arm and the code changes on your arm. If your arm gets in front of where the wall is, the code is completely different." The code stays stable and solid. It does not warp or morph the way ordinary hallucinations do. Looking from different angles or moving the laser simply uncovers new layers of the same coherent code. "I can see through the wall. It's not like a hallucination. It has spatial awareness and permanence." Thousands of people have independently reported seeing the exact same thing in the same places.

Interstellar

63,599 次观看 • 1 个月前

DELETE FIGMA. ONE MCP CONNECTOR TURNS CLAUDE CODE INTO A GOD-MODE STUDIO IN 30 MINUTES. The exact setup, step by step, no jokes: > open connectors, add a custom connector, drop in the Higgsfield MCP > open a Claude Code session and paste one prompt > it generates the first frame, the last frame, and the motion between them > then wires the result straight into an animated hero section for your site > 30 minutes end to end, nothing rendered by hand The bigger thing hiding here: MCP means the model rents hands. it doesn't know how to animate, so it hires a tool that does, mid-task, without you switching tabs. The ceiling of what one prompt ships isn't the model anymore, it's how many hands you've plugged into it. The method underneath (the goal, the rules, the bar, the loop) is in the article below, and it works with any connector you add next.
0:32

DELETE FIGMA. ONE MCP CONNECTOR TURNS CLAUDE CODE INTO A GOD-MODE STUDIO IN 30 MINUTES. The exact setup, step by step, no jokes: > open connectors, add a custom connector, drop in the Higgsfield MCP > open a Claude Code session and paste one prompt > it generates the first frame, the last frame, and the motion between them > then wires the result straight into an animated hero section for your site > 30 minutes end to end, nothing rendered by hand The bigger thing hiding here: MCP means the model rents hands. it doesn't know how to animate, so it hires a tool that does, mid-task, without you switching tabs. The ceiling of what one prompt ships isn't the model anymore, it's how many hands you've plugged into it. The method underneath (the goal, the rules, the bar, the loop) is in the article below, and it works with any connector you add next.

Miraqle

38,373 次观看 • 1 个月前

Hey Tesla Charging, Yellowstone is one of the most beautiful national parks in the world, yet it’s one of the hardest places to charge a Tesla. Right now, I’m stuck relying on slow third-party ChargePoint charger that takes 11+ hours for a full charge, while the nearest Tesla Supercharger is hours away. Millions of people visit Yellowstone every year, and EV adoption keeps growing. Adding more Tesla Superchargers in and around the park would make road trips safer, easier, and far more enjoyable for everyone. Please consider expanding the Supercharger network in Yellowstone. It would make a huge difference!
0:26

Hey Tesla Charging, Yellowstone is one of the most beautiful national parks in the world, yet it’s one of the hardest places to charge a Tesla. Right now, I’m stuck relying on slow third-party ChargePoint charger that takes 11+ hours for a full charge, while the nearest Tesla Supercharger is hours away. Millions of people visit Yellowstone every year, and EV adoption keeps growing. Adding more Tesla Superchargers in and around the park would make road trips safer, easier, and far more enjoyable for everyone. Please consider expanding the Supercharger network in Yellowstone. It would make a huge difference!

Teslaconomics

135,633 次观看 • 2 个月前

THIS GUY JUST BUILT A DRONE THAT TRACKS TARGETS WITH A LASER USING CLAUDE > No robotics team > No engineering degree > No budget He used Claude Code to write the entire system in Python - a drone that locks onto a target, follows it with a laser and corrects its own aim automatically after every attempt. The AI gets more accurate the longer it runs because it learns from every single shot. He's still improving it and this is only the beginning. You have the same tool he used. The article below is about how to actually use it to its full potential.
0:39

THIS GUY JUST BUILT A DRONE THAT TRACKS TARGETS WITH A LASER USING CLAUDE > No robotics team > No engineering degree > No budget He used Claude Code to write the entire system in Python - a drone that locks onto a target, follows it with a laser and corrects its own aim automatically after every attempt. The AI gets more accurate the longer it runs because it learns from every single shot. He's still improving it and this is only the beginning. You have the same tool he used. The article below is about how to actually use it to its full potential.

Anatoli Kopadze

275,518 次观看 • 3 个月前

This windshield wiper move might seem like a small thing, but to me it really highlights the power of Tesla’s vertical integration. Other autonomy providers bolt on their own sensors, with their owning cleaning. Tesla integrates it all together. The same wipers that clean the windshield also clean the front cameras. If you’re Waymo, how do you even go about reprogramming the windshield wiper routine for all the different car brands and models you run on? You don’t, you create a separate cleaning system for your own sensors. Tesla makes the car. They make the software that runs on the car. They control all the parts. They run the ride share service. They own the charging network. They own the service network. And they are making all of it fit together to deliver the best, the simplest, and the most elegant autonomy solution. This wiper routine is just one example of that.
0:42

This windshield wiper move might seem like a small thing, but to me it really highlights the power of Tesla’s vertical integration. Other autonomy providers bolt on their own sensors, with their owning cleaning. Tesla integrates it all together. The same wipers that clean the windshield also clean the front cameras. If you’re Waymo, how do you even go about reprogramming the windshield wiper routine for all the different car brands and models you run on? You don’t, you create a separate cleaning system for your own sensors. Tesla makes the car. They make the software that runs on the car. They control all the parts. They run the ride share service. They own the charging network. They own the service network. And they are making all of it fit together to deliver the best, the simplest, and the most elegant autonomy solution. This wiper routine is just one example of that.

Whole Mars Catalog

151,035 次观看 • 1 年前

A painting of the Phoenix on the wall of our destroyed home 🐦‍🔥 My second painting during the war. The journey to find art supplies was the hardest one I’ve had in a while. I truly felt the need to paint, but I couldn’t find a single canvas, and the colors available were unfamiliar—difficult to blend into something that resembled my soul. I returned home with orange paint, to our shattered wall, the water seeping through it, and the leaning structure that is barely standing—just like us. Now, the Phoenix is an ancient legend… It burns by its own will, and from the ashes it rises again— stronger, purer, and more radiant. In the myth, the Phoenix is not a bird that never dies, but a bird that knows how to begin again from zero. It understands that an ending is only a stage of burning before another birth. That is why I painted it here… Not because it does not burn, but because it burns— and then chooses to return. Just like us in Gaza, every single day. I hope my second painting during the war has earned your admiration ❤️🐦‍🔥
1:50

A painting of the Phoenix on the wall of our destroyed home 🐦‍🔥 My second painting during the war. The journey to find art supplies was the hardest one I’ve had in a while. I truly felt the need to paint, but I couldn’t find a single canvas, and the colors available were unfamiliar—difficult to blend into something that resembled my soul. I returned home with orange paint, to our shattered wall, the water seeping through it, and the leaning structure that is barely standing—just like us. Now, the Phoenix is an ancient legend… It burns by its own will, and from the ashes it rises again— stronger, purer, and more radiant. In the myth, the Phoenix is not a bird that never dies, but a bird that knows how to begin again from zero. It understands that an ending is only a stage of burning before another birth. That is why I painted it here… Not because it does not burn, but because it burns— and then chooses to return. Just like us in Gaza, every single day. I hope my second painting during the war has earned your admiration ❤️🐦‍🔥

SARA 𓂆

22,056 次观看 • 6 个月前

ANTHROPIC LEAKED A SETUP WHERE ONE FILE STARTS 7 LOOPS THAT TURN A PROMPT INTO A WORKING BUSINESS AI engineer drops in 1 file - the other 95% of the work closes automatically without them. spec → tasks → code → tests → docs → release → monitoring → back into the spec you don't write tickets anymore - you write the thing tickets get derived from, and Opus 5 cuts the spec into 6 tasks by itself. a task that fails its test comes back to itself, not to you - and runs a second lap without a single notification. 6 lanes of code run in parallel and none of them wait on you - the critic filters the diff before you ever open it. every new production bug becomes a permanent line in the eval set - the system never steps on it twice. monitoring isn't the end of the line, it's the start of the next spec - those back edges are what make it a graph instead of a conveyor. and one place is left where you say yes - release, 5 minutes instead of 5 hours. save this and paste it into Claude Code - and you get 7 loops that run without you ↓
0:52

ANTHROPIC LEAKED A SETUP WHERE ONE FILE STARTS 7 LOOPS THAT TURN A PROMPT INTO A WORKING BUSINESS AI engineer drops in 1 file - the other 95% of the work closes automatically without them. spec → tasks → code → tests → docs → release → monitoring → back into the spec you don't write tickets anymore - you write the thing tickets get derived from, and Opus 5 cuts the spec into 6 tasks by itself. a task that fails its test comes back to itself, not to you - and runs a second lap without a single notification. 6 lanes of code run in parallel and none of them wait on you - the critic filters the diff before you ever open it. every new production bug becomes a permanent line in the eval set - the system never steps on it twice. monitoring isn't the end of the line, it's the start of the next spec - those back edges are what make it a graph instead of a conveyor. and one place is left where you say yes - release, 5 minutes instead of 5 hours. save this and paste it into Claude Code - and you get 7 loops that run without you ↓

Sprytix

66,333 次观看 • 24 天前

Tesla wouldn't bring Cybertruck to India, so I built my own 😬 (a micro one) Used ESP32 as the controller, designed 3d printed tyres, chassis, shell, and added micro coreless motors that are otherwise used in small drones. Wrote firmware in Rust and took claude's help to write a Bluetooth (BLE) based controller that works over web browser as well as an iOS app. Opted for tank steering with 4WD, which is a lot of fun with the power it has. The car is so powerful/fast that I had to limit the max speed to 30% in my firmware 😅
0:48

Tesla wouldn't bring Cybertruck to India, so I built my own 😬 (a micro one) Used ESP32 as the controller, designed 3d printed tyres, chassis, shell, and added micro coreless motors that are otherwise used in small drones. Wrote firmware in Rust and took claude's help to write a Bluetooth (BLE) based controller that works over web browser as well as an iOS app. Opted for tank steering with 4WD, which is a lot of fun with the power it has. The car is so powerful/fast that I had to limit the max speed to 30% in my firmware 😅

Shantanu Goel

14,393 次观看 • 8 个月前