We've decided to sunset Arc on December 22, 2026. That's not an easy sentence to write. We spent years building Arc and celebrating each and every release along the way: we have so much pride and love for what we made alongside the Arc community. Our priority is to deliver best-in-class security for our members. Keeping a browser secure takes constant, dedicated work that is only increasing in the age of AI. Dia was built from the ground up to meet today’s security standards, so that's where our engineering and security teams will focus moving forward. We've worked to make switching to @diabrowser as easy as possible for Arc members. Here's how: · Your passwords, bookmarks, extensions and history come over to Dia seamlessly. · Spaces, Folders, and Tab Groups are in Dia and import over with your data intact. · Dia now surpasses Arc benchmarks in stability, speed, and security. · The browser features you use in Arc are free in Dia, and the AI is optional. Thank you for using Arc, for pushing us to make it better, and for building alongside us. The team that made Arc is the same team behind Dia, and some of our most ambitious work is just ahead. We'd love for you to be there with us when it lands.

3 steps to becoming an actual software programmer 1. Build personal software 2. Build internal software (for a select group of people) 3. Build public-facing software If you've only ever built personal software you're not qualified to build public-facing yet. As you climb the rungs the stakes get higher, your constraints get tighter, and you need to QA harder. So my advice for anyone who's never built an app is this: Find a small group of testers (even 1 is great) that will actually use an app you built in their real lives. The feedback you'll get will blow your mind. It'll show you how forgiving you are of your own crappy product. You'll begin to focus on process and quality. It'll be frustrating, slow, and hard work. That's programming.

🫡 appreciate yall a ton Everyone who doesn’t qualify under my “have your boss pay for it” callout should probably be on boot :)

it is absolutely imperative that you set up your timeline to encounter more old art, and less new AI slop. give your attention to artists who have labored painstakingly to actualize their vision, one intentional brushstroke at a time

... you can't teach every such lesson upfront. You work with your agent. You correct it. Traits saves the underlying lesson, applies it to future code, and sends violations back to the agent to fix. Teach your agent to code the way you do. traits.sh

Jev was multimodal all along Yep, the Jev you know and love was an image model this whole time. We just chose to disable it because models tend to be less intelligent on other modalities. Header: TypeSafe-Danger-Zone-Images: true

they're trying to cut open the bird to find the song

Made a rain jacket that's black when dry and turns orange wherever the rain hits it metalforge.xyz

Introducing /create-verification-skill Allow your agent to verify its own work and bring you evidence with e2e as the verification layer. Based on @poteto skills ~/ npx skills add tester-army/e2e --skill create-verification-skill