legacycode.dev/source-code/
is not making a “AI will replace programmers” argument. It’s making a systems argument about where bottlenecks move when implementation becomes cheap.
execution scales,
context doesn’t,
and human ambiguity becomes the dominant engineering problem.
Bobbi Perreault retweeted
Disclosure first, because the work argues for it: an AI drafted this, from research I scoped and reviewed.
That's half the subject. In 2015 the risk was getting caught looking something up. In 2026 it's the recorder you didn't mention. New series on what's left of senior engineering when the code is the easy part.
legacycode.dev/source-code
Bobbi Perreault retweeted
Never heard so many standout infra engineers + AI infra eng actively wanting to leave Meta than now.
A month ago they were building cutting-edge infra and then got assigned to AI data labelling
Most of them went “WTH” and now I’m the middle of interviewing
Madness from Meta
Bobbi Perreault retweeted
What's actually happening to the web right now, versus what's being sold? Six pieces, 49 sources, produced with AI agents directed against the research. Some of it is clearer than expected. The rest is a field in a snowstorm. 844,000 sites adopted llms.txt. Zero crawlers read it. A $33.7B optimization industry can't measure whether its fixes work. AI answers change 70% of the time. The small businesses everyone claims to be helping don't appear in a single dataset about their own future.
legacycode.dev/towton
This one just dropped! legacycode.dev/towton
Fair warning - this account is going to start including some posts about software development and the industry alongside the usual. I've been writing at legacycode.dev and I'll share pieces here when they're worth sharing. If that's not your thing, absolutely no hard feelings. Unfollow button's right there and we're still good.
1
12
North Korea is targeting npm maintainers -- not for crypto, but for write access to packages downloaded trillions of times a year.
Several Socket engineers were targeted in this campaign -- myself, @ljharb, @jdalton, and others. None of us fell for the bait. Unfortunately, the axios maintainer did. No shame in that -- these aren't phishing emails. They're weeks-long ops with fake companies, fake Slack workspaces, and spoofed meeting platforms built with realistic Zoom/Teams interfaces using the official SDKs for realism.
Other confirmed targets: @matteocollina (Fastify, Pino, Undici, Node.js TSC Chair), @wesleytodd (Express TC), @voxpelli (mocha, neostandard).
The common thread? High-trust maintainers with publish access to packages that sit deep in everyone's dependency tree.
The attack chain: build rapport over weeks, schedule a video call, fake an audio error, prompt the target to install a "fix." That fix is a RAT. Once it's on your machine, they have your .npmrc tokens, browser sessions, AWS creds, keychain. 2FA doesn't matter. OIDC publishing doesn't matter. Game over.
Security researcher @tayvano_ linked this to UNC1069, a DPRK-nexus group Mandiant has tracked since 2018. Why social engineer one rich person when you can compromise one maintainer and reach millions of machines?
This is the threat model now. If you maintain popular packages, act accordingly. If you use open source (and you certainly do), act accordingly.
Full writeup: socket.dev/blog/attackers-hu…
I said it before and I'll say it again, if you are a software developer and have any length of time left in your career, you need to be aware of this. Listen or read, and don't delay.
legacycode.dev/true-north/
1
15
This captures whats going on in our software development industry perfectly. In my opinion. legacycode.dev/true-north/
Bobbi Perreault retweeted
This captures whats going on in our software development industry perfectly. In my opinion. legacycode.dev/true-north/
I can't find continue watching either
Replying to @amazonprimenow
@amazonprimenow @amazon why is prime taking a shit? My continue watching is gone and I can only scroll down 5-6 lines POS APP
2
1
26
One more: ssp.sh/blog/why-are-we-here-…
12
Bobbi Perreault retweeted
Stanford just let an AI pick stocks for 30 years.
First study of its kind in finance history.
The outperformance vs. humans was so extreme, researchers spent 12 months trying to prove themselves wrong.
Here's what happens when you let AI manage your money: 🧵
I just got an email my x account for faxtina is suspended for inauthentic behavior. I thought I was letting people know about a new opensource saas product for spas and salons.
3
89
Elementary information follows: when using an LLM to build your saas product - just validate that the database models are correctly defined before proceeding. You know, no extra non-existent fields and such. Don't ask me how I know.
9
Just finished a major pass auditing AI-generated help docs for my open-source spa & salon SaaS. Now adding "Implementation Roadmaps" to bridge what's written vs what's built 💡 The docs are great! Too bad the software doesn't have all these features. :-) #opensource #AI #SaaS
1
44
github.com/faxt-development/…
Most of the code for our spa/salon SaaS was written by AI—after setting up the Laravel base. Windsurf in planning mode mostly.
It’s an open-source experiment in practical AI-assisted development.
#AIcoding #Laravel #TailwindCSS #OpenSource #DevBuild
37
Faxtina is evolving.
We're building customizable, brand-first appointment & client management for multi-tenant spas/salons.
Laravel + Vite + OSS spirit = 💅
Check out the roadmap, join the mission: faxtina.com
#OpenSource #LaravelSaaS #ViteDev #FaxtinaDev
Spinning up Faxtina—a multitenant SaaS for spas & salons. Laravel + Vite stack, Tailwind for brand harmony, custom site generation per tenant. Open source and purpose-built. 💻🎨 #buildinpublic
22








