something you should know: codex threads can now message each other! really useful if for example you want to have one chat thread to handle stacked prod deployments. just paste the thread id to your other codex chats and it'll message the deployment thread to take over!

Sharing here the message I just sent to the whole Wix team: Today is a sad day for me. We have made a very hard decision. We are reducing the Wix team size by roughly 20%. It is one of the hardest decisions I have had to make, but I am confident it is the right one, and I will explain why. Before I go into anything else, let me say - this is a very hard decision because I will be saying goodbye to many people who have worked with me for years, many whom I call friends, people I trust and respect, friends who poured their energy and talent into Wix. Team members I know personally, and team members I never had the chance to meet, but whose commitment and contribution I have witnessed. So thank you. Thank you for the effort, for the talent, for the passion, and for the friendship. We are doing this as a company-wide change, a decision that will impact the entire organization, driven by how we need to operate going forward. Why are we doing this? The first reason is the Shekel/Dollar rates. In the past few quarters the exchange rate between the Shekel and the US dollar has shifted significantly as the Israeli Shekel strengthens against the US Dollar almost every day. As the majority of our teams are Israel-based, a very meaningful portion of our costs are shekel-denominated, while our revenue is largely dollar-denominated. This creates a structural pressure on our ability to operate at our current scale. It is a reality that directly shapes what is sustainable for our company. The second stems from the fast evolution of AI capabilities. We have witnessed the most significant shift in how companies are built since the invention of modern programming languages in the 1970s. This is not just about adopting new tools - it is about rewiring how companies are built, how they think, how they manage and how they operate. Companies that embrace this change will not only build faster; they will build things the previous generation literally could not have imagined. We are already taking concrete steps in this direction. As you know, we've recently introduced new roles like Xengineer and Creators, designed from the ground up around AI-native ways of working, a meaningful step towards the kind of company we are becoming. It also means we need to become a faster, leaner, and flatter organization. We are moving to a structure with fewer levels between any member of our leadership and the most junior person on the team. Fewer layers means faster decisions, clearer ownership, and less distance between the people setting direction and the people building the product - but it also means a smaller number of people. It is clear to us that in this new era, companies need to make this change in order to lead and compete or risk falling behind. We are choosing to compete. It is a painful change, a change that touches the lives of many, but I truly believe we have no other choice - we must evolve. To those of you who are being let go I want to once more say: Thank you. Those who are affected will be contacted in person, directly, and we will do everything in our power to handle each conversation with sensitivity, respect, and the care you deserve, you will also be granted personally curated separation packages. Many of you have given years to this company and built things we are genuinely proud of. I am personally grateful for what you've created, for the culture you've shaped, and for the trust you placed in us. More than anything, this decision was about the shape of the company we need to become. We own that - and we own the responsibility of supporting all of you through what comes next. To those of you who are staying What happens in the next few days matters. The people leaving this company are your colleagues, your friends, people you've built things with. They deserve to walk out of here with their heads held high, knowing that their work was real and that we recognize it. Please treat them with the respect they've earned. How we say goodbye says as much about who we are, as anything we've ever built together. Our broader commitment Before anything else, our commitment is to our users - to make the hard decisions so Wix continues to be the company that helps them succeed. We work for our users. Millions of people run their businesses on Wix. Their world is also changing, also uncertain, also shaped by the current shifts. They rely on us - our reliability, our innovation, and our commitment to their success. The responsibility does not stop with our users - behind every Wix shareholder is a real person whose savings, pension, or investment is tied to how we perform. We take this responsibility very seriously. If we do not make this change, we will be failing our responsibility to our users, our shareholders, and our employees. In the long run, what is best for our users is best for our employees and best for our shareholders. Today's decision was made to ensure we are here for our users and our shareholders, you among them, stronger and more capable, for years to come. We are doing this today because we are committed to building a company that is healthy, durable, and positioned to lead. We will come out of this faster, stronger and better equipped for this new era. Avishai

2/ Think bigger. This is the most common mistake I see: tasks scoped too small. At this point you want to be aiming for work that would take a good engineer multiple weeks.

My thought for the day: The Peter Principle probably applies to software; steadily increasing ambition and loosening constraints makes it rise to a level of complexity and incompetence that ultimately dooms it

Claude's first day at Dunder Mifflin

This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15 direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian

Did you know about Clear-Site-Data header? 👀 One HTTP header to clear cookies, storage, or cache for your site. Perfect for logout flows. Learn more 👇 developer.mozilla.org/en-US/…

Talking to smarter folks than me, I'm convinced many of the AI folks in my timeline are full of shit. Nobody is "running 20 agents over night" and building stuff for actual users. Maybe some are building internal tools or disposable software. Maybe. But building software people like using? That doesn't get hacked on day one or blow up after the 3rd user? Nope. I don't even understand what that's supposed to look like. Do you work out a 57 pages document that perfectly describes what you want to build and then summon 14 agents and have them run wild for 6 hours? And what comes out on the other end isn't a broken pile of shit? Nope. Not buying it. PS: it may also be that I have an IQ of 82 and can't figure it out.

I don't want to go too deep on AI DDD. My current thinking: GOOD: Ubiquitous Language / Bounded Contexts / ADR's BAD: Entities / Value Objects / Aggregates / Domain Events Essentially, use DDD to document the app but don't prescribe the shape of the app

Invincible Season 4 Episode 7 has a 9.9/10 rating on IMDb with 30,000 reviews It's now the tied with the Season 3 finale as the highest-rated episode in the series