Luv Kapur

Share a bit. I don’t want to belittle the category of software. People did amazing work in the world of payroll software (agile manifest etc). But at some point a csv is created and it has a row per payee and it happens twice a week. Shopify pays out millions of businesses and moves billions a day. And we took 20m of financing ever before we went public (and had it all still in the bank when we did). The scale of nonsense that’s happening with government bespoke software is just unexplainable without fraudulent intent. But it also tracks with everything else you hear about government efficiency (minus maybe military). It’s not that it costs 10b to make a payroll software that is the problem. It’s that it costs this much for anything that the government tries to do itself. The only conclusion is that the government needs to do a lot less.

slop creep is what happens when you turn your brain off and hand the thinking to coding agents each individual change is fine, but all together, you have a pile of crap we're witnessing this happen in real-time across everything boristane.com/blog/slop-cree…

I've been saying for a while that we are collectively figuring out how elastic the market for software is. Turns out: very elastic. If making software is cheaper, we make more software

everyone's talking about their teams like they were at the peak of efficiency and bottlenecked by ability to produce code here's what things actually look like - your org rarely has good ideas. ideas being expensive to implement was actually helping - majority of workers have no reason to be super motivated, they want to do their 9-5 and get back to their life - they're not using AI to be 10x more effective they're using it to churn out their tasks with less energy spend - the 2 people on your team that actually tried are now flattened by the slop code everyone is producing, they will quit soon - even when you produce work faster you're still bottlenecked by bureaucracy and the dozen other realities of shipping something real - your CFO is like what do you mean each engineer now costs $2000 extra per month in LLM bills

@ThePrimeagen creating a thing isn’t hard. maintaining is.

On 1 Dec 2020, AWS S3 announced that all writes to S3 are now strongly consistent (not eventually consistent, like before) *at no price change or latency changes* to any customers. Pulling this off was probably one of the biggest invisible engineering achievements of the decade

A few things I've noticed as all devs write code with AI. When you write foundational / architectural code of a new project by hand, you "feel" the code pushing back if your abstraction isn't right. You feel when something is harder than it should be. The code is telling you it's not in the right shape. Good engineers are sensitive to this. When you're using an LLM, you keep pushing right through this in a way that feels like you're making progress, and it may even be directionally correct in a sense, but the underlying foundation of it all is actually bad in a way that either kills progress of the LLM later as it buckles under the complexity it has created or destroys your ability to maintain the code long term. Related to this, I see a general restlessness with just sitting and thinking about a problem for a while. As I've been working on a new library here at Laravel, there have been days where it feels like I mainly just stare at my screen thinking about something. When Claude Code is at your fingertips, it's tempting to just start yapping into the terminal and watching code come out the other end. Again, directionally correct in some ways, but often doesn't land on the elegant solution that is waiting to be discovered.

As an example of how we are building on top of Gemini 3, AI Mode in Search now uses Gemini 3 to enable new generative UI experiences, all generated completely on the fly based on your query. Here’s how you might use this to learn a complex topic like how RNA polymerase works.

Hello Thermo World.

> be me, Elon "GPU golem" Musk > "we're gonna build a 1 M sqft GPU temple in 6 months, get the warehouse keys" > entire OpenAI campus still arguing over lunch menu, I already poured 40k yards of concrete > power? lol just buy a dead Duke Energy plant in Mississippi > regulators let me spin turbines without a permit > Tennessee eco-twitter: "no gas turbines in Memphis" > move 100 ft south "what turbines?" > rent 600 MW of Solaris turbines, literally Airbnb for gas > NYSE shows xAI = 67 % of Solaris order book, stock ticker changes to "$ELON_NEED_POWER" > Oracle still waiting for concrete to cure, I already have 119 chillers humming at 200 MW > Colossus 1: 200k H100s, built in 122 days > Colossus 2: "hold my Megapack" > run 1.1 GW across state lines on Tesla batteries lined up like Duracell bunnies on meth, OSHA having stroke > goal: 1.5 GW so I can train a model that writes OpenAI's bankruptcy filing in perfect limerick > entire grid rides on rental generators, basically LAN-party logistics at nation scale > still call it “sustainable” because PR runs on different power > Sam Altman tweets "compute is our moat" while I literally dig a moat of gas turbines around him > Meta still drawing blueprints, I’m out here playing Factorio IRL > Anthropic typing safety essays while my turbines outrun their ethics board > mfw the only thing greener than my energy is their envy.exe

@elonmusk @xai @elonmusk @xai pls consider using @bitcloud_ for the simulation. It has all the infrastructure you need for the job bit.cloud

Terence Tao on the supposed Gold from OpenAI at IMO

Joseph Campbell, what a passage

The Singularity Era: A Tremendous Opportunity or an Existential Threat? And How Do We Stay in Control? What is Singularity? Singularity is a point in time when the speed of technological progress becomes exponential. Imagine the last hundred years, in which we saw greater technological advancement than in the two thousand years preceding them. After reaching the point of singularity, such progress could take only one minute, or even less. So, is it good? Yes, the positive implication of the singularity is the potential solution to all the world's problems within our lifetime. This could include solutions to incurable diseases, welfare, and communication on scales we have not yet known. What could possibly go wrong? Gradual loss of control to AI, to the point of us becoming a secondary factor in our own world. But while the discussion about this is broad, I believe that the most immediate and concrete danger is in the way we adopt AI for software development. Uncontrolled use of AI tools can turn our code into a "black box": complicated, duplicated systems that none of us truly understand anymore, are unable to maintain. The moment we lose the ability to understand and change the software ourselves, and fully depend the AI to "fix" it – we have effectively lost control and placed our fate in the hands of AI. So, what to do? The way to maintain control is to ensure that we understand, control, and can change our software and code over time. No less important, the world will be divided into those who derive value from technology and thrive and those who will be stuck and left behind. In the last 10 years, my friends from the Bit team and I have been busy developing solutions to these problems. We actually started as an artificial intelligence for building software, and after we saw the problems that the technology creates, we decided to dedicate the time and development to build an infrastructure for software composition, which is known as "Bit." How does it help? Bit is an open source project for helping developers build software by composing components and assembling them into applications. Building software with composable components allows us to derive value from artificial intelligence while ensuring control over the software over time. Understanding and effectively managing the software will prevent handing control over to artificial intelligence.

The reality of building web apps in 2025 is that it's a bit like assembling IKEA furniture. There's no "full-stack" product with batteries included, you have to piece together and configure many individual services: - frontend / backend (e.g. React, Next.js, APIs) - hosting (cdn, https, domains, autoscaling) - database - authentication (custom, social logins) - blob storage (file uploads, urls, cdn-backed) - email - payments - background jobs - analytics - monitoring - dev tools (CI/CD, staging) - secrets - ... I'm relatively new to modern web dev and find the above a bit overwhelming, e.g. I'm embarrassed to share it took me ~3 hours the other day to create and configure a supabase with a vercel app and resolve a few errors. The second you stray just slightly from the "getting started" tutorial in the docs you're suddenly in the wilderness. It's not even code, it's... configurations, plumbing, orchestration, workflows, best practices. A lot of glory will go to whoever figures out how to make it accessible and "just work" out of the box, for both humans and, increasingly and especially, AIs.

A first glimpse at how AI is going to architect and build full-blown composable applications for you. Frontend, backend, features and everything else. Enterprise-quality code with tests and docs, made of 100% reusable components.

bit.dev/blog/meet-harm… At @bitdev_ , we’ve always been committed to composability. But we’ve also seen firsthand how challenging it can be to truly connect decentralized systems into a cohesive whole. It’s a problem that impacts application performance, developer productivity, and ultimately, the end-user experience. This is why we are so excited to announce "Harmony". It connects decentralized architectures into unified, cohesive platforms. It transforms what was once an extremely complex undertaking into something as straightforward as building a simple React app. Harmony is the foundation of Bit and the Bit Cloud platform. Refined with over a decade of composable architecture experience and forged through real-world customer implementations, Harmony offers a complete, comprehensive and battle-tested solution. Learn more about Harmony in the blog post below 👇 #composability #opensource #softwarearchitecture #harmony #developer #API #microservices #innovation #platformengineering #devexperience #webdev #microfrontends #platforms #backend #frontend

Shifting from decentralized to composable architecture -------------------------------------------------------- bit.dev/blog/telling-t… Decentralized architecture has undoubtedly revolutionized software development, driving remarkable progress and scalability. However, it also brought new challenges that slow down future growth and advancement. In @bitdev_ , using composability, we shifted from stagnation driven by architectural complexity to exponential progress. We now compose over 300 independent business features into a unified platform, surpassing previous limitations on application performance, operations, and development autonomy. Read more about our journey in the blog post below 👇 To the amazing Bit team: Thank you! 💜 The past decade has been an incredible journey, and your dedication, persistence, and belief have been the driving force behind our unbelievable progress. I'm grateful for each and every one of you. @ShohamGilad @itaymendel @jonnysas @Erez_Ben_David @Gideon_Mantel @zkochan @zhaojinjiang @JoshKuttler @luv_kapur @DavidFirst2 @OCombe #composability #composable #distributed #react #angular #vue #nodejs #microfrontends #microservices #dev #design #architecture #monorepo #multirepo #mach #digitaltransformation #devex

Complexity is always a cover for fraud. In every domain.