Ben

@knowRowan @neerajjj6785 *UUID7 has entered the chat*

@neerajjj6785 Honestly, UUIDs kill index performance in databases. Auto increment is simpler for joins and caching, especially at massive scale. 💀

Interviewer : If UUIDs are globally unique... why do some large-scale systems still prefer auto-incrementing IDs for their primary keys?

The girlfriend loved Foundation and Expanse but never saw Joss Whedon's "Firefly". I only watched the series once, so... we're on episode 5 now and I'm like "whoah, the kid they got to play young Simon Tam looks a lot like Zac Efron!" And it was. 😮

@steipete In my days as a PM, I have no idea how my engineers got any real work done in cubicles or open office plans. Bravo to anyone who can build software in those environments, I think they're awful and I could never do it.

I feel the same about shared office spaces.

@vuetifyjs @discord_support Any chance you can prioritize getting the Vuetify 10+ year old Discord channel restored after it was hijacked? The real owners are trying to get in touch with you. Help pls <3

48 hours since we were the target of a cyber attack that hijacked our Discord server. 48 hours we've tried to contact anyone we could to say "please shut down our server, we're being hacked", but instead am told we have to submit a ticket from the hacked account. 10 years a paying customer, thousands of dollars in subscriptions lost, an unlimited amount of history completely gone, and the attacker is STILL roaming freely on the server. What an absolute joke @discord.

@AishwaryaDevv The logic and architecture needs to be *yours*. As soon as it isn't, you've lost the plot and you need to stop building immediately - you owe it to your users as they're at a massive security risk right now using software you are considering "disposable".

Am I the only one getting vibe coding fatigue? Building landing pages in 30 seconds was fun, but maintaining a complex codebase where half the logic was “vibed” into existence is an absolute headache. Feels like we traded 1 hour of typing for 5 hours of architectural debugging later. I’ve started manually writing core logic again so I actually know where the technical debt is hiding. Is anyone successfully managing large production projects with AI agents, or are we all just building disposable software?

@CodeWithAmann If you are interested in solving problems with software, there has never been a better time to know how to code.

Be honest devs, Is coding still worth learning in the AI era?

@rxhit05 Hyper-focus on them, drop your price, waste time performing deep competitive analysis projects, so you can then both race to the bottom and tank your market *together* !

Your biggest SaaS competitor just dropped their price. What's your move? -match the price -double down on quality -find a niche -ignore it

@RazorpayCare @Razorpay Still getting private banking information from one of *your* customers emailed to me on a daily basis. Any recommendations on what I should do next for the sake of your own customers? Contact industry regulators to notify them about your lack of security? This is wild.

Hi there, we’re here to help you with your concern. Please share your registered contact number and email address via DM so we can review the details and assist you further. Once we have this information, our team will connect with you and guide you accordingly. Regards, Team Razorpay x.com/messages/compo…

@Razorpay I'm getting daily e-mail notifications from your platform that include *private banking information* for one of your customers. Your support team has been notified and is incapable of assisting. Please DM me, I need this to stop (and so does your customer!).

@kapilansh_twt I have production apps going back 10 years using all of the above except PlanetScale. For the platform I am building now, I decided to build a service layer that will support either PostgreSQL *or* MongoDB, either globally or at the collection/table level 🤘

which database are you using for your product - Supabase - PostgreSQL - Firebase - MongoDB - PlanetScale - something else

Me: Claude, why did you do this? Claude: Honestly, the sub-agent invented it. tbh, I need moments like this in my daily grind - love you Claude Code ❤️ @AnthropicAI @claudeai

@voidzerodev Can't wait for the Nuxt update with it!

🚀Rolldown 1.0 is here!🚀 Rust-based high-performance JavaScript bundler. 🏎️ Runs at native speed that’s 10~30x faster than Rollup 🤝 Compatible with existing Rollup & Vite plugins ⚡The underlying bunder for Vite 8 After 2 years, Rolldown is officially stable and has 20+M weekly downloads. Companies like Framer & PLAID are already using Rolldown in production. Thank you to every contributor, user, and team that helped us get here.

@eshanbuilds @levie The IAAS providers give you a substrate with consumption-based pricing - the "result" you create is NONE of their business. "Outcome-based" price for AI is just SaaS vendors flailing - like you said, impossible to meter. Per-user/agent base price + consumption pricing is the way.

the most honest line here is "one customer could do all their work in 1 agent, another might split it into 1,000 agents, so pricing like a human seat is nearly impossible." that single sentence describes why every SaaS pricing model built on per-seat economics is structurally broken for agents and nobody has a clean replacement yet. the deeper problem is that agents don't use software the way humans do. a human opens box, browses files, edits a document. an agent makes 400 API calls in 3 seconds and never renders a UI. the value delivered per API call is tiny. the volume is enormous. consumption pricing captures the volume but not the value. outcome pricing captures the value but is impossible to meter. every platform is going to spend the next 3 years oscillating between these two models until someone figures out how to price a result instead of a request.

As agents become the biggest users of software, then all software has to be available in a headless fashion. Agents won’t be using your UI, they’ll be talking to your APIs. So the question becomes what is the business model of software and this headless approach in the future? Here are a few thoughts on how everything plays out based on what we’re seeing and doing at Box, but also conversation with other platforms. 1) Seats don’t go away for *people*. Seats are still a convenient and efficient way to have a customer use technology predictably for a set of users within a baseline set of usage. The key, though, is that when the customer pays for a seat, it has to come with a set of usage of APIs on behalf of that user that the agent can use on their behalf. The user will need to be able to interact with their data and the underlying tool via any agent they work with, and an embedded amount of usage will come with the seat. I would imagine most software -Box included- will enable seats to work with their data at a relatively high volume via systems like ChatGPT, Codex, Claude, Gemini, Cursor, Copilot, Perplexity, Factory, Cogniton, et al. quite seamlessly. If you don’t do this, you’re DOA. 2) Agents may have “seats” if they are doing stateful work in the system, but they will be priced very differently than people. Seats (or the equivalent) can make sense when you have an agent that has its own workspace, stores its own data, needs a different set of permissions compared to the user, and so on. If a company wants this agent to be around for long period of time, that may very well look like another “user” in the system. Openclaw-style agents highlight what this future could look like. The only issue on pricing here is that one customer could decide to do all their work in 1 agent, and another might split it into 1,000 agents. So pricing like a human seat is nearly impossible and impractical; each company will have a different approach for this as it gets tricky perfectly trying to capture all the value within an agent seat. 3) The dominant pricing for headless use that goes above the seat allotment, or when an agent is firmly acting on their own, will be a consumption model. Many enterprises software platforms have previously operated like this with PaaS options, and agents will look like another machine user of their system. In some cases the APIs might get priced just as they did previously, but in other cases there may need to be new types of APIs that represent the work an agent would do in one go -more akin to an outcome- instead of a series of API calls. This is especially germane when the headless software also has an agentic use-case embedded within in, such as orchestrating the process within their own system via AI. Overall the growth of this usage pattern is effectively unbounded as the use-cases for agents operating on data in these systems will dramatically exceed what people do with their data and tools today. Every platform that goes headless (which will be anyone that wants to take advantage of agents) will need to adopt a model like this. Some may fight it initially but it’s an inevitably as there will always be more and more agents outside your platform than people. Overall, there’s a lot of really interesting changes left to come in software due to headless use of these systems. Early days.

@James_paul_dev Have 2-4 in live apps today. I just moved my own custom auth for the current product I am building over to better-auth. Building an IT platform and auth is too central to leave to an external third party, but I was going to sink too much time continuing to build myself.

Best auth solution for startups? 1) Clerk 2) Firebase Auth 3) Supabase 4) Custom auth

@alexwtlf Things are rough in the b2c and widget-style small business/solo dev-oriented b2b app game. Thankful for the world of mid-market/enterprise b2b I'm in here, where valuable products are not cloned overnight, the market is spending more than ever, and organic growth trumps all.

Founders, why are you still building? There’s no moat anymore. How are you gonna hit $1K MRR today when AI can clone your SaaS in seconds?

@Gitmo99 This is 1000% fake news. Why is this engagement bait AI garbage even still online on this platform? 🤮

Crazy women wants to sue girl for 1.4 million after she fights back against her son who tried to mug her. MMA fighter wasn't allowing some street punk to grab her pocketbook. You need to be a better mother and maybe your son won't steal. 🇺🇸🇺🇸🇺🇸 #HIAW

@faizan10114 @weswinder Who is gonna tell them that Rocket Chat has existed for *years* 😂

@weswinder there are literally 4 startups that got into YC because they were vibe-coded alternatives to slack.

everybody saying saas is finished because of ai but i still haven’t seen a vibe coded salesforce or slack people out here running 100 claude codes in parallel and yet… literally not a single big saas has been replaced by ai code lol

@weswinder And they won’t be, because only the folks who aren’t actually familiar with how businesses choose and procure the products they use think it’s about the code. AI has somehow created armies of people cosplaying as CxO decision makers on social media and it’s wild 😂

@nateliason One line of code. One line of flawed logic in your code is all that is necessary to ruthlessly hack your app. If you are making a local sandboxed POC, do what you want. If you intend on having actual users for anything beyond a toy application, you should delete this tweet 😧

“If you don’t review AI code it just makes a mess of slop.” No, your desire to keep your code human-friendly is creating an unnecessary bottleneck. Stop looking at the code. Let the AIs handle it.

@MacroEscobar @SimonHoiberg @forgebitz If you are building a low-value/low-risk/toy application, you may not have much to lose. If you are building something substantial and the security integrity of your app is important - you review everything and AI is still useful as an accelerator.

claude just wiped my entire database the whole "i don't care about the code" isn't really valid when the stakes are high (this is just a local dev database)