Building https://xitter.cf/t.co/e0pGdhL5S3 SF · Blr

San Francisco
Joined April 2008
My AI Engineer World fair talk drops soon youtube.com/watch?v=Bck7ABCZ…
10
1,201
Thiyagarajan Maruthavanan (Rajan) retweeted
AI wrote the code. So who owns the software? Not a trick question. It’s one most teams haven’t answered yet, and it’s coming for all of us. In the latest episode of AI Factory Show, @mtrajan and I dig into the uncomfortable questions every developer and engineering leader is facing right now: - If AI writes 90% of your code, is it still your software? - Can you trust AI to review its own code? - What’s the one part of the job AI still can’t take from developers? - How should teams adapt their workflow without sacrificing quality? Our take: AI can write the code, but intent, judgment, and responsibility still belong to humans. The developers who win won’t be the fastest typists. They’ll be the clearest thinkers. Watch the full conversation here: youtu.be/modGT6MGITE So where do you stand? If AI writes the code, who should own it: the developer, the company, or the AI vendor?
1
52
Thiyagarajan Maruthavanan (Rajan) retweeted
San Francisco knew what a Software Factory was. The rest of the world needed @OpenAI to explain it. 😂 When we spoke about Software Factories in SF, nobody asked what OpenFactoryAI was or what a deploy company does. They went straight to: “How can I use this?” Then came the Security incidents and OpenAI's Defense Factory blueprint. Suddenly, people elsewhere started saying, “Ah, NOW we understand what you mean by a Factory!” Funny how an idea becomes obvious once a big name talks about it. What's fascinating is how uneven technology adoption is, even across major US cities. But here's the bigger plot twist. We've decided that OpenFactory will support all our competitors. Yes, ALL of them. We'll help implement any Software Factory. Sounds crazy? Not really. Software is no longer the moat. Engineering outcomes are. And if your competitive advantage is just the factory you built, you might be competing on the wrong thing. OpenFactoryAI. - Get it touch with us for all things about Software Factories. @humanlayer_dev @cognition @FactoryAI
1
2
112
You need a security factory to deal with challenges like Black October and first step is to build your own software factory
Just spent the last 7 days on the front lines of the vulnpocalypse fending off an active cyber attack on one of our products. Some thoughts: - Software factories are going to be required equipment for everyone. There’s just no way to keep up with the pace of highly automated adversaries without one. - We were lucky because we had spent the last few months getting our software factory running well. It is nice to have for product development but proved to be absolutely essential this week. - At the minimum you need to have a coding server in the cloud pre-provisioned with read only access to all your logs and all the services you depend on for observability. With that in place you are a prompt away from reasonably good situational awareness, ongoing monitoring with loops, and ability for coding agents to validate fixes against your actual, observed attack patterns. - Shared coding server also unlocks multiplayer incident response where everyone can see every session and jump in as needed. Sharing session links that can be forked is much higher bandwidth than re-explaining things. - You don’t need to be Ramp/Stripe/Uber scale to have a working software factory in the cloud. We are a team of 3. Ours is built with an @opencode server (thanks @thdxr!), a forked version of compound engineering optimized for automated workflows (thanks @kieranklaassen!) and a multiplayer agent in slack that handles crons (we have our own harness but pick your favorite here). - To get our software factory up and running well, we had to stop all new product development for ~6 weeks and just focus on getting the validation systems working that enabled us to reliably shipping PR without human code review. This felt very painful in the moment but was totally worth the eventual speedup in velocity. - KYC for @AnthropicAI & @OpenAI cyber programs is now easy and quick (at least for defensive access), but a day felt like a lifetime this week. Submit your app now before you really need it. - Getting Mythos access unlocked a deeper level of analysis that helped us shift from reactive mitigation to proactive patching. Wish we had done this a few weeks earlier. Get started now!
1
2
307
Thiyagarajan Maruthavanan (Rajan) retweeted
Because your team is ignorant of a 101 principle taught in every mechanical engineering and industrial engineering course
If AI makes you 10x faster at coding, why is your team not shipping 10x faster? Amdahl's law has the answer... The law says the overall speedup is capped by the part you did not speed up. With `p` as the fraction of the work you accelerate and `s` as the speedup on that fraction, speedup is computed as attached. Now plug in some numbers. Say writing code is 30% of the time from idea to production, and AI makes that part 10x faster. The overall speedup is 1 / (0.7 + 0.03), which is about 1.37x. Even if coding is half of the cycle, you get about 1.8x. These numbers are illustrative, so use your own, but the shape stays the same. The rest of the cycle is still there: - Figuring out what to build - Aligning product, design, and other teams. - Code reviews, which are now more than ever - CI and CD takes the same wall time as before. - Debugging and incidents, where code that nobody on the team wrote line by line takes longer to understand. In fact, it can get worse than Amdahl predicts. Faster code generation increases the load on every stage after it, so the review queue grows and the bottleneck shifts. A team that writes 10x more code with the same review capacity is just building a bigger queue, unfortunately So if you want the team to actually ship faster, measure the whole path from idea to production and find where work waits. Then apply AI there too: review, test generation, flaky test triage, deploy safety checks. Otherwise, you have optimized the part of the system that was never the constraint. Speeding up the typing was always the easy part :)
6
9
1
148
16,513
Onwards and upwards, @prashgarapati
Thrilled and grateful to announce our investment in @warpsciences. Warp is bringing AI and robotics into the labs, improving the very infrastructure that drug discovery runs on. Discovering new medicines gets faster and cheaper, and more of them reach the people who need them. I can't think of a better team to solve this problem. Thank you, @kevinweil, @dpatil, @manohar_paluri, and Solomon Reisberg, for giving @neon_fund the opportunity to be part of your rocketship!
1
358
Thiyagarajan Maruthavanan (Rajan) retweeted
What a crazy 24 hours for security and IT teams across the world. Human bandwidth cannot remain our last line of defense. There will be next eMudhra, PHP, LiteLLM, Node/NextJS/React, TiDB Cloud and PingCAP. We need AI Workforce for Enterprise IT and Security.
6
8
2
67
2,759
Thiyagarajan Maruthavanan (Rajan) retweeted
One may wonder why @OpenAI is investing in Bio and releated industries. AI is good at many things but sucks and synthesis the models are far far away from the capapability today. The access to process, data and metholdogy will create new unlocks in the direction.
We’ve acquired Orchestra Bio, a platform that helps biopharma teams coordinate the complex process of drug development. Together, we’ll build on Rosalind, our AI models and tools for life sciences research, to streamline those operations and help new treatments reach patients sooner. Welcome @ashokaraj_ and team! openai.com/index/openai-to-a…
1
64
Banning your competitor doesn't make you more competitive. It just makes you less likely to find out when they've become better than you. That is a dangerous game to win.
The Department of Homeland Security is requiring all civilian federal agencies to remove DeepSeek products and 'any third-party services developed using DeepSeek implementations,' and to stop buying them.
1
382
Thiyagarajan Maruthavanan (Rajan) retweeted
Code just became the cheapest thing in software. So why are we still treating it like the asset? If AI can rewrite your service in an afternoon, the value has moved somewhere else. Most teams haven't figured out where. That question came up on the latest AI Factory Show with [guest names]. It led to a few more that are harder to answer than they look. Where do juniors learn the craft now? Engineers used to learn by writing the boring code, and AI writes that now. If you don't deliberately build that practice back in, your 2030 seniors will never have had the reps. What in your repo is actually worth protecting? When code can be regenerated, the real assets are your specs, your tests, and the reasons behind your decisions. Most teams have plenty of code and very little written down about why. Can you explain your taste? Your senior engineers recognize good design on sight. If they can't put it into words, AI can't learn it, and it walks out the door when they do. Are your bugs moving upstream? AI rarely gets syntax wrong. It does exactly what you asked, so the failures come from what you meant. Is your most valuable engineer the one who deletes code? When writing costs nothing, every extra line is something someone has to understand later. The teams that win won't generate the most code. They'll know what's worth keeping. So be honest: if your code vanished tomorrow, what would your team need to rebuild it? Watch the episode 👉 youtu.be/pMszvr75yr8 @mtrajan
2
2
191
Thiyagarajan Maruthavanan (Rajan) retweeted
For 6 months, I've called myself 'mother of agents' 🐉 Working on this changed how I think about agent squads. Yes, I call them squads now 😛 Can’t say more yet. Early access gets you there first. @mtrajan @BeeKashi
Software factories don't have a textbook yet. So we're writing one. "Build Your Own Software Factory" How to turn AI coding agents into a software delivery system your organization can actually trust. From individual coding agents to coordinated digital squads. We're sharing everything we've learned building our own factory and helping other engineering teams build theirs. Including what worked, what broke, and what surprised us. FREE book. Get early access ↓ form.typeform.com/to/jdOIgvq…
2
4
174
Thiyagarajan Maruthavanan (Rajan) retweeted
Look, folks, running a software factory is mostly herding agents that escape their sandboxes, trash your repo, spin in loops all night, get throttled by the frontier labs right when it matters, and forget everything the moment you hand off context, so we wrote the book on how to survive IT ALL.
Software factories don't have a textbook yet. So we're writing one. "Build Your Own Software Factory" How to turn AI coding agents into a software delivery system your organization can actually trust. From individual coding agents to coordinated digital squads. We're sharing everything we've learned building our own factory and helping other engineering teams build theirs. Including what worked, what broke, and what surprised us. FREE book. Get early access ↓ form.typeform.com/to/jdOIgvq…
1
3
181
Software factories don't have a textbook yet. So we're writing one. "Build Your Own Software Factory" How to turn AI coding agents into a software delivery system your organization can actually trust. From individual coding agents to coordinated digital squads. We're sharing everything we've learned building our own factory and helping other engineering teams build theirs. Including what worked, what broke, and what surprised us. FREE book. Get early access ↓ form.typeform.com/to/jdOIgvq…
3
2
8
792
Thiyagarajan Maruthavanan (Rajan) retweeted
At our AI Lab, @mtrajan and I are we're seeking collaborators, from nonprofits to enterprises, who have real-world workflow data and want to turn it into practical AI solutions. Drop us note or direct DM.
1
2
75
Don't worry too much about moats. If you survive the flood moats will start showing up
When markets are growing quickly, moats don't really matter. It doesn't make sense for leaders to invest in new spaces. And tons of whitespace gets created. When markets slow down, most moats can't save you anyway. Don't worry too much about moats.
2
11
722
Best software factory is your own, every organization will build their own
Blackstone is going all-in on Factory as their platform for autonomous software development. The world's most important enterprises are building software factories and accelerating.
5
294
You can have no gaps in your roadmap and still be heading in the wrong direction. Salesforce’s Listen Labs bet puts it closer to the customer as AI disrupted all software interface. If someone else owns interface and directs the work, ServiceNow risks becoming plumbing, essential until someone finds a cheaper pipe. Denying a Decagon rumor is the easy part.
We are aware of misinformation in the market today about our acquisition strategy. To be clear, @ServiceNow has no interest or intention of purchasing Decagon. Our approach to M&A has not changed: we remain an organic growth company first. M&A is a tool to accelerate our roadmap or open meaningful new markets, not a substitute for innovation. As we have previously noted, we do not see major strategic gaps that require large-scale acquisitions at this time
3
560
Thiyagarajan Maruthavanan (Rajan) retweeted
The Age of Outcomes and Autonomy: 👉 lnkd.in/gkhXvebu → Customers pay for results, not software → Autonomy is measured in hours humans can walk away → Code isn't the moat. Relationships are till Agents start making decisions → Measure success by what changed for a real person / organization → Attention is the new IP @mtrajan and I discuss this more in this episode of Software Factory Debates.
1
1
1
199