Mike Morton

Source code is nothing more than a collection of files and folders that, when compiled or run, produces some output. But source code does not equal user intent to create. So why are vibe coding products pretending that the two are equal? Source code is an artifact, something easily produced, like a build artifact. Something cacheable and reproducible, unless user intent changes. Raw source code will be like compiled binaries in the near-distant future. Something written for machines to execute, not necessarily for humans to signal intent. A new platform must emerge that treats code as a build artifact, and that platform is socra native (coming soon).

This is HUGE

@sama posted on the wrong account again

Ok, Bun really is all that.

At this point I don’t even know what Pilates is and I’m too afraid to ask

The product in its current form is fundamentally geared toward collaboration between people and agents in a distributed network, so this would not be a primary use case. We’re planning to add offline access for scenarios where you’re on a plane and need to create Socras and use cases like that. Plus, if you’re truly local then you’ll need to be running a non-SoTA model locally as well, which most folks don’t want to go through the trouble of setting up themselves. It’s an interesting use-case though. Reminds me of my hardware days.

@morteymike @edsocra Ok that would be valuable, would Socra be able to run on air-gapped computers or LANs/WANs without internet access?

Semiconductor manufacturing is the most sophisticated, highest volume, and highest precision production process in the world. My career after college started as a photolithography engineer at TI. There, I learned how to build and monitor processes that scale, how to lead teams, and how to drive continuous improvement across cost, scrap, and yield. Now I’m seeing the same revolution happen in software. Building, testing, and deploying software end-to-end at high scale and high precision requires the same rigor. Supply chain optimization, inventory control, yield management, continuous improvement. These lessons from semiconductor fabs apply directly. I’m grateful for my time at TI. That experience shaped how I think about scale, precision, and process control. And it’s exactly what I’m applying now: creating and optimizing the processes my AI workers follow to build better than I could myself.

Think of V2 as a coordination surface for your humans and agents to operate on top of. Agents have their own identities, roles/permissions, and can interface with the platform via API. So, you’ll be able to install or build an agent that can do pretty much anything else a human could do, including report back to you or escalate to you on progress or challenges.

@morteymike @edsocra Yes, I have two edge Agents, they can run on air-gapped laptops or desktops. Could I add Socra as a project manager to let me know, when the customer approves/allows, to tell me what challenges the customer has had?

@edsocra @raulizahi No. The client-side apps will run on a sync engine though, which will enable a much more responsive experience and offline access for some things. Was there a particular use-case you were thinking of?

@raulizahi I'm assuming "yes", but not sure. Asking @morteymike.

Cursor is absolutely shooting themselves in the foot with monthly usage limits, probably bleeding customers to Claude Code like nobody's business.

Here is an xAI story. When I was first hired (low level) by xAI, I was extremely excited. I greatly admired Elon and what Grok could be. I have a pretty cool AI following here on X. Some big names see my stuff, including Elon himself (at the time). Lex, Beff, Andreessen, Aravind, many others. During the interview and onboarding for xAI, they made a *big deal* about wanting people who "take initiative" and think outside the box. Ok... So, some of the biggest names in tech follow me on X. I decided to ask for ideas and feedback on how Grok (then still early at version 2) could be improved. I asked my followers on X for the best "how can we make Grok awesome?" ideas, and was going to collect them (organized by Grok himself) into a big report for my boss(es) and ultimately, Elon. (xAI makes a big deal about how it's a "flat structure" also. You're supposed to be empowered to act on good ideas.) Well, my post got way more attention than I expected - great! Ideas to improve Grok poured in! I built a script to collect and sort all these great ideas to make xAI's core product better. John Carmack (personal friend of Elon, creator of Doom, id software, legend) retweeted it. Carmack has 1M followers. There were so many great ideas on how to improve Grok! I was collecting them and excited. Until....... I woke up the next day to a threatening email from my main supervisor* at xAI, telling me I had messed up, that I was NEVER to ask for ideas to improve Grok ever again, that it wasn't my job (I thought our job was to improve Grok.) They suspended my account on X. They never explained why. It was obviously related to my post about improving Grok. I was told to delete those posts which had gone viral. I had to delete all the hundreds (thousands?) of genuinely good ideas for improving Grok that had poured in by users on X, because it stepped on someone's toes. It made me confused and sad. Incidents like this happened often, where xAI employees would come in full of excitement and enthusiasm, and would have it stomped out by managers who hated ideas. They filled xAI with middle managers and busybodies. It was one of the most DEI and corporate-y places I've ever worked. I came in wanting Elon and xAI to win and left just sad. *That manager is gone, for what it's worth. Everyone I knew at xAI is gone.

@BenjaminDEKR I knew you were saving this banger for the right time @BenjaminDEKR

@boxfan That worked well for MySpace.

I don't want to be on a human + AI network. I want to hang out and shitpost and call my friends gay.

Wrong reaction. Could be using this as a vehicle to propel us to the first human + AI network, instead employs boomer tactics to guarantee staying behind in the new world.

Kevin Spacey’s speech at the Oxford Union Society on December 1, 2025, addressing his situation. Worth watching all the way to the end.

We choose to go to the moon. We choose to go to the moon in this decade and do the other things, not because they are easy, but because they are hard... - J.F.K.

You may not be able to move the world in a day, but you can take a couple steps in the right direction.

Fascinating. Couple thoughts: If we consider "breadth" as number of parallel or similar projects, fork count increasing means increasing breadth of repos. And if we consider "depth" to be the specific, difficult functionality that a project provides (roughly equal to useful LOC), I think this commoditization increases breadth without increasing depth much, since people who would have contributed to a project now fork it. Open source projects therefore lose their "why" as ease of copying increases. E.g. VS Code devs disheartened by a fork of their project gaining more traction. Whenever I think about this type of thing, I always like to extend the trend out 10-20 years to see how the world might be. I think in this case: - open source slowly dies - people monetize forked versions of open source projects and are more successful, much like a gene mutation can lead to advantageous selection - general software quality goes down, as does specialization of software - software slowly becomes a commodity It's hard to imagine what happens to the world when marginal cost of software drives to 0.

@morteymike Yeah. That's a good frame and effectively how it's been happening for me in the past couple months.

The problem with open networks like GitHub is authorization to request work. If anyone can create an issue or PR for your OSS with vibe-coded slop that takes you hours to review, the cognitive load on you far exceeds your ability to progress your project forward. This was barely manageable before AI, but it’s unmaintainable after AI, even to the point where we are seeing popular projects shut down the ability to request features or bugs. Something must change

@davidpwalter That’s true. I think that means fork count per repo will increase greatly - almost like a repo becomes a template that can be modified or altered to suite specific needs at scale.

@morteymike Now people can simply fork it and review and use their own vibe-code.

@vibewithed @BenjaminDEKR That’s a cop-out. We’re already married fam.

@BenjaminDEKR Ben!!! My strongest is that @morteymike is awesome and I’m lucky to have him as husband/best friend/co-founder and do life together.

Raw-dogging Netflix by picking one of the first suggestions without searching Rotten Tomatoes