Figma

Aspect Ratio: Locked. Rolling out today.

Presenting code made easier because now you don't have to reformat it Figma Slides, now with code blocks

Figma is growing in the Big Apple! 🍎 🗽 It's incredible to think we'll be doubling the size of our New York City office in the coming year. This marks a significant milestone, as we continue to grow, innovate, and build the future of Figma together. We opened our NYC office in 2021, but our team of Figmates in the Empire State have been an integral part of our success from the start. This investment reflects Figma's commitment to creating more opportunities for collaboration, creativity, and community –– and we couldn't be more grateful to Empire State Development for supporting our growth in New York. I got to speak with Bloomberg to discuss this exciting development and how it aligns with our broader goals for growth, innovation, and fostering a workplace where our people can thrive. We’re not just expanding our space... we’re expanding the space for what’s possible. To our amazing team: Thank you for making this growth possible. To those considering joining us: Now’s the perfect time. We’re just getting started. Here’s to the future of Figma in NYC! Check out figma.com/careers https://lnkd.in/gNg_3Zhf

“I’m not a good writer.” At Figma, I hear this often—right before watching those same people expertly describe technical architecture or pitch product roadmaps. On the blog today: Why writing matters for everyone in product development, and how to move past common blockers to become a more confident storyteller. Five tips: 1. Start with speech, not writing. If you’re stuck in your own head: Start by explaining it to someone else verbally. (Or record yourself talking aloud.) You may find it clearer than your first written attempt. 2. Begin a piece, don’t introduce it. Delete your first paragraph entirely. Those opening sentences are often just you warming up—the real story usually starts later. Drop your reader into the action. 3. Create a clear structure. Just like you’d give someone directions, use signposts to guide readers to where they want to go. Paragraphs should build on each other. Each sentence should raise questions answered by the next. 4. Delete your adjectives. When polishing, be ruthless. Cut unnecessary adjectives. Use stronger nouns and verbs instead. Experiment with structure—sometimes your ending makes a better beginning. 5. Get feedback early and often. The difference between ‘good’ and ‘bad’ writers is their willingness to embrace feedback, work with editors, and put in deliberate practice. It’s a muscle. Remember: If you can think, you can write. Writing is organized thinking. If you can think, you can write. “If you’re thinking without writing, you only think you’re thinking.” —Leslie Lamport


Some updates and a reminder about the billing changes we announced in December: 📆 Next Tuesday, March 11, the new Figma billing and admin flows, along with new seat types, will start to roll out. 📁 As a follow-up, our team has been working on Connected Projects: ➡️ Use the Figma seats on your team to collaborate inside another team; Pro users can connect up to 3 projects, Organization 6, and Enterprise at 15. ➡️ If you initiate a Connected Project, your plan determines the features available to all users collaborating in the project (ex: an agency on Figma Org collaborating with freelancer on the Pro plan could leverage Branches) ➡️ Resources like shared libraries and fonts can be enabled for everyone in the project. 🔗 Learn more here:
https://figma.bot/3DcLeCN

How designers at Figma organize their files, do engineering handoffs, design crits and more → https://figma.bot/4kimNo6 Jayneil Dalal with product designer, Tammy Taabassum

Figma Slides, now with plugins → Rehearse → IconScout → pdftodesign by ‹div›RIOTS → Mesh Gradient → Jitter

You'll never have to say "Hey, did you see my file?" again. → Logged-in collaborators in the same team or organization, including invited guests are recorded as having viewed the file and are shown viewer history for the file → Visitors to a file from a public link, open session, or those outside your team or organization will not be recorded in view history → If you want to opt out of being recorded as a viewer on files for all teams and organizations you are part of, you can do so from your account settings More details here: https://figma.bot/4hQ9DwR File view history rolling out this week.

As publishers figure out how to thrive in the digital era, the pace for change is only accelerating. How The New York Times, The Economist and The Minnesota Star Tribune (with Code and Theory) have reinvented their design.

Forget writing code line by line. Vibe coding is more like having a chat. You describe what you want, AI makes it happen, and you keep the dialogue flowing until it feels right. Less syntax, more vibes. In computing’s early days, programming meant meticulously preparing physical punch cards—each representing a single instruction—and waiting hours or days to see if they worked. Even as we progressed to typing code directly into computers, developers still faced a significant gap between conceiving an idea and seeing it come to life. While 75% of Replit users never write traditional code and AI-assisted development tools are raising millions, experienced developers are reporting a consistent pattern: quick wins followed by what Vincent van der Meulen calls the “valley of despair,” Anro Robinson “pile of spaghetti code,” and Julius Tarng “ something that works, but your code is in such a f---ed up state that there’s no way it’ll pass code review.” The takeaway? Those benefiting most from “vibe coding” are often seasoned developers who can spot problematic outputs, debug effectively, and know when to switch approaches. As Barron Webster puts it: “It’s like a pastry chef would know what causes croissants not to rise, but someone who just orders them at a cafe wouldn’t.” Read more about the promises and perils of conversational coding, featuring insights from engineers at Figma, Anthropic, and beyond: https://lnkd.in/eyFXErFk