Loading video...

Video Failed to Load

Go Home

Two very different projects. Same kind of engineering instinct. The upper clip uses a cockroach with a very minimal mechanical setup. The lower one takes a quadcopter and surrounds it with tracked frames so the same machine can move on land, travel through water and take off into the...

60,209 views • 9 days ago •via X (Twitter)

10 Comments

Abhimanyu Roy's profile picture
Abhimanyu Roy9 days ago

Is that first one anal probing cockroach?

Techniahqrobot | humanoid robots's profile picture
Techniahqrobot | humanoid robots9 days ago

That first project definitely needs some context 😅 I’m still trying to find the original paper or intended use case, because the setup looks very unusual

Techniahqrobot | humanoid robots's profile picture
Techniahqrobot | humanoid robots8 days ago

Too late. It already knows where you live.

RAZA | AI EXPLORER's profile picture
RAZA | AI EXPLORER9 days ago

Really interesting engineering approach. Designing around the environment instead of adding software layers is a compelling idea.

Techniahqrobot | humanoid robots's profile picture
Techniahqrobot | humanoid robots9 days ago

I like seeing hardware geometry do part of the work before control software even enters the picture. It often leads to simpler behavior with fewer assumptions.

RAZA | AI EXPLORER's profile picture
RAZA | AI EXPLORER8 days ago

Exactly. Good geometry can simplify the control problem from the start.

BonBonaz's profile picture
BonBonaz8 days ago

cockroach with a mech suit, still less scary than my liquidation price

Techniahqrobot | humanoid robots's profile picture
Techniahqrobot | humanoid robots8 days ago

Give the cockroach leverage and then we have a real problem.

Prime Ashref's profile picture
Prime Ashref8 days ago

@grok wtf is going on in the first clip

Luis's profile picture
Luis8 days ago

But why is it fucking the cockroach like that

Related Videos

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

Hanako

19,160 views • 2 months ago

I'd like to take a second to discuss what it means for a storm to be a Category 5. It's a beautiful, mesmerizing, terrifying and awe-inspiring pageant of power and elegance. It's the atmosphere at its most dynamic, raw and extreme. The hurricane has to have an absolutely perfect, undisturbed balance. It's an extremely rare feat. A Category 5 is like a spinning top whirring on a table; even the slightest jiggle can knock it off-kilter – like bumping the table. There must be virtually no shear, or changing winds with height. The upper-level winds around the system must be relatively calm. It's incredible to think that the planet's most furious storms are born out of an abundance of calm. The waters must be exceptionally warm – upwards of 86 degrees – to be replete with "oceanic heat content," or heat energy for the hurricane to draw upon. The warm waters heat and moisten the air above. That air rushes into the building hurricane. As air nears the center of the storm, it expands due to the hurricane's low pressure. That expansion releases heat energy to the environment, encouraging air to rise and powering the storm. In theory, that air parcel (pocket) should cool, but it doesn't. Why? It's still being heated by the oceans below. The ocean is constantly re-heating the lower atmosphere – and energizing the storm – at the exact same rate the air is releasing heat energy into the storm. Most of the moisture in the air condenses and produces rain, releasing even more "latent heat" to the environment. Near the hurricane's center, there's a lot of heat energy. So much so that the air rises, as if in a chimney. That rising air literally lifts air up and away from the surface. There's literally less air, and therefore less air weight, or *pressure*, at the center of the storm. Most Category 5 hurricanes are "missing" about 8-10 percent of the air from the middle. It's that deficit of air that behaves like a vacuum of sorts. Air from outside the storm rushes in to fill the void, like water spiraling into a sink drain. The greater the deficit, the faster the winds. The wind increases exponentially closer to the center of the storm; Category 5 hurricanes have winds over 157 mph. So why doesn't the eye, with the "missing" air, just "fill in?" Because the hurricane is rotating so furiously! The air is flung outwards by the "centrifugal force" at the exact same rate it's being pulled inwards by the "pressure gradient force." The air can never fully reach the eye – and instead it swirls around and around, like water perpetually sloshing around the edges of a toilet. We call that "cyclostrophic balance." Thus, the eye doesn't fill in. The storm charges on. And – until the system is torn apart by disruptive upper-level winds or moves over cooler waters/land – it continues.

Matthew Cappucci

24,772 views • 1 year ago

WHAT IS AN AI "SOFTWARE FACTORY" AND IS IT HYPE (31 MINUTE BREAKDOWN) I think it's a silly name for a genuinely USEFUL idea! A software factory is 5-6 markdown files that sit next to your code and tell your agents how you like to work, so you can build high quality apps 24/7. It's going viral because AI coding has a trust problem. The model can build the feature, but with no structure around it you end up babysitting the agent, wondering what changed and hoping it didn't break something important. So you build with agents the same way a factory builds physical products! 1. Each feature gets its own station, which in software means its own branch, so multiple agents can work at the same time without stepping on each other. 2. The build station gives the agent rules for how to write the code, because "it works" is very different from "a developer could open this repo next month and understand what happened." 3. The proof station makes the agent show evidence. Screenshots, videos, speed numbers, before-and-after states. It has to prove the thing works instead of saying it works. 4. The review station runs the work through a code review agent, and if it doesn't clear the bar, it goes back through the line. 5. Then you show up at the end to merge. For a 100+ years people have run production this way, and it worked because the structure is good. The full episode on what’s a software factory is NOW live on The Startup Ideas Podcast (SIP) 🧃 with the wonderful Micky Watch: So is it hype?!? I don't think it is, because of what it does to your output! WITHOUT a factory, you build ONE feature at a time and you're the bottleneck at every step, prompting, checking the diff, testing it yourself, hoping nothing else broke (spoiler alert it often does). WITH a factory, EACH feature runs in its own isolated copy of the app, so you can have 10+ of them going at once, and each agent has to prove its own work and pass a code review before it ever reaches you. Instead of supervising the work, you're APPROVING finished work that already has evidence attached. REALLY interesting to see how work with agents is evolving to be….well, similar to working with people!

GREG ISENBERG

30,787 views • 13 days ago