Today’s the day! My husband’s children’s book is published and available for purchase! Thank you to everyone who supported us and we hope you enjoy! store.labradillo.com

the "SaaS is dead" crowd is actually "my indie hacker SaaS for other indie hackers is dead" crowd. this should be plainly obvious to anyone who's users aren't terminally online X users. SaaS is in a boom right now. you only need to speak to the average person, let alone an actual user - to know 99% are not building "personal software".

literal hardest role to hire for rn and every ai startup wants someone > chronically online (knows trends) > has taste & can create (new media) > understands ai & technical > can execute with quality (operator) such a small niche of folks who can do this

*deep breath* people think I'm joking when I tell them that to develop taste for software they need to have brunch with their friends, watch old movies and find old records, walk around metropolitan cities and observe how the building styles lend to the personality of the people around them, but I'm so fkin dead serious. where else is this mythical "taste" going to come from? what are you doing to parse the human condition? mf you can barely decide what discomfort you're subjecting yourself to in finding out what you like/dislike, and I'm supposed to trust you to make decisions for millions of people? go do some pottery and come back to me and describe the joy you felt without faffing about curves or whatever, I need you to feel the clay under your fingernails and fall in love with mud. even steve had the decency to drop acid on a sweaty beach in goa to find himself, the least you can do is listen to your friends talk about their lives over a meal without getting distracted by your phone. *exhale*

I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.

OpenAI and Anthropic oversold AI security breaches to pressure feds into protecting turf: insiders trib.al/Jo6xMk5

I'm very sensitive to this feeling, cause I've been there. Someone does something cool, gets a lot of attention, and you're frustrated cause you already did it, a while ago. It's not enough to do things, you must also tell people. Maybe it's not fair, but it's true

We did it again. Temporal just raised a $550M Series E round at a $12.55B valuation. Learn more about how we got here: temporal.io/blog/temporal-ra…

Hey ████, I think there is room for both. 1. Prototypes and other throw-away code can be treated as totally black box. If you’re going to throw it away anyway, and if the blast radius of it breaking is low, it doesn’t need to be perfect. 2. Production code written by Claude should have a higher bar than if it was written by a human. At Anthropic, we have many guardrails in place to make sure this is happening: lots of lint rules, lots of tests, Claude-driven end to end tests, Claude-powered fuzzers running daily, automated code reviews and security reviews, automated code refactoring, and so on. Without these, you can end up with a mess that is hard to maintain down the line. Luckily, the model makes it increasingly easy to do these well — run a few daily routines, use Claude Code Review, etc. Your job is to hold the bar on code quality. If Claude’s code doesn’t meet the bar, try: - Using the latest frontier model (Opus 5 or Fable 5.1) - Increase effort to high or xhigh - Invest in your CLAUDE.md and skills to succinctly teach Claude how to work in your codebase If all else fails, steer Claude more when you work with it, or have Claude fix accumulated debt and rewrite your codebase to make it easier to work with. Or, wait for the next model. Best, Boris