We're hiring a Research Engineer at @Arsenal ⚽🔴⚪ to work directly with our Men's First Team!
We're building state-of-the-art AI models for the football domain. This role will focus on building the application layer for our research to advance coaching and analysis workflows.
New in Claude Cowork: teach Claude a skill.
Record your screen while you do a task, talk through it as you go, and Claude turns it into a skill it can run again. Find it under Record a skill in the + menu of the Claude desktop app.
Available on Pro, Max, and Team plans.
AI is extremely good at spending your money very quietly.
our own token spend went from a rounding error to more than 10% of payroll in a year. one week in May we burned through $1.5 m. our CFO didn't love telling me that number, and he really didn't love telling the internet.
but every finance leader we talk to is living the same story. the bill keeps going up and teams can't answer basic questions about it. which team is driving it? which models they're using? what changed this month? whether a cheaper model would do the same job?
so finance gets two bad options: keep paying and hope, or cut broadly and slow down the work that's actually compounding.
we built a third one. Ramp now connects to OpenAI, Anthropic, Gemini, Cursor and pulls it all into one place. see it, understand it, control it - down to a single API key. built with 1,000+ companies managing 100T+ tokens a month, and now spending less than they expected too! try it today at https://t.co/dbQK7feZaA
This reflexion is timeless and incredibly relevant today:
"Until you make the effort to get to know someone or something, you don't know anything. There are no shortcuts to knowledge, especially knowledge gained from personal experience."
Ben Horowitz
We desperately need a smart model router.
1. We’re seeing a model explosion: GPT-5.6, Grok 4.5, Muse Spark 1.1, GLM-5.2, and Fable 5 all launched within the past month.
2. Even for a single model family like GPT-5.6, there're 3 (Sol, Terra, Luna) and 5 reasoning-effort levels.
That is far too many decisions for users to make manually.
The best model should be selected automatically based on the task, latency, quality, and cost.
Hey @GoogleCloud@Firebase , I'm waiting for urgent support on an open case (project suspension), I would really appreciate any help getting this looked at.
Madrid is speedrunning the “superstar city” cycle.
For decades it was a stunning capital but still strangely local, Spanish and underrated vs London, Paris or NYC.
Then post-Covid, everything changed. Rich Americans moving in. LATAM money. Luxury hotels. F1. International schools. Coffee shops. Private members clubs. €8 pistachio lattes.
Now house prices are +62% in 5 years, rents +64%, and locals are protesting because the city is becoming a lifestyle product for people who don’t actually need to live there.
This is basically what happened to Lisbon/Barcelona/NYC/London, but compressed into one post-Covid cycle.
This is the tragedy of great cities: the more desirable they become, the less they belong to the people who made them desirable.
As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:
1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales
Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.
A healthy team needs a mix of these, depending on the product:
- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2
Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
The Product role is having an identity crisis too.
Engineering has found its AI-native interface - SWE agents dramatically increase individual leverage.
Companies are asking PMs to use AI, but they haven't evolved the role.
So there are two camps.
The old-school PM.
AI accelerates the old job: more PRDs, more strategy decks, more docs. Lots of output, not much judgment.
The Builder PM.
Builder PMs use AI to expand their role across the product lifecycle.
They explore a much larger surface area of ideas to arrive at the best. They run agents for market and user research, query logs and analytics directly, generate competing ideas, then curate the best ones.
They constantly evolve their workflows to take advantage of the latest in AI.
Their outputs are increasingly prototypes rather than docs - engineers react far more constructively to demos than docs.
They do this all without compromising on the craft -they still form a strong point of view on what should be built and why.
I think the role is moving much closer to Builder PMs.
Pricing is often guesswork for founders, so I built Pricing Prophet ✨: a tool that audits their pricing and gives actionable recommendations so they stop leaving money on the table...Link below👇🏿