Techlist.io - Korean Tech Blog Curator

figmaJun 25, 20242 min readCurated summary

Inside the Redesigned Figma, Where Your Work Takes Center Stage | Figma Blog

UI3 is Figma’s third major redesign, created to manage the complexity accumulated over nearly a decade of new features. Its central goal is to put users’ work—not the interface—at the center while preserving professional workflows and making Figma more approachable. The redesign also establishes a flexible foundation for products such as Dev Mode, Figma AI, and Figma Slides. ## Why Figma redesigned the interface - **Center users’ ideas:** New capabilities such as interactive components and AI risked making the interface feel crowded or distracting. - **Serve both beginners and experts:** Figma aimed to become more intuitive for newcomers without removing the power and familiar ergonomics professional designers rely on. - **Adapt to modern design practices:** Reusable components, generative AI, and higher-level abstractions require tools that provide building blocks rather than focusing only on individual pixels. - **Prepare for the future:** UI3 supports Figma’s broader ecosystem, including closer connections between design and code, Dev Mode, Figma AI, and the newly introduced Figma Slides. ## Clearing the stage for the canvas - The redesign began by maximizing canvas space and reducing visual distractions. - Figma experimented with extreme concepts, including interfaces that appeared only on hover and layouts where panels constantly appeared and disappeared. - These approaches made the workspace feel unstable, so the team moved toward a more consistent solution: - Resizable and collapsible panels - A slim toolbar positioned at the bottom of the canvas - The ability to hide the interface completely and reveal panels when needed - The new structure creates a roomier workspace and provides a consistent framework for switching between Figma products. ## Iterative design process - Figma explored hundreds of interface variations. - Designers built and used many prototypes internally to evaluate how each approach affected real workflows. - Features and controls were deliberately removed until the team identified what users genuinely missed, then selectively restored them. UI3’s practical recommendation is to give designers more control over the interface: keep tools accessible, but allow the canvas and the work itself to take priority.

Figma Design Systems User Experience Generative AI+2

figmaJun 25, 20243 min readCurated summary

Should robots be building our homes? | Figma Blog

Icon CEO Jason Ballard argues that robotics and AI could make housing faster, cheaper, more durable, and more sustainable. Icon’s robots 3D-print cement-based walls, while its Vitruvius AI system is intended to generate designs, budgets, schedules, and eventually robotic construction instructions. Ballard sees the same technologies eventually supporting construction beyond Earth, including on the Moon. ## From Housing Mission to Robotics - Ballard’s interest in construction grew from work with homeless shelters and sustainable building in Colorado. - Although he once planned to become an Episcopalian priest, he chose to pursue housing affordability, dignity, beauty, and comfort as his life’s mission. - A master’s degree in space resources also shaped his interest in using robots for construction in extreme environments. ## Why Icon Focused on 3D-Printed Walls - Icon believed advanced software and robotics could improve construction. - The company targeted walls because they are among the slowest, most complex, and labor- and material-intensive parts of building. - Its system extrudes layers of cement-based material reinforced with steel rods. - The printed wall replaces much of conventional construction, including framing, insulation, drywall, sheathing, finishes, and siding. ## Claimed Benefits of 3D-Printed Homes - Faster and potentially more affordable construction. - Walls rated to withstand fires for two hours and 57 minutes and winds up to 250 miles per hour. - Some residents in Icon’s 3D-printed neighborhood reportedly pay as little as $17 per month in energy costs. - Icon says its homes have performed strongly in testing for compressive strength, bending, energy efficiency, fire, flooding, hurricanes, and termites. - Ballard also emphasizes that the homes can be aesthetically appealing, not merely functional. - He predicts that conventional stick-frame construction could eventually become obsolete or even prohibited. ## Vitruvius and AI-Driven Architecture - Icon had long worked on automating architectural tasks but struggled with the complexity and computational demands involved. - Building projects must account for budgets, schedules, designs, and highly localized permitting requirements. - Building codes vary across thousands of jurisdictions, making them difficult to interpret and apply. - Icon began pursuing generative AI training roughly two years before the interview. - The company collected floor plans, building designs, permits, and related documents to create what Ballard describes as the world’s largest architectural dataset. - Vitruvius is intended to produce architectural designs and construction plans, then translate them into instructions for Icon’s robots. ## Construction on Earth and Beyond - Icon’s broader ambition is to use autonomous construction systems in challenging environments. - The company is collaborating with NASA on potential infrastructure for the Moon. - Ballard presents lunar construction as an extension of the same incremental process used to improve housing on Earth. Icon’s approach combines automated design with robotic construction rather than treating AI as a standalone design tool. If its performance and cost claims continue to hold up in real-world projects, the technology could offer a promising alternative to traditional construction, particularly where labor, materials, or access are limited.

AI Generative AI Automation Robotics+4

figmaJun 25, 20242 min readCurated summary

Config 2024 In Review | Figma Blog

Figma’s Config 2024 announcements focus on making design more exploratory, efficient, and connected to development. The company introduced Figma AI, a redesigned UI3 interface, Figma Slides, major Dev Mode improvements, and quality-of-life updates. Figma argues that as AI makes software creation easier, thoughtful design will become an even stronger differentiator. ## Figma AI: Faster exploration and production - **Visual Search** lets users find similar designs across accessible team files using a screenshot, selected frame, image, or sketch. - Improved **Asset Search** understands the context of queries, even when search terms do not match asset names. - New AI-powered efficiency features can: - Generate realistic images and copy - Rewrite, translate, or vary text - Automatically create prototype connections - Rename layers - **Make Designs**, available through the Actions panel, generates initial UI layouts and component options from text prompts. - Figma says these tools are built around practical user needs rather than AI hype, using large language models to reduce tedious work and help designers explore more possibilities. ## Other major Config announcements - **UI3** redesigns the Figma interface. - **Figma Slides** introduces a dedicated environment for building, collaborating on, and presenting presentations. - **Dev Mode updates** aim to move teams from designs being merely “design ready” to being fully “dev complete.” - Additional improvements target **Auto Layout, UI kits, and the prototype viewer**. ## Availability - Figma AI and UI3 were announced as limited betas with gradual rollout. - Users can join the waitlist through Figma’s help menu by selecting **“Join UI3 + AI waitlist.”** Figma’s overall direction is to support the full path from idea generation through design, presentation, and development, while using AI to automate routine tasks and expand creative exploration.

AI Design Systems Large Language Models Prototyping+3

figmaJun 25, 20243 min readCurated summary

Ovetta Sampson on Inputs and Outputs | Figma Blog

Minimum viable data is the idea that AI projects should begin with representative, high-quality data—not with the most powerful model or feature. Ovetta Sampson argues that model outputs are overwhelmingly determined by their inputs, which reflect human choices and historical biases. Product builders should therefore question whether AI is necessary, who it serves, and whether the data is equitable enough to avoid harming overlooked groups. ## Data Quality Shapes AI Outcomes - The quality of an AI system depends primarily on the data used to train and operate it. - Decisions about what data to collect, exclude, label, and measure determine who the system recognizes and how it behaves. - Data is never purely objective: it is generated, engineered, and transformed by people. - Treating data as disconnected from human lives can produce “traumatized data sets,” embedding social, cultural, and economic harms into models. ## The Consequences of Omission - Historical datasets often exclude entire groups: - U.S. credit and mortgage models were developed before women could independently obtain mortgages or credit cards. - The U.S. Census did not recognize LGBTQ individuals until 2021, despite those people existing in earlier populations. - When people are absent from the data, models may fail to serve them or may expose them to harmful decisions. - The central question is not simply whether data exists, but whether it represents the people affected by the system. ## Define the Problem Before Choosing AI - Teams should first identify the problem they are trying to solve and determine whether ML or AI is appropriate. - The fact that a problem can be addressed with AI does not mean it should be. - Builders should ask: - Who is the product for? - Is the data equitable and sufficiently high quality? - What is the minimum data and technology needed? - Could the proposed solution increase human risks or reduce people to data points? - Minimum viable data means collecting what is necessary for a useful, responsible solution rather than indiscriminately gathering more data. ## Putting People Back in Control - Product builders and the public need to participate in decisions about how AI systems are designed and governed. - Important questions include who defines “good” data, who decides what enters a training set, and how much data is truly required. - Sampson recommends learning from work such as *Weapons of Math Destruction*, *Ghost Work*, and research on the lack of attention given to data work in AI development. AI development should start with the people affected by a system and the data needed to represent them fairly. Choosing the smallest appropriate dataset and validating its quality can be more responsible—and more effective—than pursuing larger models or unnecessary AI features.

AI Machine Learning Generative AI Data Quality+2

figmaJun 25, 20242 min readCurated summary

Meet Figma AI: Empowering Designers with Intelligent Tools | Figma Blog

Figma AI is a suite of tools designed to help designers overcome creative blocks, work faster, and explore ideas more easily. Rather than treating AI as hype, Figma presents it as a practical way to solve common workflow problems, including finding existing designs and components. The features are initially available in a limited beta and are free during 2024, though usage limits and future pricing may change. ## Figma’s Practical Approach to AI - Figma AI builds on the company’s earlier AI features for FigJam. - The tools target several stages of design work: - Finding inspiration and existing assets - Exploring different design directions - Automating repetitive tasks - Generating interfaces from text prompts - Figma emphasizes helping designers remain efficient and creative rather than replacing their judgment. ## Visual Search - Visual Search allows users to find similar designs by: - Uploading an image - Selecting part of a canvas - Entering a text query - Results are drawn from team files the user can access. - Relevant frames can be inserted directly into the current working file. - Figma plans to expand search to Community files, with attribution, links to source files, and access to creators’ other work. ## AI-Enhanced Asset Search - Asset Search now uses semantic understanding rather than relying only on exact keyword matches. - A search such as “primary button” can find a component named `btn_large`. - The system considers the meaning and typical use of design elements, making components in large or complex design systems easier to discover. - The goal is to make finding assets feel more natural and reduce time spent searching through files and libraries. ## Beta Availability and Pricing - Figma AI and UI3 are being rolled out through a limited beta. - Users can join through Figma’s help menu by selecting **“Join UI3 + AI waitlist.”** - Features are free during the beta period, which runs through 2024. - Figma may introduce beta usage limits as it evaluates demand and infrastructure costs. - Pricing for general availability will be announced later. Figma AI is positioned as an assistive layer within the existing design workflow: it helps users locate useful starting points and reduce friction while leaving creative decisions with the designer.

AI Design Systems User Experience Generative AI+2

figmaJun 25, 20242 min readCurated summary

Making Figma Work Better for Freelancers and Agencies | Figma Blog

Figma is revising its billing model to better support freelancers and agencies that work across multiple clients. The company acknowledges that its organization-focused plans create licensing and administrative overhead, and proposes connected workspaces, easier project transfers, and stronger billing controls. These changes aim to make external collaboration easier while reducing unexpected seat charges. ## Connected Workspaces for External Collaboration - Figma is developing connected workspaces that link separate Figma accounts. - Freelancers and agencies will be able to collaborate with clients and co-edit files using their existing seats. - The feature is expected to roll out early the following year, reducing the need for multiple licenses. ## Easier Project Transfers Figma plans to improve transferring work between accounts and plans so freelancers can hand projects to clients with less friction. - Users will be able to transfer a copy while retaining the original. - Collaborators can be removed during transfer to prevent accidental paid-seat upgrades. - Work can be transferred across Professional, Organization, and Enterprise plans. - These improvements went live on August 20. ## More Visibility and Control Over Billing Figma’s browser-based collaboration model lets users begin editing immediately, but it can leave admins responsible for remembering to downgrade seats after a project ends. - Admins can enable daily, weekly, or monthly notifications showing who upgraded and what action caused the upgrade. - New accounts receive these notifications by default: - Weekly on Professional plans - Monthly on Organization and Enterprise plans - Admins can set new users’ default role to “viewer-restricted,” requiring explicit approval before they receive a paid seat. - Figma says broader billing-architecture improvements are still underway. Figma’s immediate tools help admins monitor and approve seat changes, while connected workspaces and improved transfers address the larger structural challenges freelancers and agencies face.

Figma Figjam Collaboration Figma Design+1

figmaJun 25, 20243 min readCurated summary

What Would You Ask If No One Could Judge You? | Figma Blog

Perplexity’s founders envision it as an “answer engine” that turns web-scale information into concise, sourced explanations rather than lists of links. The product grew from a personal need for judgment-free learning and was shaped by the shortcomings of early conversational AI, especially outdated knowledge and hallucinations. Its broader goal is to make curiosity easier to express and pursue. ## Building a Judgment-Free Knowledge Tool - Aravind Srinivas was inspired by childhood “Wikipedia rabbit holes” and the evolution from printed encyclopedias to AI-powered knowledge tools. - Perplexity aims to make learning engaging through curiosity rather than attention-grabbing entertainment. - The company wants users to ask anything without worrying about appearing uninformed or being judged. ## From Private Slackbot to Public Product - The founders initially built a Slackbot to answer practical questions about fundraising, employee health insurance, and running a company. - They hesitated to launch because they feared criticism for attempting to compete with Google. - Investor Nat Friedman encouraged them to view the effort as an asymmetric bet: little downside, but potentially enormous upside. - Perplexity launched shortly after ChatGPT, despite the founders having no previous company-building experience. ## An Answer Engine with Sources - ChatGPT highlighted problems with knowledge cutoffs, hallucinations, and unsupported answers. - Perplexity responded by combining: - Natural-language interaction - Web search and indexing - Large language models - Inline sources and footnotes - Its goal is to provide a direct answer while allowing users to verify the underlying information. - Srinivas describes the product as a combination of Wikipedia and conversational chat, with information drawn from across the internet. ## Making Complex Information Approachable - Perplexity follows an 80/20 approach: identify the most important concepts and deliver most of the useful understanding quickly. - It synthesizes information from multiple web pages into a concise explanation instead of requiring users to read extensively. - The product aims to simplify information without reducing it to misleading or overly shallow conclusions. ## Turning Answers into Further Curiosity - Each response includes three related follow-up questions to encourage exploration. - Srinivas argues that people are naturally curious but often lack the confidence, vocabulary, or precision to formulate good questions. - Perplexity’s design assumes that the user is never wrong; the system should help clarify and develop a person’s curiosity rather than blame them for asking imperfectly. Perplexity’s central recommendation is implicit in its design: make knowledge easier to access, verify, and explore, while removing the social fear that prevents people from asking questions in the first place.

AI Large Language Models Natural Language Processing Conversational Ai+2

figmaJun 17, 20243 min readCurated summary

Navigating the Promise and Pitfalls of AI | Figma blog | Figma Blog

AI’s promise is real, but useful AI products will emerge through experimentation rather than a race to ship features. Figma’s research suggests AI is already transforming individual workflows—especially for developers—while having a smaller effect on collaboration and foundational design work. To deliver lasting value, teams must focus on how AI reshapes products, industries, and group work, not just on model capabilities. ## Research and Methodology - Figma surveyed more than 1,800 designers, executives, and developers. - Participants came from the US, Canada, Australia, the UK, Japan, France, and Germany. - The survey ran from February 26 to March 3, 2024. - The report combines survey findings with discussions involving AI and design experts. - Its central premise is that AI’s impact depends heavily on product design and user experience—not only on the power of large language models. ## AI’s Uneven Transformation of Workflows - Developers were 60% more likely than designers to say AI had transformed the products they work on. - Developers use AI for daily tasks such as generating starting points and translating between programming languages. - AI-generated output is currently perceived as more reliable for developer workflows. - Designers may use AI to turn mockups into code, but much of design’s foundational work still involves: - Understanding user needs - Exploring problems nonlinearly - Learning about the broader problem space - AI initiatives increasingly originate outside design, with programmers, subject-matter experts, and stakeholders contributing ideas. ## AI Must Improve Collaboration, Not Just Individual Productivity - Eighty-five percent of respondents said AI had affected their personal productivity or workflows. - Common uses include text and image generation, brainstorming, and using AI as a sounding board or thought partner. - Respondents were three times more likely to report significant changes to individual workflows than to collaborative ones. - AI has not substantially changed group activities such as alignment or meeting facilitation. - Truly transformational AI products will need to support how teams work together, rather than focusing only on isolated tasks performed by individuals. ## Long-Term Effects Across Industries - Respondents in technology, professional and business services, and retail most often expected significant AI-driven changes to their products and services: - Technology: 41% - Professional and business services: 40% - Retail: 39% - Healthcare, energy and utilities, and telecommunications respondents expected the least impact over the following 12 months. - The report argues that realizing AI’s full potential requires considering how major institutions and essential services—not just software products—will evolve. ## Experimentation Before the Product Race - AI development is still characterized by experimentation, play, and research. - Teams face pressure to release new AI features quickly as new products, applications, and research appear constantly. - The recommended approach is to embrace uncertainty, iterate thoughtfully, and determine which ideas genuinely create value. - As the technology matures, the most successful products will likely come from careful exploration rather than simply adding AI features because of market hype.

AI Large Language Models Machine Learning Generative AI+2

figmaJun 11, 20242 min readCurated summary

The Long and Short of It: Issue no.5 | Figma Blog

Issue no. 5 of Figma’s newsletter, “Come together,” argues that progress depends on community, collaboration, and shared inspiration. Ahead of Config, it highlights creators and leaders whose work shows how connection—whether in person or online—helps turn ideas into reality. The issue spans product development, design quality, creative experimentation, AI, and community events. ## Building tools that feel magical - Charmaine Lee, product manager for Snap’s Lens Studio, shares principles for creating developer tools that delight creators. - Her approach emphasizes hands-on involvement, collaboration, and understanding the creator’s experience rather than following rigid product-building rules. - The feature presents creator-focused product development as an “all-hands-on-deck” effort. ## Craft, beauty, and product quality - Leaders from Stripe, Linear, and Figma discuss how to define and measure craft and beauty in digital products. - Katie Dill, Karri Saarinen, and Yukhi Yamashita explore the relationship between form and function. - Their central argument is that thoughtful design is not merely cosmetic: quality and beauty can contribute directly to product adoption and business growth. ## Designing quilts in Figma - Former product designer Nicole Boettcher uses Figma to plan and design handmade quilts. - Her process demonstrates how digital design tools can support physical, artistic work beyond conventional interface design. - The project playfully extends the idea of “moving rectangles,” connecting her former profession with her current craft. ## AI and creative tools - David Hoang, formerly of Replit, discusses how AI is changing creative tools, product design, and development workflows. - He recommends responding to rapid change through shared learning and strong communities. - Cohorts that combine accountability with fun can help people stay motivated as they develop new skills. ## Config and community opportunities - In-person Config tickets are sold out, but virtual attendance and local watch parties remain available. - Readers can follow the live blog for speaker highlights and event coverage. - The issue also promotes illustrator Thomas Colligan’s artwork, new Config merchandise, and the upcoming Figma Store release. Figma’s overall recommendation is to stay connected: creative progress is strengthened by mentors, collaborators, peers, and communities that make learning and experimentation possible.

Figma AI Product Design Developer Tools+3

figmaJun 10, 20243 min readCurated summary

What’s Happening at Config 2024? | Figma Blog

Config 2024 brought together product builders, designers, artists, and inventors for a conference focused on creativity, technology, and unconventional thinking. Figma’s coverage highlights talks, workshops, community activities, and behind-the-scenes moments from the event. The central message is that meaningful innovation comes from authentic perspectives, outside influences, experimentation, and the freedom to play. ## Conference Community and Programming - Config featured both in-person and virtual programming, including: - “Design of Everything” - New feature recaps - Friends of Figma - Figma EDU - “Figma like the pros” - Daily conference recaps - Attendees came from around the world, supported by speakers, staff, and volunteers. - Figma encouraged viewers to revisit sessions through its YouTube playlist and announced Config APAC for July 2. ## Designing Beyond Expectations - Karla Mickens Cole and Nashilu “Nash” Mouen of The Browser Company discussed designing for a world that resists conformity. - Working on the Arc browser, they argued that products should carry the “fingerprints” of their creators—their experiences, identities, and perspectives. - Nash emphasized that designers should look beyond technology for inspiration, drawing from unexpected sources, stories, and culture. ## AI, Digital Art, and Criticism - Artist Refik Anadol described his digital artwork *Unsupervised*, which uses AI to reinterpret MoMA’s archive. - He framed the project as an exploration of “the possible dreams of the machine.” - Responding to criticism that his work simplifies data, Anadol questioned who the critics are and what perspectives shape their judgments. - His comments reflected the broader challenge of establishing digital and AI-assisted art within the traditional art world. ## Creativity Through Play and Failure - Inventor and YouTuber Simone Giertz presented humorous projects such as a toothbrush-brushing helmet, a slapping alarm clock, a soup-feeding robot, and a drone hair cutter. - After leaving her startup, she found that striving for excellence was not helping and instead gave herself permission to play. - She stressed that difficulty does not necessarily equal importance. - Giertz also discussed overcoming self-deprecation and building a professional identity through her product design company, Yetch. - Her brainstorming exercise—finding unusual uses for a brick—encouraged attendees to embrace strange and creative ideas. - She concluded that creating her own career was her favorite invention. ## Design, Merchandise, and Hands-On Experiences - The conference floor offered opportunities for attendees to connect, explore exhibits, and shop at the Figma Store. - Attendees praised the quirky, distinctive character of the event merchandise. - In the Maker Space, participants customized tote bags with patches and received personalized aura portraits. Config 2024’s activities reinforce a practical creative philosophy: designers should draw from life beyond their field, experiment without fear of failure, and build work that reflects their individual perspectives.

Figma AI User Experience Product Design+2

figmaJun 6, 20242 min readCurated summary

Charmaine Lee’s 10 Rules for Building Developer Tools | Figma Blog

Developer tools feel “magical” not because of polished interfaces, but because they help users quickly become confident creators. Charmaine Lee argues that teams should optimize what happens after the initial “aha moment,” shorten the path to meaningful creation, and build products through close, authentic engagement with developers. ## Prioritize lasting adoption over onboarding - The first-time user experience (FTUE) should not be overloaded with every product capability. - The real measure of success is whether users understand and continue using the product after the initial discovery moment. - Lens Studio 5.0’s public beta omitted a formal FTUE, testing whether the product was intuitive enough to use independently. ## Shorten the path to “magic” - Teams should identify how long it takes users to move from downloading a tool to creating and sharing something valuable. - Lens Studio’s team mapped a 19-step journey from visiting the website to submitting a first project. - By removing unnecessary steps and avoiding guidance for actions users already understood, they reduced the experience to four key moments. - User-journey mapping and testing help reveal which steps create delight, friction, or confusion. ## Meet developers in their communities - Product managers should engage directly with developers at meetups, conferences, hackathons, livestreams, and online communities. - Charmaine monitors AR discussions and attends events to learn developers’ language and gather candid feedback. - Building long-term context from these conversations enables better product decisions and more informed responses to user needs. ## Replace traditional marketing with DevRel - Developers tend to respond poorly to conventional marketing and prefer authentic communication. - Effective developer relations includes: - Real experiences and detailed product-building stories - Transparency about mistakes and limitations - A balance between accessible explanations and technical depth - DevRel should be a company-wide responsibility, not limited to a specialized team. - When employees advocate for both the product and its users, they can foster a more loyal developer community. The excerpt’s central recommendation is to design for users’ sustained progress, not merely their first impression: remove unnecessary friction, understand developers firsthand, and communicate with them honestly.

User Experience Developer Tools Augmented Reality Unity+3

figmaJun 2, 20242 min readCurated summary

Updates to how drafts work | Figma Blog

Figma is moving Drafts for Starter and Professional users into team-associated spaces. The change is intended to clarify ownership, permissions, security, and plan features while keeping drafts private and free to create or edit. Users must eventually move existing drafts into a team, though no immediate deadline applies. ## Why Figma Is Changing Drafts - Drafts previously existed outside teams, creating: - Unclear ownership and team association - Inconsistent behavior across Figma plans - Limited access to paid features such as advanced prototyping, password protection, and Dev Mode - Ambiguous permissions between personal and professional work - Potential security, intellectual-property, and file-loss risks ## New Drafts Structure - Every draft must now belong to a team. - Each team provides members with a private drafts space. - Drafts in Professional teams can use Professional features when edited by eligible users. - Collaborators who are not full team members will be changed from editors to viewers when a draft moves, preventing unexpected paid seats. - Users with one Starter team may have their drafts migrated automatically. ## What Remains the Same - Drafts remain private to their owner and invited collaborators. - Users can create and edit personal drafts for free. - Starter teams can have unlimited viewers and unlimited editors on up to three collaborative files. ## Moving Existing Drafts - Users will find their files in a temporary “Drafts to move” space. - Drafts can be moved into any existing team or into a newly created free Starter team for personal work. - Existing collaborators can continue editing before migration, but new collaborators can only be added after moving a file to a team. - There is no hard deadline yet; unmoved drafts will eventually be transferred to a new free Starter plan after advance notice. ## Future Billing and Collaboration Improvements - Figma plans to make paid editor-seat upgrades clearer. - Planned improvements include better freelancer handoffs, support for users on multiple teams, license management, admin tools, and guest management. - The company is also redesigning its core billing experience. Figma recommends organizing drafts into the appropriate team—or creating a free Starter team for personal projects—to establish clearer separation between professional and personal work.

Figma Prototyping Dev Mode Access Control+2

figmaMay 28, 20243 min readCurated summary

The Linear Method: Opinionated Software | Figma Blog

Linear argues that software should be intentionally designed around a clear use case rather than offering unlimited flexibility. Its defaults reduce process debates and help teams start working quickly, while the company remains willing to evolve its opinions through customer feedback and experimentation. The approach balances strong product principles with deliberate, manageable compromises. ## Opinionated Software as a Default Way of Working - Linear was created by founders with experience at companies such as Airbnb and Coinbase, who wanted an issue-tracking and project-management tool suited to modern product teams. - Unlike general-purpose software, opinionated software guides users toward one effective workflow. - The goal is to prevent the chaos that can emerge when every team or individual invents a different process as an organization scales. - Linear does not insist that its default is the only possible approach, but it makes the recommended path clear. ## Designing at the Atomic Level - Linear favors familiar concepts such as projects, teams, labels, and due dates instead of introducing specialized jargon. - Users should be able to start without reading a handbook or learning an elaborate methodology. - The company is most opinionated about small, foundational decisions—such as treating labels and due dates as issue properties. - For broader structures, such as how projects should work, Linear responds more heavily to customer feedback because organizations differ in how they operate. - The intended result is less time spent configuring processes and more time spent building products. ## Managing Product Debt Deliberately - Linear distinguishes product debt from technical debt: - Technical debt is generally associated with poor or costly code. - Product debt comes from narrowing scope, postponing polish, or optimizing for short-term delivery. - The team treats product debt as borrowing against the future, with “interest” paid through later customer feedback, redesign work, or additional resources. - Settings are an example: Linear has continued adding features and preferences without redesigning the overall experience. - Because settings are not central to the primary workflow, the team considers the accumulated debt relatively low-interest and acceptable to repay gradually. - These shortcuts are framed less as reducing quality and more as intentionally limiting scope. ## Strong Opinions That Can Change - Linear does not treat its principles as a rigid recipe; it expects the product and its processes to evolve. - The team supports experimentation and iteration instead of preserving every decision indefinitely out of fear of user resistance. - Changes that disrupt established workflows require care, but the company believes software must retain the ability to remove or rethink features. - Strong opinions are therefore held firmly enough to guide decisions, but flexibly enough to change when evidence shows a better direction. Linear’s method is most useful when teams want to reduce workflow complexity without eliminating adaptability. Establish clear defaults for common tasks, be deliberate about where flexibility matters, and treat shortcuts as temporary product debt that should be tracked and repaid when its cost becomes significant.

Product Development Project Management Linear Issue Tracking+2

datadogMay 23, 20243 min readCurated summary

How we migrated our static analyzer from Java to Rust

Datadog migrated its static analyzer from Java to Rust after finding that ANTLR-based parsing was too slow and language support was incomplete. Rust’s strong integration with Tree-sitter enabled broader language coverage, faster scans, and lower memory usage. The migration preserved behavioral parity while tripling performance and reducing memory consumption tenfold. ## Why Performance Became a Priority - Datadog runs analysis directly in customers’ CI environments, often on resource-constrained runners. - On a two-core, 7 GB GitHub Actions runner, medium repositories took about five minutes to scan instead of the target of under three minutes. - Codiga’s previous hosted environment used large, tuned servers, which masked some performance problems. - Java also required customers to use JVM 17+, potentially conflicting with JVM versions already installed in their CI environments. - Improving Java offered limited upside, so the team considered a rewrite despite its cost and risk. ## Static Analyzer Architecture - The analyzer consists primarily of: - A parsing layer that builds an abstract syntax tree (AST). - An execution layer that analyzes the AST, reports violations, and offers fixes. - Tree-sitter generates the AST. - The existing Java binding lacked important functionality, including Tree-sitter pattern matching. - Tree-sitter’s core libraries are implemented in Rust, where support was more complete. - Analysis rules are written in JavaScript and were originally executed through GraalVM’s polyglot capabilities. - Fast parsing, pattern matching, and rule execution were central to meeting the desired CI performance. ## Migrating from Java to Rust - Rust was selected because it is a first-class part of the Tree-sitter ecosystem and provided better access to its features. - The migration required: - Feature parity with the Java implementation. - Identical analysis results and reported violations. - No execution-time regressions. - Migrating the parser was relatively straightforward because Rust support came directly from Tree-sitter. - The Rust implementation: - Tripled analyzer performance. - Reduced memory usage by a factor of ten. - JavaScript execution moved from GraalVM to `deno-core`, a Rust-based V8 integration. - Only the core JavaScript functionality was included. - Disk and network capabilities were excluded because analysis rules do not need them, improving security. ## Migration Strategy and Rust Adoption - The team treated automated equivalence and performance tests as requirements for a successful rewrite. - Rust allowed the analyzer to integrate more directly with its key dependencies rather than maintaining a separate Java binding. - The broader migration also required replacing supporting Java components with corresponding Rust libraries; the article indicates that these mappings were documented as part of the transition. Overall, the move to Rust was justified by the analyzer’s deployment model: faster execution and lower resource consumption directly improved the experience of customers running scans in constrained CI environments.

Database Design CI/CD JavaScript Rust+4

datadogMay 23, 20242 min readCurated summary

How we migrated our static analyzer from Java to Rust | Datadog

Datadog migrated its static code analyzer from Java to Rust to improve performance, resource usage, and operational reliability. The rewrite addressed limitations that became increasingly significant as the analyzer processed larger codebases and ran more analyses in parallel. Rather than replacing everything at once, the team preserved existing behavior and introduced the Rust implementation incrementally. ## Why Move from Java to Rust - Static analysis is computationally intensive and often runs across many files simultaneously. - The Java implementation introduced overhead from: - Garbage collection - High memory consumption - Startup and deployment costs - Difficulty achieving predictable performance under heavy workloads - Rust offered: - Native performance - More predictable memory usage - Lightweight binaries - Safe concurrency without a garbage collector ## Preserving Analyzer Behavior - The primary challenge was maintaining compatibility with the existing analyzer and its rules. - The migration had to preserve: - Parsing behavior - Finding locations and diagnostic messages - Rule semantics - Output formats consumed by Datadog’s products and integrations - The team treated the existing implementation as the behavioral reference while rebuilding internal components in Rust. ## Incremental Migration Strategy - Datadog avoided a risky “big bang” rewrite. - Functionality was migrated in stages, allowing the team to: - Compare Java and Rust results - Detect behavioral differences - Benchmark performance - Roll back or isolate problematic changes - Parallel validation helped ensure that improvements in speed did not produce inconsistent security findings. ## Engineering Trade-offs - Rust improved control over memory and execution, but introduced a steeper learning curve and more explicit systems-level design. - The team had to redesign interfaces between components rather than mechanically translate Java code. - Particular attention was required for: - Error handling - Concurrency - Cross-platform builds - Dependency management - Observability and debugging ## Results and Lessons - The Rust implementation provided a stronger foundation for scaling static analysis workloads. - More predictable resource usage makes it easier to run analyses reliably in CI and other automated environments. - The migration demonstrated that large infrastructure rewrites are most manageable when correctness is continuously checked against the existing system. The practical recommendation is to approach similar rewrites incrementally: define compatibility requirements first, compare old and new implementations continuously, and use measured performance and resource data—not language preference alone—to guide the migration.

Kubernetes Datadog Observability Application Performance Monitoring+4