Techlist.io - Korean Tech Blog Curator

figma3 min readCurated summary

Making Space for a Handmade Web | Figma Blog

The web’s early personal, expressive character has been diminished by commercialization, platform standardization, and pressure to optimize for broad audiences. Chia Amisola argues that a “handmade web” still exists in pockets such as Neocities and internet-art communities, and that anyone can support it by making a website without forcing it to serve a conventional purpose. Websites can instead be temporary, obscure, playful, poetic, or collectively imagined spaces. ## From Personal Webpages to Standardized Platforms - In the 1990s, services such as GeoCities gave people small parcels of digital space to build personal webpages. - GeoCities hosted as many as 38 million pages, organized into themed “neighborhoods” and shaped by amateur creativity. - Although the web now contains more sites than ever, efficiency, commercialization, and social media have reduced its visual and expressive variety. - Many people retreat into the internet’s “dark forest,” limiting public self-expression because of judgment, surveillance, or pressure to conform. ## The Handmade Web Still Exists - Neocities continues GeoCities’ legacy by offering free hosting and has grown to nearly one million sites. - Organizations including Rhizome, the Center for Net Art, and the School for Poetic Computation support internet art through exhibitions and workshops. - Decentralized-web initiatives supported by groups such as the Internet Archive promote an internet shaped and owned by its users rather than concentrated platforms. ## Websites as Living, Personal Spaces - Making a website is presented as the most direct way to participate in the handmade web. - A website does not need to be a resume, portfolio, blog, homepage, or comprehensive representation of its creator. - It can be treated as a changing environment that grows over time, rather than a fixed destination. - Personal sites can be short-lived or maintained for decades, focused on one subject or combining many interests, and addressed to a broad community or a single person. ## Websites with Time Limits - Websites can deliberately operate only at particular times or for limited durations. - B&H’s website reflects the closing schedule of its physical stores during religious observances. - “Cloudwatching” and “Stargazing” are accessible only during the day and night, respectively. - Temporary projects such as Internet Stoop and Reddit’s The Button demonstrate how expiration and scarcity can create meaningful online experiences. - Digital spaces are inherently impermanent because domains expire and sites require ongoing maintenance. ## Websites That Resist Discovery - A site can be rewarding precisely because it is difficult to find. - Cassie McQuater’s *Black Room* uses an intentionally illegible URL, while *Default Filename TV* collects videos that retain their original camera-generated filenames. - Obscurity offers an alternative to search-engine optimization, algorithmic distribution, and polished branding. - These sites encourage “surfing” through links and rewarding accidental discovery. ## Websites Without Clear Ownership - Websites can outlive or separate themselves from their original creators, much like abandonware. - Anonymous or ownerless sites can function as fictional tools, alternate realities, or spaces where visitors construct their own meanings. - JODI’s long-running site presents a maze of ASCII landscapes, while the collectively authored SCP Foundation uses a fictional wiki to build a shared mythology. The practical recommendation is simple: make a website without requiring it to be useful, polished, permanent, or widely understood. Its value may lie in being personal, strange, temporary, and shaped by the people who encounter it.

Read original(opens in new tab)
figma2 min readCurated summary

It’s Time We Expand Our Definition of Design | Figma Blog

Figma argues that design should no longer be viewed as the exclusive domain of professional designers. Marketers, developers, product managers, and other collaborators already make visual and communication decisions every day, but often lack the confidence or tools to do so effectively. Expanding access, simplifying workflows, and changing organizational mindsets can help more people participate meaningfully in design. ## Design Tools as Spaces of Belonging - Figma files can feel intimidating to non-designers, much like entering an unfamiliar gallery or professional critique. - Simply inviting someone into a design tool does not guarantee that they will feel comfortable contributing. - Tools can help create belonging by making collaboration more approachable and welcoming. ## Everyday Work Is Design - The author describes repeatedly creating thumbnails, event invitations, and other assets in marketing, product, and sales roles to avoid design bottlenecks. - These activities involve visual communication, creativity, and decisions about how audiences understand and engage with information. - Products such as FigJam, Dev Mode, and Figma Slides are already helping marketers, developers, and other partners work more confidently. - The larger shift requires organizations and individuals to recognize that design participation is not limited by job title. ## Making Design More Inclusive - Teams can support “everyday designers” through: - Templates that provide a reliable starting point. - Simpler, more accessible tools. - Features for staying on brand and finding approved assets. - Assistance with copy exploration and approval workflows. - Organizations should also educate, validate, and celebrate colleagues who want to improve their design skills. - As work becomes faster and more collaborative, these forms of support become increasingly important. Figma’s broader recommendation is to treat design as a shared organizational practice. By giving non-designers better guidance, accessible tools, and permission to contribute, teams can produce stronger work while helping more people feel that they belong in the design process.

Read original(opens in new tab)
figma2 min readCurated summary

The Best Advice to Bring to Work in 2025 | Figma Blog

The article gathers practical workplace advice from leaders at Ableton, Snapchat, Coda, and other companies. Their principles emphasize finding inspiration beyond familiar sources, automating low-value work, shortening users’ path to meaningful results, designing meetings around clear purposes, and maintaining momentum through difficult work. Together, they argue that effective work depends less on rigid formulas than on experience-based judgment. ## Look Beyond Design for Inspiration - Pablo Sánchez of Ableton recommends drawing ideas from emotions, memories, science, nature, and other fields—not just existing design conventions. - Designing for yourself first can produce work with genuine personal energy that resonates with users. - Ableton’s Note app borrowed from Brutalist architecture rather than traditional music software, creating a stripped-down experience focused on immediacy. ## Automate Work That Gets in the Way - Product managers should focus primarily on understanding customers, delivering value, and enabling sound decisions—not perfecting internal artifacts. - When documentation, reviews, or OKRs consume as much time as product development, teams should delegate or automate them. - Peter Yang uses AI to synthesize brainstorms, summarize customer feedback, and improve product requirement documents. ## Accelerate Users’ Time to “Magic” - Products should help new users reach their first meaningful “aha moment” quickly instead of overwhelming them with tutorials. - The goal is to move people from following instructions to confidently creating and sharing something of their own. - Snapchat’s Lens Studio team mapped the user journey and reduced the path from download to first submitted project from 19 steps to four milestones. ## Cultivate Different Types of Meetings - Coda’s Shishir Mehrotra distinguishes three meeting categories: - **Cadence meetings:** Regular staff meetings, standups, and syncs that track progress against goals. - **Catalyst meetings:** Decision-making forums, product reviews, and design critiques that resolve questions and drive change. - **Context meetings:** All-hands meetings, off-sites, and orientations that share information, establish context, and build connections. - Teams need a healthy balance, since too many catalyst meetings can cause burnout. ## Keep Moving Through Difficult Work - Dan Mall compares difficult progress to the tedious parts of training that are usually omitted from an exciting montage. - His advice is to build momentum to counteract the discouragement and monotony that can accompany worthwhile goals. The broader recommendation is to focus attention on meaningful outcomes: use unconventional sources of inspiration, remove unnecessary effort, guide users quickly toward value, give meetings a clear purpose, and keep building momentum when progress feels slow.

Read original(opens in new tab)
datadog2 min readCurated summary

Effective habits of remote workers

Remote workers at predominantly office-based companies must be intentional about staying connected, visible, and effective. The author argues that remote success depends less on physical presence and more on deliberate communication, visible engagement, and strong virtual relationships. Clear updates, responsive availability, and active participation help ensure remote employees remain part of the team. ## Overcommunicate to Compensate for Distance - Share frequent updates about progress, milestones, and blockers instead of waiting for formal meetings. - Ask questions openly, including questions that might feel “dumb”; online messages replace the casual help available in an office. - Respond promptly during working hours and clearly communicate your schedule, especially across time zones. - Keep your calendar accurate by blocking off lunch, appointments, errands, and focused work while leaving room for ad hoc conversations. - Prioritize face-to-face communication during video calls over simultaneous messaging. - Treat writing as your remote “voice”: frequent, clear communication makes your personality and engagement more visible. ## Create a Strong Sense of Presence - Keep your camera on for virtual meetings when appropriate, using reliable audio and video equipment. - Use an intentional background—either an uncluttered workspace or a virtual background that reflects some personality. - Maintain eye contact by positioning your camera properly and staying visually engaged, particularly in one-on-one meetings. - Speak up during meetings, ask questions, and volunteer to summarize notes. - In meetings dominated by office-based participants, be willing to interrupt or talk over others when necessary to contribute meaningfully. - Treat your workspace as part of your professional identity. Show personality intentionally, but avoid relying on artificial blur when a clean wall or thoughtfully arranged background works better. ## Stay Connected Despite Working Remotely - Physical distance does not have to mean disconnection. - Remote employees need to deliberately maintain visibility and presence in virtual spaces. - The excerpt introduces the importance of proactively building relationships, though the discussion ends before that section is completed. Remote workers should compensate for the lack of casual office interaction with consistent communication, visible participation, and intentional relationship-building.

Read original(opens in new tab)
datadogOriginal article

Effective habits of remote workers | Datadog (opens in new tab)

Cody Lee argues that remote workers in office-centric companies must intentionally project visibility and over-communicate to remain effective. By treating digital interactions with the same gravity as physical ones, remote employees can bridge the gap with their office-based colleagues and maintain strong professional relationships. The guide concludes that long-term success depends on the intentionality of one's "digital voice" and the strategic use of periodic in-person visits. ## Prioritizing Communication to Overcome Distance * Over-communicate progress and blockers frequently to ensure teammates are aware of your status without needing to ask. * Ask "dumb" questions openly in collaboration tools to stay engaged and leverage the collective knowledge of the team. * Maintain high availability by keeping an updated calendar with visible blocks for lunch and focus time, mimicking the accessibility of an office setting. * Prioritize face-to-face video communication over asynchronous messaging when active discussions are taking place. ## Embodying Digital Presence * Always keep the camera on during virtual meetings to convey body language and build a higher level of trust. * Maintain "eye contact" by looking at the camera rather than secondary screens and speak up during meetings to remain an active participant. * Be prepared to interrupt politely in hybrid meetings where office-based participants may dominate the conversation. * Avoid the "blur" effect on backgrounds in favor of a clean, unblurred workspace or a virtual background that reflects your personality. ## Proactive Relationship Building * Schedule recurring virtual coffee chats with colleagues across the organization to build rapport beyond immediate work tasks. * Participate in non-work-related messaging threads and volunteer for team-building initiatives to become more than just a name on a screen. * When visiting the office—ideally once per quarter—prioritize casual interactions, such as morning coffees and team dinners, over routine administrative tasks. * Clear your schedule of non-critical remote meetings during in-person visits to leave room for spontaneous "hallway track" conversations. ## Balancing Visibility and Communication Fatigue * Establish a consistent communication rhythm that provides meaningful updates without becoming overwhelming or irritating to colleagues. * Tailor your outreach methods by consulting teammates’ "How to work with me" documents to respect their individual communication preferences. * Focus on clarity and brevity in written text, as your writing effectively becomes your "voice" in a remote environment. Succeeding as a remote worker requires a shift from passive participation to active, intentional engagement. By treating digital communication as a primary tool for presence and prioritizing periodic in-person connection, you can ensure your contributions remain visible and your professional relationships remain strong.

figma2 min readCurated summary

27 FigJam Activities to Spark Creativity in the Classroom | Figma Blog

FigJam’s collaborative canvas can make classroom participation more inclusive, creative, and engaging across subjects. The post presents 27 adaptable activities that use sticky notes, drawings, widgets, and shared templates to support community-building, discussion, problem-solving, creative breaks, and assessment. Its central conclusion is that familiar teaching activities become more interactive when students can contribute visually and collaboratively. ## Building Classroom Community - Icebreakers help students share interests, personalities, hobbies, dreams, and favorite subjects. - “Let me introduce myself” activities use sticky notes, stickers, and sketches. - Scavenger hunts prompt students to find classmates with shared experiences or interests. - A virtual “shoe rack” lets students express their individuality creatively. - FigJam tools such as drawing, voice recordings, and photobooths give students multiple ways to participate and connect. ## Making Language and History Come Alive - Shared canvases turn reading and historical analysis into group activities rather than isolated assignments. - Students can visualize character relationships, track plot developments, and discuss themes together. - Templates such as book chats support collaborative literary discussion. - History activities can encourage students to debate perspectives and investigate events collectively. ## Visualizing STEM Concepts - FigJam activities help students represent abstract scientific, mathematical, and technical ideas visually. - Collaborative diagrams, notes, and sketches can support group problem-solving. - The flexible canvas allows teachers to adapt activities for different subjects and grade levels. ## Taking Creative Brain Breaks - Short, playful FigJam exercises can reenergize students between lessons. - Drawing, visual prompts, and collaborative challenges provide a creative change of pace. - These breaks maintain engagement while still encouraging communication and imagination. ## Checking Understanding Together - Teachers can use shared templates to see how students are processing a lesson. - Students can contribute answers, questions, reflections, and visual explanations in one collaborative space. - Group responses make misconceptions easier to identify and create opportunities for peer discussion. Overall, the post recommends using FigJam as a flexible classroom workspace rather than limiting it to presentations. Its free education access and adaptable templates make it suitable for teachers who want more inclusive, participatory learning activities.

Read original(opens in new tab)
microsoft3 min readCurated summary

Dev Box Ready-To-Code Dev Box images template

Microsoft announced Team customizations and imaging for Microsoft Dev Box to make development environments faster to create, more consistent, and easier to maintain. The feature builds on Microsoft’s internal One Engineering System (1ES) “ready to code” environments, already used by more than 35,000 developers. Its central approach is to use reusable templates, automated image builds, and centrally managed improvements to reduce setup time and eliminate environment inconsistencies. ## The Challenge of Large-Scale Development Environments - Large teams often work with enormous repositories, proprietary or legacy tools, and slow build processes. - Many setup steps are shared across teams, but creating and maintaining reusable customizations requires significant effort. - Teams also need flexibility for unique requirements without duplicating large amounts of configuration. - The 1ES approach addresses this through reusable templates with conditional logic and shared modules. ## How 1ES Ready-to-Code Environments Work - Templates define common environment requirements while allowing teams to customize: - Repositories to clone - Build configurations - Default tools - Additional setup tasks - Image artifacts, implemented as scripts or CI/CD tasks, install and configure environment components. - Azure Managed Identity provides secure access to required repositories and assets. - Azure Bicep modules hide template complexity while allowing reusable infrastructure definitions. - Azure Pipelines manage image creation and refreshes, making troubleshooting familiar to Microsoft developers. ## Benefits of Team Customizations - **Security:** Images use Managed Identity, approved sources, and validated artifacts. - **Performance:** Dev Drive and security settings are preconfigured for development workloads. - **Consistency:** Smart defaults reduce configuration differences and “works on my machine” problems. - **Flexibility:** Teams can tailor repositories, tools, builds, and other customizations. - **Maintainability:** Shared Bicep modules allow central teams to deliver improvements broadly. - **Easy updates:** Automated Azure Pipelines simplify image refreshes and maintenance. ## Testing and Controlled Releases - 1ES creates hundreds of Ready-to-Code images for Microsoft teams. - Template pull requests are tested with a small set of images covering core features. - Before each template release, larger test runs simulate real customer image definitions. - Releases are phased through internal dogfooding before wider deployment. - Bicep Module Registry tags distinguish release phases and support targeted hotfixes. ## Community Sample Template Microsoft is sharing a simplified version of its internal approach using Azure Image Builder. The sample demonstrates how to create Ready-to-Code images for open-source repositories such as MSBuildSdks, eShop, and Axios. Key components include: - `README.md` with setup instructions - Bicep image definitions for different repository types - `devbox-image` as the main reusable module - `build_images.yml` for Azure DevOps image builds - PowerShell artifacts for image configuration ## Capabilities of the Sample - Clones repositories, restores packages, builds projects, and creates shortcuts. - Supports MSBuild and .NET projects with automatic SDK installation. - Configures repository and artifact authentication through Managed Identity. - Sets up Dev Drive automatically. - Uses a Visual Studio-based Azure Marketplace image by default. - Installs tools such as VS Code, Visual Studio extensions, Git, Sysinternals, WinGet, and the Azure Artifacts Credential Provider. - Applies developer-focused Windows and Defender settings. - Supports image chaining, Compute Gallery publishing, and configurable build VM sizing. The recommended approach is to adopt a reusable, templated image definition rather than maintaining one-off setup scripts. Teams can start with Microsoft’s sample and extend it for their repositories, while Team customizations evolves toward bringing the 1ES capabilities directly into Microsoft Dev Box.

Read original(opens in new tab)
figma2 min readCurated summary

Updates to our pricing, seats, and billing experience | Figma Blog

Figma announced changes to pricing, seat types, and billing workflows taking effect March 11, 2025. The company is raising prices for Figma Design, consolidating seat management, and giving administrators advance approval over paid seat upgrades. The changes are intended to improve billing visibility while allowing users temporary access during approval. ## New Pricing and Seat Structure - Figma Design prices will increase, with changes applying to Full seats. - Existing plans will transition to four seat types: - Full - Dev - Collab - View - Paid seats will include access to FigJam and Figma Slides. - The free Starter plan will remain available. ## Admin Approval for Seat Upgrades - Previously, users could trigger seat upgrades and admins reviewed them afterward. - Under the new model, paid seat upgrades will require admin approval by default. - Admins will manage one seat per user rather than separate seats for each product. - Users can temporarily access the requested seat for up to three days while approval is pending. - During this period, they can create files and edit files where collaborators have granted edit access. - Approved seats will appear on the next invoice, prorated from the approval date through the end of the subscription period. ## Migration and Timing - Existing plans will migrate to the new seat structure and approval workflows beginning March 11, 2025. - Full-seat price increases and updated proration rules will apply at the first renewal on or after that date. - Figma says existing customers will receive additional details by email. ## Connected Projects for Freelancers and Agencies - The billing changes prepare the way for Connected Projects, planned for later in 2025. - Freelancers and agencies will be able to collaborate with clients using their existing seats. - This is intended to eliminate the need to purchase licenses across multiple plans for client collaboration. Organizations should review their seat assignments and establish an approval process before the March 2025 migration.

Read original(opens in new tab)
figma2 min readCurated summary

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

Figma’s Issue No. 8 reflects on how its community shaped the company’s 2024 releases and culture. The year included 180 product updates, a major Config conference, expanded tools for developers and product teams, and a refreshed brand identity. The central message is that Figma builds products through continuous dialogue with the people who use them. ## A Year Shaped by the Community - Figma published 180 new releases in 2024. - More than 10,000 people attended Config. - Over 220 Friends of Figma groups operated worldwide. - The company emphasizes that users do more than receive new features: they influence how those features evolve in practice. ## Expanding Figma’s Products - Figma refined its UI3 interface to give users more control. - AI tools were reworked with a more deliberate approach. - Dev Mode was enhanced to improve connections between design and code. - Figma Slides was launched to support presentations and give design work a broader stage. - The company highlights that the design process continues after launch, when users apply new tools to real workflows. ## Config and the Future of Product Building - Config 2024 was Figma’s largest conference yet, held in San Francisco with more than 10,000 attendees. - Figma points readers toward talks and advice from Config speakers. - Featured guidance focuses on creating memorable presentations and sessions that genuinely inspire audiences. - Early-bird tickets for Config 2025 were already available. ## A New Brand and Web System - As Figma expanded toward developers, marketers, and broader product teams, it updated its visual identity. - The redesign introduced a new typeface and a refreshed brand system. - Figma used its own tools to audit and rebuild its web system. - The process included streamlining components, improving workflows, refining variables and styles, and preparing the system for future growth. ## Design Inspiration and Cross-Functional Collaboration - Community templates for Figma Slides offer ways to create more engaging presentations. - Ableton Note designer Pablo Sánchez shares seven principles for designing surprising and memorable digital experiences. - One North’s Nick Villapiano argues that developers should participate actively in design rather than treating design as a handoff. - These examples reinforce Figma’s broader view that design is collaborative and extends across disciplines. Figma’s year-end message is ultimately a recommendation to keep building in conversation with users. Product launches, brand systems, developer workflows, and community events become more valuable when people actively shape how they are used.

Read original(opens in new tab)
figma4 min readCurated summary

Figma 2024: We shipped it, you shaped it | Figma Blog

Figma’s 2024 product work was driven by community feedback, spanning 180 releases, UI3, AI tools, performance improvements, and new workflows for moving from concept to delivery. The company’s central conclusion is that meaningful progress comes from reducing friction while preserving designers’ existing habits. Community input shaped both major launches and small refinements across Figma, FigJam, and Figma Slides. ## UI3: Putting the Work Front and Center - Figma redesigned its interface for the first time substantially since 2019, updating typography, layout, colors, icons, labeling, and panel behavior. - Early UI3 testing revealed that floating panels disrupted users’ speed and daily workflows. - Based on feedback, panels became docked and resizable, while users could hide panels to maximize canvas space. - The eyedropper was upgraded to reuse styles and variables, switch between color formats, and create new styles or variables. ## Improving Core Design Workflows - Multi-edit simplified making changes across multiple designs. - Typography improvements added support for italic, bold, underline, underline styling, mixed paragraph spacing, and better local-font detection. - File organization improved through pinning, enhanced search filters, page dividers, and split tabs. - Drafts, content transfers, and file-moving workflows became easier for teams working across organizations. - “Suggest Auto Layout” helped users make designs more responsive. - Figma also introduced playful retro cursors inspired by DOS, Y2K, skeuomorphism, and Windows Vista. ## Performance, Collaboration, and Administration - Dynamic page loading made large design files more manageable. - Memory optimization and a revamped memory-management system improved performance in large files. - Multiplayer collaboration became smoother and more reliable. - Admin tools received new sidebar navigation and a dedicated content-management tab. - Infrastructure improvements included EU-localized file hosting, better support for large asset libraries, and stronger Enterprise security controls. ## AI Features That Reduce Friction - Visual search lets users find designs by uploading an image or selecting part of the canvas. - Asset search understands context instead of relying only on exact component names. - AI-assisted layer renaming improves file organization. - Replace Text Content generates realistic copy, while Rewrite, Translate, and Shorten help revise text. - Make an Image enables image creation and editing directly on the canvas, and Remove Background isolates subjects without requiring another tool. - FigJam’s AI mindmaps became a popular way to explore ideas and visualize connections. - Figma AI can turn a FigJam board into a Figma Slides outline and generate presenter notes. - First Draft, formerly Make Designs, was redesigned to help users move from an idea to an initial design. It was in limited beta, with planned support for custom libraries and deeper integration with existing design systems. ## Moving from Work in Progress to Shipping - Figma continued expanding tools intended to connect design work with development and presentation. - Dev Mode and Code Connect aimed to reduce developer context switching by translating design components into code. - Figma Slides supported creating high-fidelity presentations, extending Figma’s workflow beyond interface design. - The broader goal was to help teams move more smoothly from early concepts to implementation and delivery. ## Community-Led Product Development - Figma reported 10,000 Config attendees and more than 220 Friends of Figma groups worldwide. - Product decisions were shaped through beta testing, user conversations, and feedback from individual designers and organizations. - The company emphasized thoughtful AI development: AI should help express ideas and remove tedious work without replacing designers’ judgment. - Community members influenced both flagship features such as UI3 and First Draft and smaller quality-of-life improvements. Figma’s 2024 updates show a strategy focused on practical acceleration rather than novelty alone: improve the fundamentals, apply AI where it removes real friction, and build stronger bridges between design, development, and presentation. For teams, the most valuable improvements are likely the cumulative ones—better organization, faster search, stronger performance, and workflows shaped directly by how people already work.

Read original(opens in new tab)
figma3 min readCurated summary

Pablo Sánchez’s 7 Rules for Designing the Unexpected | Figma Blog

Pablo Sánchez argues that memorable digital products come from personal conviction, unexpected sources of inspiration, and a willingness to imagine alternatives to the present. His work on Ableton Note demonstrates this approach: instead of reproducing conventional music-production tools, the app emphasizes tactile, immediate experimentation through features like “Capture,” which loops phrases after they are played. ## Design for Yourself - Strong design begins with personal conviction rather than detached objectivity. - Designers should create something that inspires them, since personal enthusiasm can make the final product feel authentic. - For Ableton Note, Sánchez replaced an expected MIDI editor with directly playable instruments suited to mobile interaction. - User testing later validated the direction, and the app launched without a MIDI editor. - Note lets users tap rhythms on a 16-pad grid, play melodies and chords, and develop variations in Session View. ## Brainstorm Without References - Starting with existing design references can lock a team into familiar solutions. - Brainstorming without references encourages ideas drawn from personal experience and absorbed cultural influences. - Sánchez describes this process as creating an “assemblage” from the collective ideas designers carry with them. - Although Note’s influences were not copied directly, apps such as Samplr and Borderlands Granular contributed to its creative foundation. ## Look Beyond Design - Inspiration can come from literature, dance, nature, science, emotions, and personal memories—not only other interfaces. - Sánchez wanted Note to feel as immediate as picking up a guitar and experimenting. - He also drew from Brutalist architecture, particularly its emphasis on materiality, simplicity, and the removal of unnecessary ornament. - This led to a minimal interface that reduces the complexity of music production and lets users interact directly with sound. - Note includes features such as a microphone-based sampler and a visual sound interface. ## Design for Tomorrow - Sánchez distinguishes between: - **Affirmative design**, which solves existing problems and reinforces the current world. - **Critical design**, which questions current conditions and explores how the world could be different. - Unexpected design combines both approaches by imagining new possibilities while encouraging people to investigate them. - Designers are encouraged to speculate beyond present assumptions rather than simply repeating familiar patterns. - The article invokes xenofeminist thinking—“If nature is unjust, change nature!”—as an example of challenging supposedly fixed conditions. The excerpt presents unexpected design as a practice of trusting personal intuition, combining diverse influences, and designing toward possibilities that do not yet exist. Ableton Note illustrates how a focused, unconventional vision can produce a more playful and distinctive experience than simply implementing expected features.

Read original(opens in new tab)
figma3 min readCurated summary

The Making of the Figma Pattern Library | Figma Blog

Figma rebuilt its internal design system during the UI3 redesign after years of growth had produced inconsistent components, detached instances, and a fragmented workflow. The resulting Figma Pattern Library (FPL) was created through close designer-engineer collaboration and uses variables, APIs, and shared standards to keep design intent aligned with shipped code. Its goal is to provide both a reliable source of truth and a flexible foundation for building consistent, accessible products across Figma’s product suite. ## Why Figma rebuilt its design system - Figma’s internal system had become increasingly fragmented as the company and product portfolio expanded. - Components that were intended to be identical had accumulated subtle but important differences. - Detached component instances made consistency difficult to maintain. - The upcoming UI3 rollout made these problems impossible to ignore. - The team needed a foundation that could support consistent, efficient development across all Figma products. ## A paired design-and-engineering approach - A five-person team of designers and engineers led the rebuild. - The team modeled its workflow on pair programming: - One discipline would actively build. - The other would review and provide immediate feedback. - This collaboration helped bridge the gap between design intent and technical implementation. - The system was designed to be both: - A source of truth for shared UI decisions. - A springboard for future product development. - The effort resulted in the new Figma Pattern Library, or FPL. ## Using variables as a shared language - The previous system relied on Figma styles for designers and a separate Google Sheet for engineers’ color tokens. - Because the spreadsheet often lagged behind product changes, designs and production code diverged. - FPL replaced this disconnected process with Figma variables and the Figma REST API. - Typography variables were introduced and aliased through existing typography styles. - Color styles were migrated to color variables as a centralized source of truth. - CSS definitions were added to color variables so Dev Mode could display the correct variable names during inspection. ## Primitive and semantic color systems - FPL organized colors into two main variable collections: - **Primitive variables:** Color ramps organized by hue and numbered from 100 to 1000. - **Semantic variables:** Contextual names based on Figma’s dark-mode schema. - Semantic variables support multiple themes and products, including: - Light and dark modes. - Figma Design. - FigJam. - Slides. - Dev Mode. - Semantic variables alias primitive variables, allowing colors to be changed across themes and products without manually updating every component. - This structure enables shared components to adapt to different contexts while preserving visual consistency. The practical lesson is that a scalable design system requires more than a component library: it needs shared ownership, synchronized design and engineering tokens, and variable-based foundations that can support multiple products and themes.

Read original(opens in new tab)
datadog1 min readCurated summary

How we use formal modeling, lightweight simulations, and chaos testing to design reliable distributed systems | Datadog

The provided content does not include the blog post itself. It contains Datadog’s navigation menu and a link titled “Formal Modeling and Simulation,” but no article text or technical explanation to summarize. ## Available Information - Datadog promotes its observability platform across: - Infrastructure and application monitoring - Logs, databases, and data pipelines - Security - Digital experience monitoring - Software delivery and service management - AI-powered observability - The page also advertises Datadog’s recognition as a Leader in the Gartner Magic Quadrant for Observability Platforms. - The linked engineering article appears to concern formal modeling and simulation, but its subject, methods, and conclusions are not included. ## Conclusion Please provide the blog post’s full text or the relevant article content to receive an accurate technical summary.

Read original(opens in new tab)
datadog3 min readCurated summary

How we use formal modeling, lightweight simulations, and chaos testing to design reliable distributed systems

Courier’s design illustrates why distributed systems need more than unit, integration, and chaos testing. Datadog combined formal modeling, lightweight simulation, and conventional testing to uncover system-level risks before implementation. The approach was especially important after the March 8, 2023 outage, which showed how locally reasonable decisions can produce severe global failures. ## Why Distributed Systems Require Additional Analysis - Distributed systems provide greater scale and availability, but introduce concurrency, coordination, and failure modes that are difficult to reason about intuitively. - Traditional tests operate at relatively low levels of detail and may miss high-level design flaws. - Formal models and simulations allow teams to evaluate system behavior during the design phase, before implementation choices become expensive to change. - Model checking exhaustively explores all states permitted by a design and verifies defined correctness properties. ## Formal Modeling and Lightweight Simulation - Formal modeling uses a high-level specification language to describe: - System components and their interactions - Allowed system states - Properties the system must satisfy - Lightweight simulation builds a replica that runs under controlled conditions to study statistical characteristics such as: - Latency - Cost - Scalability - Behavior under realistic workloads - Modeling verifies correctness but cannot fully assess performance-related concerns. - Neither technique validates the final implementation directly. - Keeping models and simulations synchronized with the production design adds maintenance overhead. - Datadog considered the additional effort worthwhile because Courier was foundational, needed strong reliability guarantees, and incorporated lessons from the 2023 outage. ## Courier’s Requirements Courier was created to replace a decade-old Redis-backed queuing system that had begun to face throughput, scaling, and durability limitations. Its main requirements were: - **Multi-tenancy:** Isolate teams and products so one tenant cannot significantly disrupt others. - **At-least-once delivery:** Messages must not be lost; they must be delivered and acknowledged or sent to a dead-letter queue. - **Graceful degradation and high availability:** Throughput should decline roughly linearly as compute capacity is lost, rather than collapsing entirely. - **Horizontal scalability:** Throughput should increase linearly as compute capacity is added. The graceful-degradation requirement directly addressed the March 8 outage, when lost compute capacity caused a disproportionate throughput failure. ## FoundationDB Sharding for Tenant Isolation - Courier uses multiple FoundationDB clusters. - Each tenant is assigned to a subset of clusters. - No two tenants share the exact same cluster subset. - The initial design used: - Eight FoundationDB clusters - Four clusters per tenant - A theoretical maximum of `8 choose 4 = 70` tenant assignments - If one tenant saturated or disabled its four clusters, other tenants would still retain access to at least 25% of the total cluster capacity. - This arrangement provided sufficient isolation for the intended workloads. ## Broker Layer and High Availability - A broker layer exposes gRPC APIs for: - Sending messages - Receiving messages - Deleting messages - Clients connect only to the brokers, which apply the tenant-sharding logic. - Brokers health-check FoundationDB clusters and remove unhealthy clusters from consideration. - Both brokers and FoundationDB clusters are deployed across three availability zones to improve resilience. Courier demonstrates that formal verification and simulation are valuable complements to implementation testing. For mission-critical distributed services, teams should validate both correctness and operational behavior early, while also using unit, integration, and chaos testing to verify the final system.

Read original(opens in new tab)
figma2 min readCurated summary

Why Devs Should Play an Active Role in Design | Figma Blog

Developers should participate actively in design rather than treating design files as read-only specifications. Nicholas Villapiano argues that Figma’s Dev Mode reduces friction, improves confidence, and creates a shared workflow between designers and developers. Teams should advocate for these tools because they understand day-to-day collaboration problems better than management often does. ## Shared Tools Create a Common Language - Dev Mode gives developers a dedicated space within Figma instead of forcing them to work cautiously in designer-oriented files. - It treats developers as contributors to the product process, not merely implementers of finished designs. - Figma’s Auto Layout offered an early example of shared understanding by resembling CSS Flexbox and making designs behave more like responsive web layouts. - Dev Mode extends that connection into a broader framework for collaboration between design and engineering. ## Developers Should Advocate for Better Workflows - Managers may not see the practical pain points developers encounter when translating designs into code. - Developers already advocate for change through GitHub issues, pull requests, and technical discussions, so they should apply the same behavior to design and collaboration tools. - Useful opportunities to raise these needs include one-on-ones, sprint retrospectives, and team meetings. ## Exploring Designs Without Fear - Dev Mode is read-only by default, preventing accidental edits or deleted work. - This works much like branch protection on `main`: developers can investigate freely without risking the source file. - Greater confidence encourages developers to explore designs instead of avoiding or cautiously navigating them. ## Comparing Design Changes Clearly - Dev Mode provides version history and visual comparisons similar to Git commit history and pull requests. - Developers can see what changed, when it changed, and who made the change. - Differences become an actionable checklist, such as updating copy, adjusting margins, or adding a component variant. ## Reducing Context Switching - Developers often lose time switching between design files, documentation, and code. - Dev Mode and related tools such as Code Connect aim to bring implementation details closer to the design workflow. - Centralizing relevant information can reduce the “tab-switching tax” and make design-to-code work more efficient. ## Practical Recommendation Developers should actively evaluate and promote shared design-development tools like Dev Mode. By creating safer exploration, clearer change tracking, and a common language around implementation, teams can improve productivity, collaboration, and morale.

Read original(opens in new tab)