Codio
@0xCodio • 2,548 subscribers
Videos
Fable 5.2 now builds rocket parts in Blender around the exact point where they are meant to break Every part fails eventually, and in flight hardware the only question that matters is which one goes first and what it takes with it. Nobody places a weak point by hand, a Python script runs the loads and writes the failure order into the geometry: > Load: real flight forces applied to every surface > Rank: parts sorted by what their failure destroys > Shape: the chosen break point thinned on purpose • What designing the failure buys > A bracket that yields before the tank it holds > A mount that shears clean instead of tearing > A failure that happens where sensors already sit • Why strongest everywhere is the wrong target > Making one part stronger moves the break elsewhere > An unplanned failure path is just an unknown one > Mass spent on the wrong part is mass off the payload A full assembly gets its failure order in about five minutes. And the part that broke my brain: The over engineered version survived the test and took the structure around it down. The deliberately weakened one broke first, alone, and everything above it flew. Same assembly. One version decided nothing about how it dies. Strength was never the goal. It was choosing which part goes first ↓
Codio41,601 Aufrufe • vor 3 Tagen
A Chinese fab wired Anthropic into its chip pipeline and cut design costs to almost nothing Most of a chip isn't the clever part, and teams still pay senior engineers to redraw all of it every generation. They split the die by who should own it, the commodity half generated and verified automatically, the differentiated half left entirely to humans: > Classify: every block is tagged as commodity, adapted or genuinely novel > Generate: commodity blocks are produced from the house rules, not redrawn > Verify: those blocks are checked automatically against the same rules > Reserve: the novel blocks never enter the pipeline, engineers own them outright • What counts as commodity and nobody admits it > Power distribution, clock trees, scan chains, reset logic > Standard interfaces that have been the same for fifteen years > Test structures that get copied from the last project anyway • Where the savings actually come from > Roughly 70% of the die stopped consuming engineer hours > The same senior people now spend all their time on the 30% that matters > A new generation reuses the rules, so the cost drops again each time The commodity half of a die regenerates in about two hours. And the part that broke my brain: Their best engineers had been spending most of each project redrawing clock trees. The pipeline took that work away and the headcount stayed the same. Same silicon. One version pays senior salaries for solved problems. The expense was never the hard part of the chip. It was everything around it that nobody wanted to own ↓
Codio21,580 Aufrufe • vor 9 Tagen
Chinese engineering team builds the robot's chip and its control code as one artifact, and neither one is written by hand Most robotics splits the two, a silicon team ships a processor and a software team spends a year discovering what it's bad at. They generate both from the same movement spec, so the chip knows what motion it exists to serve and the code knows what the silicon can hold: > Describe: the robot's reach, payload, cycle time and safety envelope go in as text > Co-solve: the control loops and the silicon that runs them are generated together > Burn: the chip layout and the firmware come out matched, nothing adapted later • What co-generating actually eliminates > Control code shaped around a latency the hardware never had to impose > Silicon carrying units the motion profile will never once call > The six-month handoff where each team learns what the other assumed • Why this only works generated > A human can't hold both the floorplan and the control math in one revision > A change to the payload re-solves silicon and software in one pass > The tradeoff between them becomes a value, not a negotiation One robot's chip and control stack regenerate from spec in about two hours. And the part that broke my brain: The usual process takes a year and ends with software apologising for the hardware. This one regenerates both overnight and they were never designed apart. Same robot. One version is two teams guessing about each other. The bottleneck was never the chip or the code. It was the wall between them ↓
Codio26,786 Aufrufe • vor 13 Tagen
A molecular model that only reports the connections no single paper could have seen Most research builds one link at a time, a protein to a pathway, a pathway to a symptom, and each study stays inside the field that funded it. This one holds every published link as a graph and goes looking for paths that cross fields nobody reads together: > Link: 40 years of findings become edges, each dated and sourced > Walk: it traverses paths of three and four hops across different literatures > Surface: only paths where no two edges come from the same research group • What crossing fields turns up > A metabolic enzyme tied to a neurological symptom through two unrelated papers > A drug side effect explained by a pathway described in agriculture research > Two diseases sharing a mechanism neither field had reason to compare • Why nobody found these by reading > A four-hop path spans four journals nobody subscribes to at once > Each individual edge is unremarkable, the path is the finding > Specialisation is what makes the gap, not laziness • How it avoids inventing connections > Every hop names the paper and the year it held true > A path with one expired edge is shown broken, not completed > It proposes the experiment that would test the path, or drops it One full traversal across the corpus runs in under three minutes. And the part that broke my brain: Two labs published halves of the same mechanism eleven years apart. Neither cited the other, and nothing in either field would ever have connected them. Same literature. One version can only see what someone already assembled. The discovery was never in a new experiment. It was sitting between papers nobody read together ↓
Codio30,926 Aufrufe • vor 19 Tagen
Anthropic's modelling stack writes ribosome scripts that run the translation instead of animating it Most ribosome visuals are choreographed, which means the animation can only ever show what someone already believed. Here the ribosome is a script with rules, and what you watch is whatever those rules produce when you feed it a real sequence: > Encode: each step is written as a condition, not a keyframe > Feed: an actual mRNA sequence goes in, codon by codon > Run: the ribosome moves because the rules fire, not because a timeline says so • What emerges that nobody animated > It stalls on rare codons, exactly where the tRNA pool runs thin > A frameshift happens on its own when the sequence sets one up > Two ribosomes on one transcript collide, because nothing stopped them • Why a script beats an animation > Change the sequence and you get a different movie, not a re-render request > A behaviour that surprises you is a result, not an artistic choice > The same script runs 10,000 sequences overnight and reports the odd ones • Where it stays honest > Every rule traces to a measured rate, not a guess > A step with no rate in the literature refuses to run silently > The output logs which rules fired, so a weird result is debuggable One sequence translates in real-time-equivalent in about 40 seconds. And the part that broke my brain: Every animation I'd seen showed translation running at one smooth constant speed. Fed a real gene, the script stalled three times and one of the stalls is documented. Same process. One version could only show what its animator knew. The hard part was never drawing the ribosome. It was letting it do something nobody scripted ↓
Codio25,889 Aufrufe • vor 20 Tagen
A Chinese chipmaker cancelled $4M a year in engineering hires and spent it on Opus 5.5 instead, and shipped ten times the designs Most of the cost in chip design was never compute, it was the months of senior time spent turning a spec into something manufacturable. They moved that work to the model and kept the people on judgement, so the floor now runs more projects than it has engineers: > Spec: requirements go in once, as text, for every project on the floor > Generate: layouts, verification setups and test benches come out of the same spec > Review: engineers only read what the model flagged as uncertain > Ship: the rest moves to tapeout on the house rules it was generated against • What the token math actually looks like > Opus 5.5: $4 per million in, $20 out, cache reads at $0.20 > Batch rates halve that again, $2 in and $10 out, for anything that can wait > A full design pass lands near $30 in tokens against weeks of engineer time • Where the 10x actually came from > The same headcount now carries ten projects instead of one > Verification stopped being the queue everything waited behind > Revenue scaled with projects shipped, not with people hired One full design pass regenerates in about 40 minutes. And the part that broke my brain: Their old limit was how many senior engineers they could hire in a year. The new limit is how many customers they can sign, and the token bill barely moved. Same floor. One version was capped by a hiring market. The constraint was never the silicon. It was how many people had to touch it ↓
Codio10,842 Aufrufe • vor 7 Tagen
A university lab had an LLM build 3D molecules and only kept the ones the model itself couldn't explain Most generative chemistry rewards confidence, which means the output is a very expensive average of the training set. They inverted the filter, the model builds the structure and then has to justify why it works, and the ones it can't justify are the only ones that go forward: > Generate: structures are built against the target property as usual > Explain: the model writes the mechanism it believes makes each one work > Score: a confident, familiar explanation sends the candidate to the discard pile > Keep: anything it builds but cannot account for goes to the bench • Why the unexplainable ones are the valuable ones > A structure the model can explain is one the literature already implies > Novelty lives exactly where the learned pattern stops predicting > The explanation is a proxy for how crowded that chemical space already is • What came out of the first run > Four scaffolds with no close analog in any published series > One binding mode the model described as unlikely and the assay confirmed > A discard pile full of compounds three other groups were already patenting • Where this breaks if you're careless > Unexplainable also describes garbage, so synthesis screening runs first > Every keeper has to survive the same physical validity checks > A candidate with no route to the bench is dropped regardless of novelty One generate-and-filter cycle produces about 30 keepers from 400,000 builds. And the part that broke my brain: Every other pipeline ranks candidates by how sure the model is about them. This lab reads that same confidence as proof somebody already got there. Same model. One version optimises for the middle of what's known. The hard part was never generating molecules. It was noticing that the confident ones are the crowded ones ↓
Codio11,408 Aufrufe • vor 17 Tagen
Keine weiteren Inhalte verfügbar