swift-build being open source is awesome for understanding how Xcode compiles your projects.
Pick an issue and try to fix it: https://github.com/orgs/...
E.g. this one breaks Sentry's package (multiple .xcframeworks, same binary name): https://github.com/swift... Just noticed the Swift team has list of bugs that happen when SwiftPM integrates with swift-build so I thought it’d be a good idea to learn more about the internals of swift-build to help solve some of them. First PR:
github.com/swiftlang/sw... 
every founder of a sequoia-backed company should be asking why they haven’t fired maguire yet
You too can impress your customers, friends, and future friends by building canvas experiences with the tldraw SDK. Visit tldraw.dev to learn more. Check out Genio at genio.co/ Welcome @Geniolearn as the newest customer for the tldraw SDK! Genio creates learning tools for students and uses tldraw for visual note-taking in their Genio Notes app on web and mobile. 
You too can build canvas features and become a customer at tldraw.dev. Check it out at snaptrude.com Welcome @snaptrude as the latest customer for the tldraw SDK. Snaptrude uses tldraw to power its present mode where users share and collaborate around architectural designs. 
Heavy images hurt performance, add costs, and degrade UX.
Here's how to find the culprits with Observability. 👇 www.youtube.com/watch?v=5eLM... And if you want to build something like this, we have a starter kit for building agents that control the canvas. Check it out here: tldraw.dev/starter-kit... You can also read the source code at github.com/tldraw/tldraw. Check out tldraw.com to try it yourself. We're unshipping the fairies at the end of the month, so get em while you can! We also encouraged the agents more to request new context. This would create a new prompt to continue what they were doing before, but with new context about the canvas, todo list, and fairies, too. You can see this if you select three fairies and prompt the group. One fairy will be elected as the orchestrator, create the project, and wait for the other fairies to finish the work. 
In earlier builds, fairies had different personalities and talents. The orchestrator fairy would assign tasks based on the most appropriate worker fairy available, preferring to use a more creative fairy for some tasks and more operationally inclined fairies for other tasks. We ended up using a 'fairy management system', where one fairy would draft the plan, create the todos, assign the todos to other agents, and then coordinate their output with followup todos. For example, if three fairies began working on a wireframe with todos for a header, body and footer, they would often place these in completely arbitrary places relative to the others. There were many issues with this. What if two agents start working on the same task? Even if agents work on different tasks, how do they work together towards an overall goal? And in doing this, how do they coordinate between different parts of the overall goal? Our first attempt at orchestrating multiple fairies was to create a shared todo list for all of the agents and give it as context alongside screenshots and structured data about the canvas. How do you coordinate when agent spend most of their time 'underwater' and only briefly and intermittently ‘return to the surface’ for context? In a multi-agent system, things can change a lot while an agent is working. Another agent might be editing the canvas. Humans might be moving things around. For example, on tldraw, one person can draw something while speaking to their collaborator and looking at what they are drawing. An agent can only see the state of the canvas or communicate with other agents before and after it has finished drawing.