Engineering. 🚧 Distributed Protocols - Wallets - AI | open source. I'm a car enthusiast.

Joined July 2017
62 Photos and videos
Pinned Tweet
8 Sep 2021
Building cryptographically secured systems is all about guarding and building defenses against replay attacks until you die πŸ˜…
1
12
Regulatory capture
There's some weird games being played by some of these AI labs, it'll all make sense in a few months from now
1
20
There's some weird games being played by some of these AI labs, it'll all make sense in a few months from now
39
Slowly the madness will come to an end....
More AI-generated code doesn't make your team faster. It might actually slow you down.
46
I don't think the chassis for such old cars was designed to hold heavy EV powertrains
These guys are artists. Moment Motor takes classic cars and turns them electric. It's two to four months of work and can cost $175,000. Tons of people in tech land send their cars to Austin to get modernized. Full episode here.
26
SF crowd so obsessed with not being left behind that they'll jump on anything just to feel avant-garde πŸ˜…
14
Ed πŸ€ retweeted
Weekend experiments: got local TTS running on mobile with QVAC, and the results are looking really promising. It's great to see more AI workloads moving fully on-device. New article dropping soon with a deeper dive. Mobile inferencing is coming along nicely. πŸš€ @qvac
2
2
5
102
This has always been a wrong analogy πŸ˜… Assembly to a higher level language is deterministic nature. Prompting a chatbox for code generation isn't
You do realize there’s no AI bubble and we’re not going back to writing code by hand, ever? Hint: there’s a reason why you’re not writing assembly by hand
1
735
Something very sad about devs who are now fully relying on AI code generation is the fact that they can't really think for themselves anymore. This is literally brain atrophy happening in real time. Very sad!
1
1
44
When if you're reviewing a PR that was mostly done by AI, you ask the PR author a question, they can't explain what or why they this or that! 😭 They literally prompt back into AI chatbot again and come back with another AI slop response. This here is even more sad
35
Most people aren't aware this car has some of the lowest max load capacity. Around 375 kg ◉⁠‿⁠◉
The Jetour T2 has a very small boot. Its just slightly bigger than a hatchback's boot.
1
118
39
Ed πŸ€ retweeted
Figure parking lot on Monday
Today, we're announcing the completion of a $100 million employee tender at Figure To solve general robotics, we need the best engineers on the planet and as a private company I'm glad to be providing liquidity along our journey
107
63
2,848
518,738
Ed πŸ€ retweeted
Some lore on mobile inferencing: I’ve been playing around with QVAC lately, and I’m honestly surprised by how fast local inference has become on modern phones. A few years ago, the idea of running an LLM directly on a smartphone sounded ridiculous. @qvac
2
1
2
158
GitHub down again πŸͺ« #github
2
120
Ed πŸ€ retweeted
Levie’s Law of AI Psychosis: The farther away you are from the actual work the more confident you are that humans are no longer needed I like it
CEOs are uniquely prone to AI psychosis because they’re sufficiently distant from the last mile of work that still has to happen to generate most value with AI. So when they play with AI, they see the happy path results, often not considering the next 10 or 20 things that have to happen to get sustainable results from agents. β€œLook I made this awesome product prototype”. Yes but you didn’t have to review the code before it went into production and fix a bunch of issues. β€œLook I generated a contract”. Yes but you didn’t verify all the terms before it goes out to the counterparty and didn’t have to wire up all the past contracts to work with. The best thing you can do as a CEO is to use AI a *ton* to figure out the real implications of agents in the enterprise, and come out the other side with an appreciation for both the upside and the real work that goes into them.
76
881
7,668
442,672
May 19
We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.
1
53
Future markets for compute/capacity...
May 19
customers are increasingly asking us for certainty on capacity. as models get better, we expect that the world will be capacity-constrained for some time. we are offering discounted tokens for 1-3 year commits. (it also helps us plan, so hopefully a big win-win.)
39
Ed πŸ€ retweeted
It is a shame that the simple act of transferring a large block of data as fast as possible over the internet is not handled effectively by the primitive operating system calls. You either multiplex over parallel persistent TCP connections to combat head-of-line blocking and slow starts, or reinvent reliable delivery and flow control over UDP. QUIC has a lot going for it, but it is a large library (six figure LoC!) and conflates security and performance in a way I don’t love. There is also fundamental information about competition with other processes and link layer congestion that should be useful, but is unavailable to user libraries. You should be able to just write(really_big_buffer) and it is all taken care of for you.
156
148
3,280
264,466
Ed πŸ€ retweeted
May 11
This malware deletes your full system as soon as you revoke the API keys it stole from you
SECURITY ADVISORY β€” TanStack npm packages A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package. Status: ACTIVE β€” packages are deprecated, npm security engaged, publish path being shut down. Severity: HIGH β€” payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys. If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised: β€’ Rotate cloud, GitHub, and SSH credentials immediately β€’ Audit cloud audit logs for the last several hours β€’ Pin to a prior known-good version and reinstall from a clean lockfile Detection β€” the malicious manifest contains: "optionalDependencies": { "@tanstack/setup": "github:tanstack/router#79ac49ee..." } Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root). Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level. Full technical breakdown, complete package and version list, and rolling status updates: github.com/TanStack/router/i… Credit to the security researcher for responsible disclosure.
12
47
557
107,253
Ed πŸ€ retweeted
Compilers are deterministic. Give them the same code with the same compiler settings, and you'll always receive the same binary. You can take responsibility for your software at the code level. LLMs, on the other hand, are stochastic. Even if you set the temperature to zero, you're likely to get different responses on the same prompt. Therefore, you need to understand the code it produces if you want to take ownership and responsibility for it.
We're definitely going to get to the point where handwriting code doesn't make sense. Similar to handwriting assembly doesn't make sense. But the analogy breaks down. Developers don't really know assembly and they can't really review assembly. On top of it, the assembly that's produced by compilers is so optimized and confusing that you can't even understand it. For AI the code that's being produced, the developer needs to understand it could have written it themselves but it's just not as efficient or safe to do so. AI is not a new abstraction layer. It is a tool to create something you understand. We still need people to understand the mechanics of coding. We still need people to learn these skills and these are important skills. And even with the power of AI, you can't get away with not knowing these skills if you want to be effective. As always, there'll be people who try to take shortcuts and they'll get short-term gains and then it will fall apart.
114
204
2,530
213,854