Software developer + product builder, launching for e-commerce, local business, LLM/AI experiences. For hire to build web products, fractional CTO, tech advisor
NYC
Joined November 2007
- Tweets2.8K
- Following1.6K
- Followers885
- Likes2.5K
I’ve always been a claude/anthropic customer and always recommended them and brought them to companies I’m working with. But there’s no way around it: they are full of shit on this one. They always said 20x and that’s it. I never heard that the weekly limits were 10x. I just saw 20x everywhere. And this was backed up by the discount language and more. They lied to us and tricked us about what we were buying and ripped us off, which is a very severe blow to their trust and reputation and will be remembered. And on top of that they make it sound almost like we were too stupid or it was some misunderstanding? Gross.
Don't gaslight us.
"I get that some new users assumed 20x applied to both limits. We could have done better here, and I'm sorry."
If you didn't want to be misleading, you would have left out the '50% savings' claim on the $200 plan—at 10x the price of the $20 plan ($20 x 10 = $200), a 50% discount clearly implied we were getting 20x the usage.
Figma doesn’t support AI tools in 2026.
Hey David, Gayani here from Figma. You're right that our remote MCP server only accepts clients on our supported list, and Pi isn't on it yet. You can see the current list in our MCP catalog at figma.com/mcp-catalog. If you'd like Pi considered for a future addition, please fill out this form: forms.gle/qSvUawwznWyoj8Go7.
Sam Kennedy retweeted
Just another horror story from @Airbnb_uk for your records. Two weeks ago we arrived at our booked accommodation, accessed it using the security codes given, and when we entered, we found a very startled young female student, whose rented accommodation we’d just invaded. 1/2
@elliottdotorg @wendyperrin @ThePointsGuy @garyleff @crankyflier @veraborenstein @veraboron @naborchers @ConsumerReports @CRAdvocacy @FairShake @jeremypgordon @bchesky @skift @TechCrunch @CNN #AirbnbNightmare #AirbnbFail #Airbnb
They double down on charging me full price for an accommodation where I was injured and couldn’t stay because the place was full of broken glass. Too much AI in the @AirbnbHelp support chat! They’ve lost their humanity and their common sense.
I never used to hit limits with @Claude Code, so I never felt the need to maximize usage. Now that limits are more apparent, my mindset has shifted to squeezing every last drop out of my subscription. Might backfire on @AnthropicAI... scarcity changes behavior.
Paid @sanity_io hundreds of dollars to cover a bandwidth overage and still dead in the water. No support whatsoever is available... just an AI chat bot and discord server where you get ignored.
Sam Kennedy retweeted
Sam Altman says Slack has many positives, but it creates endless fake work
We need an AI-native productivity suite to replace docs, slides, email, and Slack
Not add-on features, but trusted agents that handle work and only escalate when needed
This finally feels within reach
If you're a dev but you don't know how to use git bisect, make that the next thing you learn.
kevin3010.github.io/git/2025…
Wow my first ever post to hackernews hit the front page. news.ycombinator.com/item?id…
I spent a few hours last weekend building a web server with zero application code.
Every HTTP request goes straight to an LLM. It decides what to do in an agentic loop using three tools: database, webResponse, updateMemory.
Here's what happened →
These feel like problems of degree, not kind.
Inference improving ~10x/year. Cost heading to zero. Context windows growing.
When inference hits 100ms, the question shifts from "how do we generate better code?" to "why generate code at all?"
Open sourced the whole thing. Check `prompt.md` to see how it works. Customize it to build whatever you want.
It's slow, expensive, and kinda dumb, but if you want something to mess around with, go nuts.
github.com/samrolken/nokode
Recent Azure/AWS outages are reminders that every cloud provider is a single point of failure in your architecture.
Companies confuse technical debt with architecture debt because the symptoms look the same - delays, outages, rising costs.
But the fix is completely different. Technical debt requires building work: coding, refactoring, testing. Architecture debt requires organizing work: governance, standardization, cross-org coordination. One needs more engineers. The other needs executive authority to make decisions across team boundaries, sunset duplicate platforms, and enforce standards. You can't fix architecture debt in a sprint because it's not about code - it's about power, policy, and organizational structure.
Sound familiar to anyone?