*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*

Bury your head in the ground at your own risk. I aim to not jump on any hype trains, but since Opus 4.6 and GPT-5.2 + the harnesses it was clear that these things can write code nearly as good as I can in my best language; better in other languages. But we won't see non-devs push production code for a long time; possibly forever, if you ask me. Software still needs to be built in robust ways, and it's our profession to do this well, and use the new tools we have, which create new and interesting (+tough!) challenges

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…

Habitat is OpenAI's online storage platform that powers everything from ChatGPT to Codex. It has grown over 10x year over year. Before the Rust rewrite, its Python service handled more than 20 million requests per second at peak.

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

A message from the family of Dolly Parton.

Introducing OpenShip. An open-source application platform for building, deploying, operating, and scaling applications on infrastructure you own. Replace deployment tools, managed services, and infrastructure workflows with one open-source platform. Available today: - Mail Server (Built in. One click). • Runs on your own VPS • Unlimited domains • Unlimited mailboxes • Modern webmail included • Connect with Gmail, Outlook, Apple Mail, Thunderbird, or any IMAP/SMTP client • Send email directly from your applications using SMTP • No mailbox subscriptions or API fees • High email deliverability - Deployment: • Deploy any stack • Git-based deployments • Zero-downtime deployments • One-click rollbacks • Development, Staging, and Production environments • Multi-branch deployments with isolated environments • Deploy to VPSs, dedicated servers, cloud VMs, or your homelab - Services: Provision the services your applications need in one click. Replace multiple managed providers with services running on your own infrastructure. • Supabase • PostgreSQL • MySQL • MariaDB • MongoDB • Redis • MinIO • Meilisearch • Qdrant • RabbitMQ • Kafka • ClickHouse • Elasticsearch ...and deploy any other service alongside your applications. - Operate: • Live deployment logs • Live request logs • Real-time traffic analytics • Automated backups • Monitoring • Secrets management • Domains • Automatic SSL • Environment variables • Scheduled jobs • Health checks -Multi Environments: • Separate Development, Staging, and Production environments • Deploy every branch independently • Test changes before production • Isolated services, secrets, and configuration per environment - Security & Teams: • Team management • Role-based access control • IP allow/block rules • Rate limiting • Security rules - Developer Experience: • Web dashboard • Native desktop application • CLI • REST API • MCP support for AI agents, just add the mcp and your agent can do the work for you • Manage your infrastructure without living in SSH - Coming Soon: • Multi-server clustering for applications and databases • One-click load balancing • Horizontal scaling across multiple servers • Built-in high availability and failover • Scale from a single VPS to a cluster with the same workflow • Just add servers. OpenShip handles the rest. Open source.