
Building https://nitter.cf/t.co/1bZdsKayV9. Toolmaker, motorcyclist, father, hunter, American, husband to @jeeyunit
San Jose, California
Joined July 2006
- Tweets5.6K
- Following1.2K
- Followers1.7K
- Likes22.2K
Rockets are cool
Fast iteration, transparency, autonomy, measured risk, depth of understanding where it counts
Incredibly inspiring watching my childhood dreams become reality on X
Replying to @DJSnM
Yes, the green flame is caused by burning copper from depleting fuel in the regenerative cooling circuit and going oxygen-rich (closer to stoichiometric temperature) in the main combustion chamber.
Slight underperformance of engines on this flight is the reason. The booster is meant to land with tiny residuals, so the solution is to improve engine performance and performance consistency (underway with Raptor V3.2), as well as adjust flight software to do MECO1 about one second earlier to ensure enough propellant for boostback and landing (tiny change).
These early ships and boosters are already outdated by improved designs in production or on the test stand, so this booster loss does not change our timeline to reach high volume, fully reusable Starship flights.
57
Using browser-use to self-verify agent-desktop timeline cards work
browser_exec and the new desktop_exec tool show live frames and screenshot evidence in the Paseo timeline
82
Reid Burke retweeted
Agentic coding benefits from powerful abstractions, just like humans do.
AI may well be able to write massive software projects “from scratch”, but that almost certainly isn’t the fastest / highest performance / highest security / most token efficient way to do things. Good building blocks matter.
In addition to RL’ing the agents on final task loss, we should try to get them to regularize the building blocks as well. What would the standard library look like that makes the agents most effective?
It is likely at the limit that it turns out to be some alien organization of code, but given the existing human-bias in training, I bet that in the near term it would be lovely code that old programmers would appreciate.
I suspect the same could be said for mathematics, but that is out of my lane.
Driving my Mac with agent-desktop in @paseo_sh
Introducing agent-desktop
Computer use for your agents
▲ E2E test desktop apps with agents
▲ Reads apps via the accessibility tree
▲ Drills into part of a window to save tokens
▲ Runs many agents on one app at once
▲ Works on macOS, Windows & Linux
npm i -g agent-desktop
61
we will need to rebuild and rewrite much of software to adapt to a new, faster pace.
code used to arrive one drop at a time. soon, if not already, code will be written as if it were a continuous stream, like a violent river twisting and turning as it pleases.
this is not a new thing: big tech cos have had to deal with this with the enormous scale of their engineering teams. but now ai has brought an incredibly elastic and capable workforce wielded by every engineer. this is your problem now, and the only way to adapt is to evolve your systems so agents - even and especially the ones with little context about the right way of doing things - can thrive. make the easy thing the right thing.
your codebase is becoming organic architecture. agent contributions grow around the constraints and guardrails you’ve designed. good software engineering matters even more now! and no, the continuous stream of code is not something you have to watch helplessly. be more ambitious and design systems, frameworks, and languages to control the chaos.
the time for mourning coding is long over
Replying to @josephfcox
Here is Proton CTO's AI manifesto, that I obtained multiple copies of 404media.co/manifestos-fear-…
Personal supercomputers are awesome
January’s SOTA intelligence for coding in your home for $4k and 65 W of power is wild
47



































