AI tools are only as useful as the content they can reach. The Box Connector is now live for all paying @grok users, giving Grok Business secure, permissions-aware access to the enterprise content already living in Box. Watch here. 👇

AI-native software engineering teams operate very differently than traditional teams. The obvious difference is that AI-native teams use coding agents to build products much faster, but this leads to many other changes in how we operate. For example, some great engineers now play broader roles than just writing code. They are partly product managers, designers, sometimes marketers. Further, small teams who work in the same office, where they can communicate face-to-face, can move incredibly quickly. Because we can now build fast, a greater fraction of time must be spent deciding what to build. To deal with this project-management bottleneck, some teams are pushing engineer:product manager (PM) some teams are pushing engineer:product manager (PM) ratios downward from, say, 8:1 to as low as 1:1. But we can do even better: If we have one PM who decides what to build and one engineer who builds it, the communication between them becomes a bottleneck. This is why the fastest-moving teams I see tend to have engineers who know how to do some product work (and, optionally, some PMs who know how to do some engineering work). When an engineer understands users and can make decisions on what to build and build it directly, they can execute incredibly quickly. I’ve seen engineers successfully expand their roles to including making product decisions, and PMs expand their roles to building software. The tech industry has more engineers than PMs, but both are promising paths. If you are an engineer, you’ll find it useful to learn some product management skills, and if you’re a PM, please learn to build! Looking beyond the product-management bottleneck, I also see bottlenecks in design, marketing, legal compliance, and much more. When we speed up coding 10x or 100x, everything else becomes slow in comparison. For example, some of my teams have built great features so quickly that the marketing organization was left scrambling to figure out how to communicate them to users — a marketing bottleneck. Or when a team can build software in a day that the legal department needs a week to review, that’s a legal compliance bottleneck. In this way, agentic coding isn’t just changing the workflow of software engineering, it’s also changing all the teams around it. When smaller, AI-enabled teams can get more done, generalists excel. Traditional companies need to pull together people from many specialties — engineering, product management, design, marketing, legal, etc. — to execute projects and create value. This has resulted in large teams of specialists who work together. But if a team of 2 persons is to get work done that require 5 different specialities, then some of those individuals must play roles outside a single speciality. In some small teams, individuals do have deep specializations. For example, one might be a great engineer and another a great PM. But they also understand the other key functions needed to move a project forward, and can jump into thinking through other kinds of problems as needed. Of course, proficiency with AI tools is a big help, since it helps us to think through problems that involve different roles. Even in a two-person team, to move fast, communication bottlenecks also must be minimized. This is why I value teams that work in the same location. Remote teams can perform well too, but the highest speed is achieved by having everyone in the room, able to communicate instantaneously to solve problems. This post focuses on AI-native teams with around 2-10 persons, but not everything can be done by a small team. I'll address the coordination of larger teams in the future. I realize these shifts to job roles are tough to navigate for many people. At the same time, I am encouraged that individuals and small teams who are willing to learn the relevant skills are now able to get far more done than was possible before. This is the golden age of learning and building! [Original text: ]

Your AI journey just got simpler Join our AMA and see how RedotPay lets you pay for AI tools and subscriptions! 🗓 May 13th | ⏰ 3 PM UTC | 🚨24 hours to go Leave your questions 👇

Most AI tools look the same: dark UI, monospace font, glowing border, vague copy about "agents." We took a different approach. Bloome looks like something you'd want to live in. Built for humans first, made beautiful on purpose.

Most AI tools help you automate the process, but don’t understand your context. Discover what's doable at Amazon Quick turns scattered data into presentation-ready resources. Ask for a weekly pipeline review and Quick compiles real-time Salesforce data into a report. Automate your workflow without inputting a single line of code.

Most AI tools stop when you stop. Devin in Windsurf 2.0 doesn’t. It runs on its own VM after you close your laptop. Debugging, testing, deploying. The PR is waiting when you return. Live today in Windsurf 2.0.

Most AI tools generate answers. But engineering is about making the right decisions. Meet the new PatSnap Eureka Engineering — a collaborative R&D AI Agent that helps teams move faster from search → decision-ready plans. Try PatSnap Eureka Engineering today.

✨ AI tools to spark everyone's creativity 📺 the best of YouTube right in your living room ❤️ more than $70B paid to creators, artists & media in 3 years Just a few highlights from @nealmohan's community letter!→

Which types of AI users are you? 1. The Skeptic: "I tried ChatGPT once. It got a fact wrong. AI is useless." 2. The Dabbler: Has 12 AI tools. Uses none of them consistently. 3. The Optimizer: Spent 6 hours writing the perfect prompt to save 10 minutes. 4. The Delegator: "Just handle it." Lets agents do the work. Checks results. 5. The Builder: Makes the agents.