Pierce Primm, Sr. (@PiercePrimm) header
Pierce Primm, Sr. (@PiercePrimm) profile picture

Software Developer, Crestron Master Programmer, Houston IoT Meetup Host. Teacher of JS, MQTT, IoT, Arduino, RPi.

Houston, TX
Joined August 2013
Photo by Pierce Primm, Sr. (@PiercePrimm)Photo by Pierce Primm, Sr. (@PiercePrimm)Photo by Pierce Primm, Sr. (@PiercePrimm)Photo by Pierce Primm, Sr. (@PiercePrimm)Photo by Pierce Primm, Sr. (@PiercePrimm)Photo by Pierce Primm, Sr. (@PiercePrimm)Photo by Pierce Primm, Sr. (@PiercePrimm)Photo by Pierce Primm, Sr. (@PiercePrimm)Photo by Pierce Primm, Sr. (@PiercePrimm)Photo by Pierce Primm, Sr. (@PiercePrimm)
Pierce Primm, Sr. retweeted
PCBs made in America. Twice as fast as Shenzhen. Today @CircuitHub is unveiling The Grid, our factory-scale robot in Massachusetts that builds circuit boards on demand. No changeovers, no per-design setup. Prototypes and production batches, fully automated.
358
673
221
7,226
420,256
Pierce Primm, Sr. retweeted
RAM is the new bottleneck. Every Node.js process is fighting for memory: containers, serverless, cloud bills, k8s limits. And here's the maddening part: V8 can use half the memory with one flag, and almost nobody turns it on.
46
73
18
1,259
77,737
Pierce Primm, Sr. retweeted
There's a lot of reasons I hate the "P(doom)" concept, but one of them is that it conflates P(ruin|ASI) and P(ASI). P(ruin|ASI) where the ASI is built by anything remotely resembling current techniques, or by new techniques invented and managed by any LLM resembling Astra/Fable, as meddled-with by current personnel at current AI companies, is "Yes" on my current estimate. P(ASI) marginalizes over P(ASI|policy_i) and P(Policy). And while I've heard other people pontificating that they definitely know what the Policy will be, I do not find their arguments convincing. I wouldn't claim to have a very solid forecast myself. So I do not have an equally solid opinion about P(ASI) as I do about P(ruin|ASI). I do know some spots where other pontificators seem to me wildly optimistic about P(ASI|policy_i), and for this reason I am more scared than some others, and think a more hardline Policy is required to succeed. Conversely, some accelerationists would like you to believe P(ASI|policy_i) is 1 for all policies, so that you won't be able to think about how to pick a Policy for which P(ASI|policy_i) is lower and thereby successfully prevent ASI. Accelerationists put forth motivated overestimates of P(ASI) and call that "Yes", so that your only mental refuge from uncomfortable thoughts will be misestimating P(ruin|ASI). But to say all that is around as much further refinement and expertise as I can manage to bring to bear. Sane people will have strong opinions about particular causal links in the World that are unusually easy to forecast, rather than imagining themselves experts about the entire World and able to casually marginalize over its entire causal lattice. Sane discussion will generally focus on pieces of Reality. Even an expert on the entire field of ASI alignment can only ever tell you about P(ruin|ASI_i); though also, importantly, we can rule out it being easy to construct a bunch of hopeful particular ASI_k that particular loony optimists think they can imagine. People who yell back and forth about the whole World will never be able to communicate anything but vibes. People trading P(doom) like it was their new astrological sign are systematically making prominent a malformed topic to discuss. And the word "doom" is not helpful for serious discussion, and everyone against ASI ruin who did not flatly reject the word "doom" every time it was used has made a serious mistake (or perhaps, profited in the short-term at humanity's long-term expense) by failing to uniformly oppose its entry to the discourse. And likewise, ASI advocates who claim to be in favor of serious discussion have falsified that claim and exposed their lack of integrity if they helped popularize "doom" or "doomer" themselves.
101
42
31
640
89,221
Pierce Primm, Sr. retweeted
Would love to host this on EconTalk. I would moderate. I am mostly agnostic on this issue. Let me know if you're interested. @sapinker @slatestarcodex
I think you've done enough calling us paranoid and preposterous. The next step is for you to defend your position in public against someone who will push back against it. I'm happy to meet you for a debate anywhere, anytime. You're a world-famous veteran of dozens of debates against the world's top intellectuals, and I've never argued in public before, so adjusting for the relative correctness of our positions, if you're a betting man I'm happy to put my $5000 against your $1000 (ie 5:1 odds in your favor) that I'll win by some standard of audience opinion change. Let me know if you're interested and we can hash out details.
19
33
4
610
34,179
Pierce Primm, Sr. retweeted
#DietPi v10.7 has been released! We have new images for the LubanCat 4, ARM64 VMs, and containers with virtual network. The home inventory and organization system #HomeBox, and the video integration platform @scryptedapp joined our software catalogue. dietpi.com/docs/releases/v10…
2
11
54
1,158
Pierce Primm, Sr. retweeted
Given we don’t write code anymore… why are we still dealing with TypeScript and transpilation? Models can write perfect JS in less tokens.
263
36
44
1,496
202,730
Pierce Primm, Sr. retweeted
✨ I replaced all these SaaS with my own vibe coded now, so about $25,000/mo savings: - Weather API -> My own vibe coded weather service using Norway's meteorology API - Image resizing API -> My own vibe coded image resizing API with NodeJS's Sharp + Redis (saves ~$1,500/mo) - Google Vision NSFW detection -> My own $0/mo vibe coded NSFW detection service with Python's NudeNET (saves ~$2,500/mo) - Cloudflare Streaming -> My own $0/mo Nginx VPS video streaming (saves ~$250/mo) - API Flash -> My own $0/mo screenshot service (for social images) (saves ~$250/mo) - New Relic + IPHub -> My own $0/mo error monitoring, DDOS blocking and fleet management service (called error2telegram) (saves ~$250/mo) - Human moderators -> My own moderation on all my sites with @xAI (saves ~$10,000/mo) - IFTTT -> Telegram bot (saves ~$100/mo) - Photopea as editor inside Photo AI -> Vibe coded my own photo editor (saves ~$100/mo) - Mapbox -> Vibecoded my own free replacement with OpenFreeMaps (saves ~$500/mo) - Uptimerobot -> My own $5/mo Uptime Canary app running on Kuma (saves ~$50/mo) - Ghost blog -> My own $0/mo blog platform - Customer support -> @featurebasehq + AI support bot (saves $5,000/mo) - Scrapingbee/SerpAPI -> My own $1/mo scraper with Patchright (save ~$250/mo) I think I have reached my final limit of replacing my SaaS services as I have these left, but that'd mean becoming an ICANN registrar (I don't want 😁), managing my own email (I don't want), managing my own hard drives at home in a storage (I don't want) and managing my own servers at home too (I don't want) and running my own GPU rig at home (I don't want): - Cloudflare Domains - Cloudflare Email Sending - Cloudflare R2 Storage - Backblaze B2 for backups - Hetzner for all my servers for all my sites (VPS) - xAI for all LLMs for all my sites (so many things like moderation, writing emails, anything)
✨ Okay with lots of help from @javilopen and his Spanish scraping friends I've managed to vibe code my own @Scrapingbee alternative and replace my $249/mo Scrapingbee plan with my own $1/mo scraper running on my VPS! First I tried OpenSERP, an open source project that seems freshly maintained but it didn't work on my VPS IP or laptop IP and got blocked fast Then I tried to use residential IP proxies from IPRoyal but they were already quite tainted IPs meaning Google already knew they were scrapers and just blocked about 60% of them already, not so great, also didn't work! Then I discovered OpenSERP uses a vanilla headless Chrome, Google instantly detects that and blocks that, so literally the entire repo is useless cause it won't even work? I don't get why they don't say that in the docs? OpenSERP is even worse than just basic CURL, as my AI said: "plain curl got 7% blocked but OpenSERP's headless browser got 100% blocked" So then I just built my own with Playwright and a real Google Chrome on my VPS, headful and persistent context, and slow pacing like every 30 seconds or so And I got some better residential IP recommendations (which I can't tell you because thenhey t stop working!) Now I'm at about 90% success rate, which is similar or better than Scrapingbee And it costs me ~$1/mo (measured by GBs, obviously for text scraping I barely use a lot) instead of the $249/mo I paid Scrapingbee! My only remaining SaaS now are: - Cloudflare Domains - Cloudflare Email Sending - Cloudflare R2 Storage - Backblaze B2 for backups - Hetzner for all my servers for all my sites (VPS) - xAI for all LLMs for all my sites (so many things like moderation, writing emails, anything)
358
224
142
4,533
896,877
Pierce Primm, Sr. retweeted
Who's doing the first agentic bank? I want to give my machine an agent account, an allowance, and permission to just take care of stuff.
939
146
112
4,374
473,256
Pierce Primm, Sr. retweeted
we're headed to Austin! 🤠 thursday evening, we're hosting a Grok Bot for GTM build night in atx. build GTM workflows, free credits, and live demos from our @spacexai GTM team!
60
22
11
593
52,648
Pierce Primm, Sr. retweeted
> i want you to design whatever your heart designs out of sheet and/or tube metal that is orderable from rmfg (use the mcp to dfm / quote). give me a review link to it once you are done. you can design whatever using whatever tools you need. this is what codex wants us to make
18
3
3
81
14,410
Pierce Primm, Sr. retweeted
PlatformIO Open Source August Updates are here 🚀 ✅ New boards & dev-kits ✅ ESP-IDF 6.1 ✅ Zephyr RTOS 4.4.2 ✅ Support for STM32C0xx Family ✅ Updates for Espressif and ST STM32 dev-platforms 👉 piolabs.com/blog/news/platfo… 📌 #OpenSource #Technology #EmbeddedSystems #Semiconductor
1
3
10
731
Pierce Primm, Sr. retweeted
Omarchy is blowing up. I've never been involved with anything in my career that has grown this fast. With Ruby on Rails, we had years to build solid institutions, teams, and relationships. With Omarchy, we've been forced to figure it all out in twelve days. It's exhausting, but also incredibly exciting. It was never sustainable with just Ryan and me running everything. That's how it was, more or less, up until Quattro. Lots of other contributors, but all the responsibility was on us to make sure the ship stayed afloat, the servers didn't crash, and fixes got pushed out quickly. Now it's time to build a proper institution. Durable, resilient, and competent. That's what we're doing here on Basecamp now. I'm spinning up teams for every facet of responsible distro management, and I'm getting an absolute outpouring of interest for all of them. Everyone wants to be part of this. We're winning hearts, minds, and volunteers at an astounding rate. Great! We need all of it to succeed. Because make no mistake: There are many people who'd love to see this rocket blow up before it reaches the moon. Aggrieved Linux users who don't like the sudden attention their exclusive hobby has received. Competing Linux distributions that are seeing our numbers explode. Mac stans who've sunk their identity into an apple. And, of course, any of the haters I've picked up in my quarter-century career speaking bluntly on the internet. They're not going to succeed. Because we've already become unstoppable. There's too much momentum, too much money, and too much support now backing this effort. We're living the Mandate From Heaven meme at the moment. And we are here to fulfill the prophecy: The Year of Linux on the Desktop! That has been a joke for two decades. But by the end of the year, nobody at Apple or Microsoft is going to be laughing. They're going to be scrambling. Because neither of these proud organizations currently has any method to counter the speed, vision, or ambition with which we're going to accelerate into the future of personal computing. This is the moment. This is the opening. This is our chance. For thirty years, we've been subject to one OS overlord or another. Dictating how we compute. Choking off competitors through platform malfeasance. Tollboothing the distribution. That ends now. Because Linux is going to win. And Linux is free. As in beer, speech, and source. But just because it's inevitable doesn't mean it's going to be easy. We have a lot of work in front of us if we actually want to make our mark. But there's never been a better time for this kind of delusional ambition. The age of agents is the unlocking factor. It sounds like a LinkedIn slogan, but it's true. Where the application of tokens goes, the innovation follows. We can fix everything. Let's do it together. Let's go. --- This is what I sent to the dozens of new volunteers who've signed up for teams within the new Omarchy organization yesterday. But we might as well broadcast our mission and intentions to the world too.
354
564
136
8,908
902,559
Pierce Primm, Sr. retweeted
Here's my conversation with @DHH. He is back for round 2! It was an epic fun 5 hour conversation about the future of programming, AI, Linux, and human civilization. It's here on X in full and is up everywhere else (see comment). Timestamps: 0:00 - Episode highlight 1:27 - Introduction 2:56 - Programming with AI agents 18:14 - How software will change 27:30 - AI impact on open source 37:21 - Building Omarchy Linux distro 47:05 - Vibe coding vs agentic engineering 1:00:06 - The end of manual programming 1:10:24 - Advice for programmers 1:22:30 - Surviving Internet Hate 1:31:46 - Programming setup for AI Agents 1:44:11 - Obsessing about speed 2:07:06 - Voice prompting vs typing 2:21:05 - Best AI coding models 2:37:55 - Best AI coding harnesses 2:50:57 - AI video generation and filmmaking 3:10:28 - Fatherhood 3:38:35 - Linux will win the desktop 3:49:51 - PewDiePie 3:59:24 - Future of programming 4:22:17 - Politics and immigration 4:53:54 - Longevity, over-optimization, and fear of death 5:05:38 - Eternal recurrence and future of human civization
360
470
176
4,616
921,089
Pierce Primm, Sr. retweeted
Omacom Foundation funding has now hit TEN MILLION DOLLARS thanks to @drewhouston and @steipete joining as Founding Patrons with $1 million each for the mission. Couldn't be more thankful! I know just where to send some of the money... omarchy.org/news/2026/08/oma…
115
158
55
3,683
624,881
Pierce Primm, Sr. retweeted
WOW! The $8 AI Machine! Something extraordinary just happened and it changes what “local AI” can mean. I am testing it tonight. Thus far it shows many possibilities… So what it this $8 AI device? A developer going by slvDev has forced a 28.9-million-parameter language model onto an ESP32-S3 microcontroller that costs roughly eight dollars. Not a Raspberry Pi. Not a Jetson. An eight-dollar microcontroller. The model runs completely offline, generates coherent short stories at about 9.5 tokens per second, and draws power measured in the same range as a small LED. This is more than a hundred times larger than the previous record for the same class of chip (the earlier 260,000-parameter TinyStories experiments). For perspective, the original ChatGPT sat at 117 million parameters. We are now running a model roughly a quarter of that size on silicon you can buy for the price of two coffees. How the Impossible Became Possible The ESP32-S3 has only 512 KB of fast SRAM, 8 MB of PSRAM, and 16 MB of flash. Conventional wisdom said a model of this size simply would not fit. The breakthrough is architectural, not brute force. Most of a language model’s parameters live in a giant embedding table a lookup table you mostly read from, not compute against. Drawing directly from Google’s Per-Layer Embeddings technique (the same family of ideas used in the Gemma models), the developer moved the bulk of that table roughly 25 million parameters into flash memory and memory-mapped it. The chip only needs to pull about six rows, roughly 450 bytes, for each new token. The remaining dense “thinking” core stays in the fast SRAM (around 560 K of active working memory). The model is stored at 4-bit quantization and occupies about 14.9 MB total. The result is a system that feels almost free to run. The heavy parameters sit quietly in flash and are sampled sparingly. The little core does the real work. It is elegant engineering of the purest kind. What I Am Doing With It Right Now I have the boards on the bench in the garage lab. The first units are already talking short, coherent stories appearing on a tiny wired display, generated entirely on the chip with no Wi-Fi, no API key, no cloud round-trip. Latency is local. Privacy is absolute. Power draw is low enough that battery operation becomes interesting. I am treating these as the first generation of true $8 AI machines. Early tests are focused on three practical directions. - Embedding the model into simple nodes. - Pairing it with local voice front-ends - Exploring whether multiple of these chips can be networked as a lightweight swarm. The model is deliberately limited. It was trained on the Microsoft TinyStories dataset and is excellent at coherent narrative, not at open-ended question answering or tool use. That is a feature, not a bug. It forces us to design systems around what the silicon can actually deliver instead of pretending every edge device needs a frontier model. Real Use Cases That Suddenly Become Practical Once you accept that a capable language model can live for eight dollars and run without the cloud, a new class of devices becomes possible: This is the opposite of the current trajectory that wants every intelligent act to travel through a remote server. It is the beginning of intelligence that is cheap enough, private enough, and local enough to become infrastructure rather than a service. We have spent years watching model sizes explode upward. The more interesting frontier may be the opposite direction: how small, how cheap, and how local can useful intelligence become? An eight-dollar chip that can tell coherent stories is not a toy. It is a proof that the lower bound keeps moving. The open repository is at github.com/slvDev/esp32-ai I will keep testing, measuring, and reporting what these little machines can and cannot do. The age of abundant local intelligence just got a little more real, and it arrived wearing an eight-dollar price tag.
194
469
115
3,105
425,115
Pierce Primm, Sr. retweeted
Watch git diff while the code is changing! 🤯 👁️ livediff — A real-time diff viewer for the terminal 💯 Watch file changes live as generators, formatters, migrations & refactors modify your code 🦀 Written in Rust & built with @ratatui_rs ⭐ GitHub: github.com/SoCkEt7/Livediff #rustlang #ratatui #tui #git #terminal #devtools #opensource
10
26
2
435
36,643
Pierce Primm, Sr. retweeted
Texas A&M now has the most powerful supercomputer among United States universities. VISION, the Texas A&M supercomputer, debuted at No. 66 on the prestigious Top500 list, ahead of machines operated by Samsung, Dell, Microsoft and numerous national and international agencies and laboratories. The supercomputer triples Texas A&M's previous supercomputing capacity and positions the university as an epicenter for impactful AI education and research. Read more: tx.ag/pWJI9Rd
23
83
15
657
79,474
Pierce Primm, Sr. retweeted
VLANs do not automatically make a homelab secure. They create boundaries. The firewall rules decide whether those boundaries actually mean anything. Segmentation without policy is mostly nicer network diagrams. #HomeLab #Networking #Security
6
1
34
3,920
Pierce Primm, Sr. retweeted
Bu robot, 50’den fazla kavşak arasından en hızlı rotayı kendi başına seçiyor.
78
137
17
8,986
2,924,178
Pierce Primm, Sr. retweeted
In many applications, you need a map from strings to integers. In python, you might do it like so... d = {"apple": 100, "banana": 200, "cherry": 300} If you have 1 million keys, that can use a lot of memory!!! Like over 100 bytes per key! I have published a new library that uses about 9 bytes per key. That's right. Just 9 bytes. You use it like so: from fastconstmap import ConstMap d = {"apple": 100, "banana": 200, "cherry": 300} m = ConstMap(d) m["apple"] # -> 100 m.get_many(["banana", "cherry"]) # -> [200, 300] It can be significantly faster (e.g., 2x in some cases) than the a standard dict. Further, you can serialize it and deserialize it to disk or to a network for convenient reuse.
27
29
296
43,772