maintainer of @mapwithrapid and other open source mapping curios

New Jersey, USA
Joined August 2008
Replying to @bhousel
🧚‍♂️ Pixi v8 Upgrade! We upgraded Rapid’s render to use the latest version of @pixijs game engine. This version gives Rapid a welcome performance boost - if you’ve aired any grievances about Rapid being laggy, the new Rapid should perform much better for you! 2/6
1
9
792
Bryan Housel retweeted
13 years ago I thought "I should write a blog post about the economics of open source" but the outcome was too depressing. After noodling on it for a decade, I have finally finished the post. I wasn't expecting to end up at "Microsoft should send corporations a huge bill" but hey, a lot has changed. seldo.com/posts/nobody-pays-…
12
28
5
235
31,538
Gotta love the LLMs' standard response - because it's exactly what any mathematician would say if you showed up with this out of the blue.
hello there the jacobian conjecture is false thanx to my close friend akhil for asking about it and my other close friend fable for working during the world cup final ((1+xy)^3 z + y^2 (1+xy) (4+3xy), y + 3 x (1+xy)^2 z + 3 x y^2 (4+3xy), 2 x - 3 x^2 y - x^3 z): \C^3\to \C^3, has jacobian determinant -2, and sends (0, 0, -1/4), (1, -3/2, 13/2), and (-1, 3/2, 13/2) to (-1/4, 0, 0)
44
149
28
4,676
602,365
Bryan Housel retweeted
ever wondered if @googlemaps will route different people differently to lower overall congestion? turns out - they have been experimenting with this based on this recent paper in @NatCities key line - "For this study, the Google Maps algorithm was modified to prefer alternative routes with similar travel times and segment types, effectively guiding trips away from the pre-selected congested segments." result? "Averaged across citie ... a median increase of around 2% in driving speeds" research.google/blog/the-pow…
11
44
13
870
563,005
Bryan Housel retweeted
Knockoff is now live! Filter out the knockoff crap brands on Amazon. Sorry to brands like WNPETHOME, EHEYCIGA, YXYL, LU&MN, JOYIN, TOMY, GODONLIF, YOOJEE, LINGTENG, LANEIGE, VISCOO, BIODANCE, COOFANDY, BALENNZ, TOSY and LUENX. knockoff.shopping
built a little chrome extension that lets you dim (or hide!) all the crap, mass-produced, fake brands on amazon. should i release it?
1,205
3,896
451
55,100
11,723,617
LMAO @GitHubCopilot this is ridiculous. The thing you are offering in June isn't anywhere close to the thing I signed up for in January.
2
122
Npm pushing trusted publishing / OIDC was a mistake. So glad I never opted any of my projects into it. I will probably forever be manually publishing projects using short term 2FA tokens, and I feel good about that.
This attack leveraged GitHub Actions Cache Poisoning. Payload deployed here: github.com/TanStack/router/p… It looks like it detonated here: github.com/TanStack/router/a…
131
Bryan Housel retweeted
I want to get the most AI pilled folks in NJ for a meetup in Westfield. I have no idea how to source or find these people so please X do your thing!
195
13
2
310
78,526
Bryan Housel retweeted
🚨 CRITICAL: Active supply chain attack on axios -- one of npm's most depended-on packages. The latest [email protected] now pulls in [email protected], a package that did not exist before today. This is a live compromise. This is textbook supply chain installer malware. axios has 100M+ weekly downloads. Every npm install pulling the latest version is potentially compromised right now. Socket AI analysis confirms this is malware. plain-crypto-js is an obfuscated dropper/loader that: • Deobfuscates embedded payloads and operational strings at runtime • Dynamically loads fs, os, and execSync to evade static analysis • Executes decoded shell commands • Stages and copies payload files into OS temp and Windows ProgramData directories • Deletes and renames artifacts post-execution to destroy forensic evidence If you use axios, pin your version immediately and audit your lockfiles. Do not upgrade.
533
3,955
1,821
15,952
12,494,586
Bryan Housel retweeted
Prof. Donald Knuth opened his new paper with "Shock! Shock!" Claude Opus 4.6 had just solved an open problem he'd been working on for weeks — a graph decomposition conjecture from The Art of Computer Programming. He named the paper "Claude's Cycles." 31 explorations. ~1 hour. Knuth read the output, wrote the formal proof, and closed with: "It seems I'll have to revise my opinions about generative AI one of these days." The man who wrote the bible of computer science just said that. In a paper named after an AI. Paper: cs.stanford.edu/~knuth/paper…
144
1,836
311
8,994
1,419,243
Bryan Housel retweeted
The buried lede in this post is the October-to-December timeline. In October 2025, Karpathy publicly said AI agents “just don’t work.” Eight weeks later he’s 80% agent-coded and calling it the biggest workflow change in two decades. That’s the fastest opinion reversal from one of the most credible voices in AI, and it maps to something measurable. Stack Overflow’s 2025 developer survey tells the other side of this story. Only 16% of developers reported “great” productivity gains from AI tools. 45% said debugging AI code takes longer than writing it themselves. Meanwhile, the Claude Code team is shipping 20-27 PRs per day, 100% AI-written. That’s a bimodal distribution forming in real time. A small group is getting 10x leverage. The majority is getting modest autocomplete improvements and spending extra time fixing hallucinated code. Same tools, completely different outcomes. Karpathy names the variable: “ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions.” That’s a skill that looks nothing like traditional programming. You’re managing agents the way a senior engineer manages junior devs. Scoping work, reviewing output, catching failure modes, maintaining system-level context. The 10x engineer ratio he’s worried about is already here. 25% of YC’s Winter 2025 batch shipped codebases that were 95% AI-generated, and every founder was fully technical. They weren’t replacing skill with AI. They were compounding skill through AI. The gap between someone who can decompose a weekend project into agent-executable chunks and someone still typing code line by line is widening by the month. What makes this post different from the usual AI hype: Karpathy is explicitly naming the failure modes. Needs high-level direction. Needs taste. Needs judgment. Works better for well-specified tasks. This is an honest field report from someone who mass-reversed his own position 90 days ago, and that combination of enthusiasm and specificity is what makes the signal real.
It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow. Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes. As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now. It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.
12
19
1
145
24,816
I, too, ruminate on all my past dumb mistakes. My agent is just like me, but with a markdown file.
The secret file he didn't mention: `. learnings/LEARNINGS. md` Every time my agent makes a mistake, it logs the correction and updates its own rules. 43 skills. 661 lines of learnings. An agent that gets smarter every day. Your setup isn't just a moat. It's a flywheel.
1
115
Well this is a new one. I was working on a pretty extensive plan in @code and clicked "Continue in Background". The plan just disappeared from the chat as if it never happened. But wait..
1
1
99
Then, I just asked it "I haven't seen VSCode lose a substantial chat before. Try to think of ways that we could get it back"... 🤨
1
71
Claude actually - probed into VSCode's internal chat storage, figured out the storage format, and wrote some temporary python programs to recover the missing chat. I'm still in shock 😳🤯 WTF! Never seen anything like this.
67
This will end OpenAI, if they really do decide to go this route.
OpenAI’s CFO says the company will take a cut of the IP its AI helps customers invent.

44
Bryan Housel retweeted
I recently learned the USGS has free aerial LiDAR data for many areas. Draw a box, then click the green button on the right side and select Eptium viewer. apps.nationalmap.gov/lidar-e…
36
429
48
5,298
1,216,553
I guess we're really doing this.
75