As always my app ideas comes from: "I can not find an app that does this very simple thing! :( " Let's start coding!

We used to go to a special website, ask strangers for help with programming, and get humiliated in return

"We used to review every line of code before it went into production"

I'll be speaking at #GraphQLConf on May 20 about how Airbnb solved GraphQL Data Mocking at Scale With LLMs. If you'll be at the conference, would love to connect! graphql.org/conf/2026/schedu… #graphql #ai

After months of work, my new app is finally available to preorder on the Mac App Store. It's called Kickstart, and it has just one job: to help indie app developers make more money on the App Store. How does it do that? Let me explain…

Claude Code doesn't show you how many tokens you're using for subscriptions. No breakdown by model. No breakdown by project. Just a progress bar that says "63% used." So I built a local dashboard that reads the files Claude Code already writes to your machine. Turns out every session, every turn, every token is logged to ~/.claude/projects/ in JSONL files. Input tokens, output tokens, cache reads, cache creation, model name, timestamp. It's all there. You just can't see it. My numbers over the last 30 days: 440 sessions. 18,000 turns. $1,588 in API-equivalent costs. On one day, the cache spiked to 700M tokens - visible cache bug, two days in a row. The dashboard scans those local files, builds a SQLite database, and serves charts on localhost:8080. Filter by model (Opus, Sonnet, Haiku). Filter by time range (7d, 30d, 90d, all time). Cost estimates based on current Anthropic API pricing. Works retroactively. First run processes your entire Claude Code history. Install: git clone github.com/phuryn/claude-usa… cd claude-usage python3 cli.py dashboard Windows: use python instead of python3. Zero dependencies. Python standard library only. Open source, MIT. Star it. Fork it. Make it your own.

"Using coding agents well is taking every inch of my 25 years of experience as a software engineer, and it is mentally exhausting. I can fire up four agents in parallel and have them work on four different problems, and by 11am I am wiped out for the day. There is a limit on human cognition. Even if you're not reviewing everything they're doing, how much you can hold in your head at one time. There's a sort of personal skill that we have to learn, which is finding our new limits. What is a responsible way for us to not burn out, and for us to use the time that we have?" @simonw

my entire feed is just

Okay, fine, I'll do one Here is a native macOS AppKit app using TextKit exclusion paths (not pretext) to exclude Chika, while she dances over some rich text. It's fully editable, and she will happily dance over any new text you write

🚨This is so much worse than you think. > Amazon laid off 30,000 engineers. Then told the ones who survived that their bonuses depend on how much they use AI to write code. So engineers started using AI to push changes faster, because their paycheck literally depends on it. > And then the site went down. Multiple times. Amazon's own shopping app broke because AI-generated code got pushed to production. > So what did management do? Did they take responsibility for forcing engineers to use AI they weren't ready for? Did they admit they created the problem? No. They called a mandatory meeting and blamed the engineers. > AI is powerful enough to replace engineers, we've been saying that all day. But it's not powerful enough to replace quality control AND common sense all at once. Amazon proved that executives who don't understand AI are more dangerous than the AI itself. And every company rushing to do the same thing is watching this and learning absolutely nothing.

🔴This is nuts! 🤯 Grammarly now lets you get an "Expert Review" of your text. Based on the topic, it assigns experts to review it with you. Apparently I'm one of those experts in the tech category, along with many colleagues among hundreds of authors, including some who are dead! WTF… Here you can see a Grammarly clone of me reviewing my own text for my upcoming book. In case you're wondering, no one gave them any permission. I've found @slightlylate, @addyosmani, @rachelandrew, @gradualclearing, @jaffathecake, @brucel, @Paul_Kinlan among others

Just dusted off my 5-year-old project -- rules_applecross now works with Bazel 9, bzlmod and latest of everything. Here's a pipeline of it building a SwiftUI app from Linux github.com/apple-cross-toolc…

hummourAdvancedProgrammingThisIs redd.it/1ri7uxu

Dijkstra predicted in 1978 how people would feel about #Swift Strict Concurrency checking in 2025.

Had to update my local development workflow a bit since AI agents can do a lot more in parallel now. Decided on a lightweight git worktree wrapper, with simple tmux window management. Wrote about it some more here: scottberrevoets.com/2026/02/…

We’re going to show you some amazing things Swift is capable of! 😁

“Add an image for each row and watch it die” Every row loads an image from the network. In memory cache, no file cache. URL is random every time (uuid) so cache should always be a miss.

I’m giving a talk titled “Designing APIs for Swift Concurrency” this Thursday at the @sentry HQ in SF! Join for food, cool people, and an exploration of writing correct, ergonomic code in a poorly understood area of Swift. Here’s the link to sign up: luma.com/tqb3l8w6

Claude/Codex is in the middle of a medium size refactor in a monolithic app when the “10% context remaining” comes up. What do you do? Keep going? Compact context soon? Start over with a narrower scope? Wrap it up and start over with a new prompt that summarizes progress so far?