Our software factory is pretty killer. Now available for your team too. rollbar.com/factory

Anyone working on a better Slack client, for managing a large number of concurrent threads? I don't mean a Slack alternative. Too hard to move off Slack. Just an easier way to manage 10-20 concurrent threads.

From... > AI will do the work worse, but faster, so we should lower our standards to... > With AI, we can do the work faster *and* better, so we should raise our standards

> Reviewing an implementation plan from Codex > Think of a detail it needs to handle > Write feedback > Read next line of the plan > It already thought of it

Please, Slack, fix this, I can't rest.

AI means I can just do everything and don't have to prioritize anymore, right?

Claude Code Review... very good, and wow, $$$

Hm. So far, codex 5.3 seems worse than 5.2. Seems to lose context faster, and make worse decisions.

California voters love to vote yes for taxes. So the strategy against the wealth tax should be to start a new competing initiative, right? 1. Introduce a tax to treat loans as realizing gains. 2. If it gets more votes than the wealth tax, the wealth tax is void.

Speed is fun.

NVDA at 20x revenue / 30x operating income, at rule of 125, seems cheap.

I'm looking for a way to run multiple codex agents in parallel, where each has its own cloud development environment (not just a worktree). There must be good solutions for this, right?

1 prompt and 10 minutes for Codex to add some tech debt. 5 prompts and 30 minutes to clean it up.

We're excited to release Session Replay in Rollbar! Rollbar Session Replay integrates seamlessly with our Error Monitoring, so you (and your AI) can easily understand, repro and fix frontend bugs. If you haven't used Session Replay in debugging before - you've been missing out. You have to try it. If you have, try Rollbar's because: - you already use Rollbar for error monitoring. It's directly integrated into the UI, SDK, API, MCP, and billing. - you want more control over which replays you record. Rollbar's is the only session replay that gives developers full control over what's recorded and how it's recorded. No more wasted replays on sessions that don't contain the events you care about. - you want to analyze your sessions with AI. Rollbar is the first we could find that provides the actual session recording (not just a list) via the MCP server. Try asking Codex CLI to analyze a replay associated with an error and determine if any user-facing impact occurred.

Easy to forget how important a fast feedback loop is. Just slowly whittled away at an issue with a 3-minute feedback loop. Got nowhere over several hours, thinking a few seconds at a time with long breaks in between. Finally did the work to cut feedback to subsecond. Fixed the issue a few minutes later.