I don't understand why Claude Code doesn't have access to its own weekly usage percentage.
Hey look RAM prices are totally acceptable nowadays.
The contrarian take seem to be a version of "hey, this is kinda cool."
So.. yeah, kinda cool. Won't keep me from not using the touchscreen when I don't need it.
We brought Touch to the Mac!
From the all-new iPad mini to the 14-inch MacBook Pro and iMac... and now MacBook Pro with PROLED XDR Display and Touch, creators have new tools to do their best work yet.
Show more
This turned out to be "expected behavior" (fork of a private repo got cascade-deleted when the original repo got axed), and wasn't communicated clearly.
A reminder of just how important it is to have clear attribution and messaging in your audit trail. People freak out easily.
Show more
someone outside our GitHub org deleted one of our private repos.
no membership or invite or role. nothing in our org or enterprise audit logs gave them access. just one repo.destroy from the gh CLI.
and it's not in deleted repositories, so no restore.
@github how is this possible, what sorcery is this?
Show more
To anyone who believes MCP as a usage vector is dead on arrival, here's an adoption curve from a real product used by real people.
Today, 42% of all
@TallyForms are built with AI.
(Tally AI + MCP)
Getting more and more of that from my customers, directly or indirectly (by asking for feature parity in the API and MCP).
SaaS products of the future MUST present all affordances equally to humans, agents, and machines. UI, MCP, and API have to be fully interchangeable.
Show more
If I have to go to a dashboard to use your product, I'm not going to use your product.
If anything, I'm more likely to tell Claude to rebuild your product.
One is selling intelligence as a commodity, the other is selling commodities as a commodity.
Is this valuation reasonable? Is there room for growth that would make investing in the Stock vs an index make sense?
I feel it might be, but I can’t reason my way there…
Show more
Anthropic valuation: $1.5 trillion
Walmart valuation: $960 Billion
Anthropic revenue: $16.3 billion
Walmart revenue: $365 billion
ICPs are moving upstream.
If you feels that “paying $50 for a service every month is getting too expensive” then you can rest assured that most software business definitely don’t want you as their customer.
Just as people expect to be able to build more with AI, vendors will expect their customers to churn because of it. Expect them to spend even less time catering to their weakest customer segments in the months to come.
Show more
Curator: "And here, ladies and gentlemen, we have an exhibit showing the last known Reddit-based communication of a now-extinct kind of human."
Museum of Artificial History Visitors: "Oooooh!!"
r/opensource now doesnt accept AI-assited projects
do you know what project uses AI-assisted code? the Linux kernel.
the LINUX KERNEL ISNT ACCEPTED by r/opensource now.
The result of this poll right now (around 50:50) is as baffling as it is an indicator where this is clearly going.
A: Uses AI coding agents HEAVILY in implementation and review and doesn't look at the code at all
B: Hand writes and reviews everything
Assuming the products solve the same problem etc, which product would you feel more comfortable trusting as a user?
Show more
Who is building this?
Input: human-edited podcasts (over 100 examples, raw+edited audio+Pro Tools Files) + 1 unedited podcast recording + custom episode-specific prompt
AI: Magic
Output: 1 edited podcast episode, ready to publish
Show more
A lot of the reasoning behind a $50+ pricing floor is segmentation.
People who will pay $50 would also pay $10. But not many who will pay $10 would also pay $50. And those “cheap” customers are often the most demanding.
You CAN get to $50k MRR on $10 subs (I did with FeedbackPanda), but is SO much more work on the customer service side. And often, low-budget customers are extremely demanding and unreasonable.
So, you segment them out. You set an entry price tier at $50 ( I did that initially with Podscan, later moved to $100 for even more filtering) and get rid of interest (and workload) from that segment.
Also, very importantly, professional customers (who buy for their job) are much more likely to have a 3-4 figure budget for tooling. You can expand into existing teams much better than from one individual customer to another unrelated one.
Reducing prices tends to hurt revenue and your sanity. Increasing prices does the opposite in most cases.
(And for the extremely price-conscious customers, you can always lure them in with significant discounts.)
Show more
I'd love to know how many small SaaS products could make perfectly good money charging $5 or $10 a month.
Instead, half the internet seems to be selling $49/month subscriptions to people who need the tool twice a week.
I wonder how many customers never even get as far as the free trial?
Show more
This week has been a great year.
During this red-teaming exercise, we also found a vulnerability that allows for unauthenticated remote code execution in Brotli, a widely-deployed compression library included in many pieces of software such as Node.js, Bun, and Envoy.
The flaw could let an attacker run their own code on affected systems by sending or replying with malicious compressed data, without any need to create a user account. That is, an unpatched server that accepts compressed input could be taken over by a malicious client, and an unpatched client that accepts compressed input (such as “curl --compressed”) could be taken over by a malicious server.
This root cause issue was actually fixed in the Brotli source code in February, but it wasn’t known at the time that it gave rise to a security vulnerability and there was no more recent release of Brotli. Since Brotli is built into other software, any software which includes this library needs to take the update too, followed by the users of that software. We disclosed the vulnerability to Brotli and other downstream projects such as Node.js, which released or are currently releasing security updates, and Brotli cut new release versions and published a CVE.
More details on the patch and mitigations below:
Show more
I still believe PHP is a great language (and Laravel is a stellar framework).
Kind take: AI is helping us build better software.
Less kind take: if you thought AI code was slop, you should see what humans have been writing for the last few decades.
idk what words to choose here this is crazy
Ah, good, another one.
(Glad many turned this off the night before Wednesday...)
Set session.upload_progress.enabled=0 till next PHP release to block an unlikely RCE vector (CVE-2026-115560). Already recommended for CVE-2026-109619 Wed, keep disabled. Only apps with non-default serialize_handler switching it to "php" at runtime can be affected. #
php# #
phpc#
Show more
All those CVEs should humble all the programmers who still think they're better than AI.
Who's better actually doesn't matter. Human + AI = unstoppable. Be that human.
This looks like the path forward. TDD is great, but agent-written tests are so cheap that many devs skip the review process. PDD might just be what is needed to increase clarity and specificity.
This analogy is the best I've ever heard when it comes to how LLM-generated code looks, works, and what the role of developers is morphing into.
Pre-AI codebases are sturdy, with scaffolding that allows for human comprehension and, at the same time, prevents hyper-optimization. We need to "get" the code, not just run it.
Post-AI codebases let go of all pretense to be both accessible by interpreters/compilers/runtimes AND humans, and contain JUST what is needed to provide the expected outcomes.
And that is what developers are realizing they must measure, review, and verify. Not the code, but the constraints and tests around it.
Show more
You know these Star Trek LCARS interfaces that always looked like they were specifically designed to answer a plot-driven question visually and were never the same, always looked haphazardly constructed in that moment?
I think, yet again, Star Trek understands the user interfaces of the future better than we do in the present.
I think we are a very short time away from applications designing and assembling UI in the moment versus having it pre-designed. Contextual interfaces won't just consider what they present, but also who they're showing it to (on a highly (inter-)personal level) and when those people need which information in their workflow.
Show more