I don't think it is killing SaaS. I have definitely had to extend my sales cycle when a potential customer vibe-coded a quick fix for a pain point that might have triggered a sale a few weeks earlier, but eventually the benefit delivered by someone else caring about the software as their entire mission really wins out over a feature here and there.
If you are selling SaaS consider that a vibe-coding customer is validating your feature roadmap with their own time and sweat. It's actually a very positive signal because it demonstrates how badly that product is needed. If they could vibe code a "good enough" version of something to get themselves unstuck for a week, you should be able to iterate on those features and build something even better in short order, except deployed securely and professionally.
Everyone's going to talk about how cool their custom vibe-coded CRM is until they get stuck in a failed migration.
Yeah I have been saying this since the start of vibe coding, Saas companies rely on their sales, who are good enough to sell ther products even in tougher conditions. Software costs for the companies is 100% tax deductible, and they spend a very little on it (Most of times its less than 1% of CapEx). Only reason to optimize this cost is if the Execs of those companies think you can sell the same product.
The other thing is bringing in the knowledge about what other customers in the same field want. For business-focused software this can be a boon, customers often can't really envision the solution to their problem, it's like the Henry Ford attributed "If I had asked people what they wanted, they would have said faster horses"
> Everyone's going to talk about how cool their custom vibe-coded CRM is until they get stuck in a failed migration.
Failed/partial/expensive migrations is the name of the game with SaaS as well. Lock-in is the bottom line.
Migrations become much less scary when you truly own your data and can express it in any format you like. SaaS will keep sticking around, especially those that act like white-hat ransomware.
My friend Dave Taylor (programmer on Doom / Doom 2 / Quake / Abuse) was famous for marathon gaming sessions when he was at id. He told me it almost killed him after a session because he was driving and saw what he thought was a Quake rocket ammo box and he instinctively swerved the car at speed to "pick it up", but it was in fact a concrete pylon securing a guardrail by a drop-off. He narrowly swerved back into the road.
On a lighter note, I played far too much GTA: Vice City on PS2 in college, to the point that when driving in real life I forgot to check my side and back mirrors at stop signs, and instead realized I was squeezing my middle fingers on the steering wheel instead of turning my head to look.
Even closer to the mark—I used to play Carmageddon with some of the engineers at Apple when work was wrapping up for the day. Yeah, you had to come down from that very quickly when you got into your actual car then to begin the commute home.
I attempted to replace my 13 mini's battery today using the iFixit kit. I broke the OLED panel doing so. Removing the screen take much more force than I though.
I did this hopping to keep my iPhone maybe 2 more years. Now I am waiting for ordering the 17 next Friday. I will have to manage having half of my screen being white until then...
> Removing the screen take much more force than I though.
Sorry, how is applying less force more dangerous?
(in general, wish the force meters would be widespread so that iFixit kit just had a monitor with a number and a beeper once you reach the needed force level)
This seems like a cool company and I don't want to nitpick too much, but gamers have no respect for history:
Castlevania... [so] called because it is a Metroidvania game set in a Castle.
Ouch - this is precisely backwards. Metroidvanias are named after Metroid and Castlevania because those series practically defined the genre.
Also a bit frustrating because the first Castlevania itself isn't actually a metroidvania, it's a more conventional action-platformer. Castlevania II has non-linear exploration, lots of items to collect, and puzzle-solving, all like Metroid. So it's not too surprising Antithesis had to do a lot of work for adapting their system to Metroid - but I wonder if this work means it now can handle Castlevania II without much extra development.
Yeah the company sounds interesting. I wish the main page had clearer info about what it does. There’s a lot of text but I want the simple, “here’s the little bit of example code to get going.”
I assume they are intentionally not very vocal, probably still maturing/scaling their platform. Until recently they were a stealth startup. The stuff they are doing is truly revolutionary.
If you are a California resident you can request a deletion via the state's new DROP platform which is launching next year. That will send the deletion request to every registered data broker in the state who will then have 45 days to comply. Part of that compliance is sending deletion notifications to everyone downstream that they have shared or sold your data to in the past. The penalty for not responding to a DROP request is going to be $200 a day, per request.
Starting in 2028 CA registered data brokers will have to undergo audits to ensure that they have been complying with deletion requests to the fullest extent of the law. Now, maybe only 20% of actual data brokers are registered in California like they are supposed to be, but it's a start.
Shameless plug: I'm building a platform to help the data brokers actually delete the data they are supposed to, provide full auditing and accounting for that process, and automate privacy request handling: forgetmenaut.com
One of my favorite interviews (Mixrank) was where the CTO/founder and I picked a random problem on Project Euler and we both coded on it in parallel. I was in the driver's seat as far as design and general approach was concerned but we were each coding an independent solution. We weren't even using the same languages.
Once we both had the correct answer, we started optimizing to try and eclipse each others' runtime. This was actually a fantastic test to display deeper knowledge beyond just regurgitating a solution, showing benefits and drawbacks of different languages and patterns, and seeing how we could work while agreeing or disagreeing on a technical subject.
I was really too junior for the role they wanted and I didn't get the job, but it was a fantastic experience.
I can absolutely relate since I'm doing the same right now. I had a good meeting with another founder last week, and the thing I was most excited about wasn't the potential integration between our platforms but just that he was willing to invite me to a group call of other early founders to get support and ideas. This is emotionally more difficult than any previous building phase I've had.
If you are selling SaaS consider that a vibe-coding customer is validating your feature roadmap with their own time and sweat. It's actually a very positive signal because it demonstrates how badly that product is needed. If they could vibe code a "good enough" version of something to get themselves unstuck for a week, you should be able to iterate on those features and build something even better in short order, except deployed securely and professionally.
Everyone's going to talk about how cool their custom vibe-coded CRM is until they get stuck in a failed migration.
reply