Automation

43 posts

kakaoOriginal article

[AI_TOP_10 (opens in new tab)

The AI TOP 100 contest was designed to shift the focus from evaluating AI model performance to measuring human proficiency in solving real-world problems through AI collaboration. By prioritizing the "problem-solving process" over mere final output, the organizers sought to identify individuals who can define clear goals and navigate the technical limitations of current AI tools. The conclusion of this initiative suggests that true AI literacy is defined by the ability to maintain a "human-in-the-loop" workflow where human intuition guides AI execution and verification. ### Core Philosophy of Human-AI Collaboration * **Human-in-the-Loop:** The contest emphasizes a cycle of human analysis, AI problem-solving, and human verification. This ensures that the human remains the "pilot" who directs the AI engine and takes responsibility for the quality of the result. * **Strategic Intervention:** Participants were encouraged to provide AI with structural context it might struggle to perceive (like complex table relationships) and to perform data pre-processing to improve AI accuracy. * **Task Delegation:** For complex iterative tasks, such as generating images for a montage, solvers were expected to build automated pipelines using AI agents to handle repetitive feedback loops while focusing human effort on higher-level strategy. ### Designing Against "One-Shot" Solutions * **Low Barrier, High Ceiling:** Problems were designed to be intuitive enough for anyone to understand but complex enough to prevent "one-shot" solutions (the "click-and-solve" trap). * **Targeting Technical Weaknesses:** Organizers intentionally embedded technical hurdles that current LLMs struggle with, forcing participants to demonstrate how they bridge the gap between AI limitations and a correct answer. * **The Difficulty Ladder:** To account for varying domain expertise (e.g., OCR experience), problems utilized a multi-part structure. This included "Easy" starting questions to build momentum and "Medium" hint questions that guided participants toward solving the more difficult "Killer" components. ### The 4-Pattern Problem Framework * **P1 - Insight (Analysis & Definition):** Identifying meaningful opportunities or problems within complex, unstructured data. * **P2 - Action (Implementation & Automation):** Developing functional code or workflows to execute a defined solution. * **P3 - Persuasion (Strategy & Creativity):** Generating logical and creative content to communicate technical solutions to non-technical stakeholders. * **P4 - Decision (Optimization):** Making optimal choices and simulations to maximize goals under specific constraints. ### Quality Assurance and Score Calibration * **4-Stage Pipeline:** Problems moved from Ideation to Drafting (testing for one-shot immunity), then to Candidate (analyzing abuse vulnerabilities), and finally to a Final selection based on difficulty balance. * **Cross-Model Validation:** Internal and alpha testers solved problems using various models including Claude, GPT, and Gemini to ensure that no single tool could bypass the intended human-led process. * **Effort-Based Scoring:** Instead of uniform points, scores were calibrated based on the "effort cost" and human competency required to solve them. This resulted in varying total points per problem to better reflect the true difficulty of the task. In the era of rapidly evolving AI, the ability to "use" a tool is becoming less valuable than the ability to "collaborate" with it. This shift requires a move toward building automated pipelines and utilizing a "difficulty ladder" approach to tackle complex, multi-stage problems that AI cannot yet solve in a single iteration.

figma2 min readCurated summary

ServiceNow and Figma Launch Strategic Collaboration to Turn Design Vision Into Enterprise Transformation | Figma Blog

ServiceNow and Figma have launched an MCP-powered integration that turns Figma designs directly into enterprise applications. By using a Figma design link as a prompt for ServiceNow’s Build Agent, teams can automate the transition from visual concept to secure, scalable software. The collaboration aims to combine Figma’s design context with ServiceNow’s AI workflows, governance, and platform intelligence. ## From Design to Enterprise Application - Developers can provide a Figma design link directly to the ServiceNow integrated development environment. - ServiceNow’s Build Agent interprets layouts, components, styles, and other design details. - The agent generates a functional enterprise application rather than merely reproducing an image. - The process is intended to reduce manual coding, improve consistency, and accelerate development from minutes-long design-to-build workflows. ## Powered by Figma’s MCP Server - Figma’s Model Context Protocol (MCP) server gives ServiceNow structured design context. - This deeper understanding supports higher-fidelity translations of designs into working applications. - The integration connects design intent with production code, helping designers, product builders, and professional developers collaborate more effectively. ## Security and Governance - The integration uses OAuth 2.0 authentication and secure server-to-server communication. - Access tokens are stored within the customer’s ServiceNow instance to support privacy and compliance. - Applications created through Build Agent inherit ServiceNow capabilities such as permissions, audit trails, version control, and enterprise governance. ## Availability and Broader Impact - The integration is available in the latest ServiceNow Build Agent release through the ServiceNow Store. - Customers must request access after installation. - ServiceNow and Figma position the collaboration as a way to deliver AI-powered experiences faster while preserving human-centered design and enterprise-scale reliability. - Figma’s CTO emphasizes that design quality will remain a key differentiator as AI-generated software becomes more common. Organizations using both platforms can now shorten the path from prototype to production while maintaining security, governance, and design fidelity. The integration is especially suited to teams that want to accelerate enterprise application development without losing the original design intent.

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

Enhancing Code Quality at Scale with AI-Powered Code Reviews

Microsoft developed an AI-powered pull request reviewer to reduce routine review work, catch defects earlier, and help developers merge code faster. What began as an internal experiment now supports more than 90% of Microsoft’s PRs—over 600,000 per month—and has influenced GitHub’s Copilot for Pull Request Reviews. The central lesson is that AI works best as a human-in-the-loop assistant embedded directly into existing workflows. ## Addressing PR Review Bottlenecks - Human reviewers often spend time on style issues and minor bugs while overlooking architectural or security concerns. - Large, multi-file PRs can lack sufficient context and may wait days or weeks for review. - The AI reviewer automatically joins new PRs and handles repetitive or easily missed checks, allowing humans to focus on higher-level decisions. ## AI-Powered Review Features - **Automated comments:** Flags issues such as missing null checks, error-handling problems, sensitive-data risks, inefficient algorithms, and style inconsistencies. - **Suggested fixes:** Provides corrected snippets or alternative implementations, but authors must explicitly review and apply changes. AI does not commit changes automatically. - **PR summaries:** Generates descriptions of the change and highlights key modifications across the diff. - **Interactive Q&A:** Reviewers can ask questions about parameters, code behavior, or the impact on other modules directly in the PR discussion. - **Workflow integration:** The assistant behaves like a normal reviewer, requiring no separate tools or interfaces and optionally engaging as soon as a PR is opened. ## Effects on Quality and Development Speed - AI-assisted reviews reduced median PR completion times by 10–20% in early studies across 5,000 repositories. - Early feedback reduces waiting time, back-and-forth cycles, and the chance that minor issues delay approval. - The system has identified bugs such as missing null checks and incorrectly ordered API calls before they reached production. - Developers, particularly new hires, can use the explanations as continuous guidance on coding standards and best practices. ## Team-Specific Customization - Teams can configure repository-specific review guidelines. - Custom prompts support specialized checks, including regression detection based on historical crash patterns and validation of deployment or change gates. - This extensibility allows the reviewer to address concerns beyond generic code quality rules. ## Feedback Between Internal and External Products - Microsoft’s internal deployment provided early feedback on review quality, usability, and developer trust. - Internal experiments helped shape features such as inline suggestions and human-controlled change application. - These lessons contributed to GitHub Copilot for Pull Request Reviews, which reached general availability in April 2025. - Microsoft also uses learnings from GitHub’s broader external adoption to improve its internal development practices, creating an ongoing feedback loop between first-party and third-party products. Overall, the post recommends treating AI review as an always-available first pass—not a replacement for human judgment. Its greatest value comes from seamless integration, strong customization, and keeping authors and reviewers accountable for final decisions.

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

Double Click: Does Efficiency Kill Love? | Figma Blog

Config 2025 framed AI less as a tool for maximizing efficiency and more as a way to deepen connection, care, and creative purpose. The article contrasts the slogan “Efficiency kills love” with the idea that “Design is chasing a feeling,” arguing that craft and intentionality should remain central as technology accelerates. AI’s role, therefore, depends on the values people choose to embed in it. ## From Efficiency to Care - Figma’s community expressed renewed enthusiasm for craft, emotion, and meaningful creative work. - Smith & Diction’s presentation, “The Wild West of Collaborative Brand Design,” captured the mood with the declaration that “Efficiency kills love.” - Figma CEO Dylan Field’s keynote offered a complementary idea: “Design is chasing a feeling.” - Together, these statements suggest a shift away from treating productivity and speed as the sole measures of successful design. ## Craft as the Conduit - Yang You, Head of Design at Paradigm, summarized the emerging attitude: “Craft is king, and care is the conduit.” - Designers are looking beyond target metrics and faster workflows toward: - Storytelling - Purposeful making - Emotional resonance - A sense of magic and meaning - Microsoft design leader Brittany Mederos similarly described Config’s theme as making meaningful things with purpose. ## Technology Should Reflect Human Values - Madeline Gannon argued that automation is not inevitable; it is intentional and reflects collective cultural choices. - This reframes AI from an unstoppable force into a technology shaped by human decisions about what should—and should not—be automated. - The central question becomes not simply what AI can make faster, but what people want to create with it and why. ## Slowing Down in an Automated World - Polaroid’s approach illustrates how technology can support, rather than replace, human creativity. - Its app provides AI-powered photography advice while preserving the company’s emphasis on slowing down, making physical things, and creating objects with personal meaning. - The example suggests that even advanced tools can reinforce deliberate, hands-on experiences instead of eliminating them. Ultimately, the article recommends treating AI as an augmentation of creative practice rather than an automatic substitute for it. Efficiency is valuable, but designers should protect the care, craft, and emotional intent that make creative work meaningful.

Read original(opens in new tab)
coupangOriginal article

Coupang SCM Workflow: Developing (opens in new tab)

Coupang has developed an internal SCM Workflow platform to streamline the complex data and operational needs of its Supply Chain Management team. By implementing low-code and no-code functionalities, the platform enables developers, data scientists, and business analysts to build data pipelines and launch services without the traditional bottlenecks of manual development. ### Addressing Inefficiencies in SCM Data Management * The SCM team manages a massive network of suppliers and fulfillment centers (FCs) where demand forecasting and inventory distribution require constant data feedback. * Traditionally, non-technical stakeholders like business analysts (BAs) relied heavily on developers to build or modify data pipelines, leading to high communication costs and slower response times to changing business requirements. * The new platform aims to simplify the complexity found in traditional tools like Jenkins, Airflow, and Jupyter Notebooks, providing a unified interface for data creation and visualization. ### Democratizing Access with the No-code Data Builder * The "Data Builder" allows users to perform data queries, extraction, and system integration through a visual interface rather than writing backend code. * It provides seamless access to a wide array of data sources used across Coupang, including Redshift, Hive, Presto, Aurora, MySQL, Elasticsearch, and S3. * Users can construct workflows by creating "nodes" for specific tasks—such as extracting inventory data from Hive or calculating transfer quantities—and linking them together to automate complex decisions like inter-center product transfers. ### Expanding Capabilities through Low-code Service Building * The platform functions as a "Service Builder," allowing users to expand domains and launch simple services without building entirely new infrastructure from scratch. * This approach enables developers to focus on high-level algorithm development while allowing data scientists to apply and test new models directly within the production environment. * By reducing the need for code changes to reflect new requirements, the platform significantly increases the agility of the SCM pipeline. Organizations managing complex, data-driven ecosystems can significantly reduce operational friction by adopting low-code/no-code platforms. Empowering non-technical stakeholders to handle data processing and service integration not only accelerates innovation but also allows engineering resources to be redirected toward core architectural challenges.

figma3 min readCurated summary

Are we finally entering the age of androids? | Figma Blog

Humanoid robots are moving from science fiction into public spaces and workplaces, forcing people to confront both the promise and risks of embodied AI. Their humanlike form makes technology more intuitive and emotionally engaging, but it also encourages people to project intelligence, intention, and personality onto machines. The article argues that designers must shape this illusion carefully, using humanoid robots to foster connection and understanding rather than control or deception. ## Humanoids as Technology in Human Form - Ameca, created by Engineered Arts, performs at Las Vegas’s Sphere as an interactive entertainer. - It turns toward speakers, displays facial expressions, tells jokes, and responds conversationally. - Its appeal comes from combining AI with expressive robotics. - Apollo, developed by Apptronik and argodesign, represents a different model: - It is designed as a general-purpose laborer. - Its flat face, cameras, and LED mouth prioritize function over lifelike appearance. - Humanoid robots have deep cultural roots, appearing in Greek mythology, Taoist philosophy, and science fiction. - Their human form makes software easier to engage with through gestures, expressions, and face-to-face interaction—what Engineered Arts CEO Will Jackson describes as a heads-up alternative to screen-based technology and virtual reality. ## What the Illusion of Sentience Unlocks - Humans naturally anthropomorphize objects and search for faces, motives, and signs of life. - Madeline Gannon uses body language and animal behavior as inspiration for designing industrial robots with recognizable personalities. - Even simple geometric animations can appear intentional: the Heider and Simmel experiment showed that people assign motives to moving shapes. - Ameca intensifies this effect through: - Furrowed brows, smiles, and expressions of surprise - Celebrity impressions - Custom personalities created by a dedicated “Persona Architect” - The ability to switch behavioral modes depending on context - Engineered Arts deliberately avoids making Ameca appear fully human: - Its metallic body avoids realistic skin. - It has no defined race or gender. - Its artificiality makes the theatrical nature of the interaction more visible. - The technology underneath remains impersonal: AI interprets language and maps it to suitable facial expressions. Nevertheless, users can experience meaningful emotional moments, such as a shy attendee gaining confidence while speaking Japanese with Ameca. - Gannon argues that designers must make complex systems legible, much as everyday objects communicate how they should be used. - She sees design as a way to redirect technology toward curiosity, kindness, and care, creating relationships based on connection rather than control. ## Designing Androids for Work - Apollo does not claim to be sentient; its purpose is practical labor. - It is being developed to address worker shortages, including work in Mercedes-Benz factories and potentially space exploration. - Its humanoid shape is primarily a response to human-scale environments and tools. - Unlike Ameca, Apollo must appear approachable enough for workers to accept, while avoiding the uncanny valley. - The article frames this as a central design challenge: workplace robots need to communicate socially without misleading people about what they are. Humanoid robots are most valuable when their appearance and behavior clarify how people should interact with them. Whether used for entertainment or labor, designers should treat the illusion of intelligence as an ethical material—balancing emotional engagement with transparency and purposeful design.

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

Welcome to The Prompt | Figma Blog

AI may transform design and building, but its ultimate impact remains unsettled. Figma’s *The Prompt* explores that uncertainty through essays and interviews with experts across design, engineering, product development, and the built environment. The collection argues that human judgment—especially the ability to ask thoughtful, well-framed questions—will remain central to making AI useful. ## Prompting as a Creative Discipline - Prompt engineering is described as the practice of getting better answers by asking better questions. - Like interviewing or editing a magazine, effective prompting requires: - Clear context - Thoughtful framing - Useful guidance - AI’s capabilities are treated as largely inert without human direction; people must coax useful results from the technology. - The act of questioning is presented as a fundamentally human and creative instinct. ## The Purpose of *The Prompt* - Created by Figma’s Story Studio and Brand Studio, the magazine launched at Config 2024. - It combines writing, interviews, and illustrations to examine how AI is changing creative and technical work. - Contributors come from both inside and outside Figma and work across: - Design - Engineering - Product development - Robotics - Manufacturing - Residential housing ## Questions About AI’s Future The magazine uses a range of prompts to investigate both immediate applications and larger societal questions, including: - What constitutes good design when AI can generate and automate more work? - Whether code becoming a commodity should be feared - How much data is actually necessary - How starting with imperfect or incomplete ideas can shape innovation - Whether AI development can move beyond technological echo chambers - If efficiency undermines creativity - How to build AI features that people both want and trust - The relationship between artificial design intelligence (ADI) and artificial general intelligence (AGI) - Whether automation can unlock the full potential of design systems - The role of robots in construction and housing - Whether society is entering an age of androids ## Practical and Long-Term Perspectives - Contributors examine ambitious challenges, such as applying AI to manufacturing and housing. - They also focus on what AI can deliver reliably today rather than only speculating about distant possibilities. - The goal is to make complex systems more understandable and usable while learning how to guide AI more effectively. Figma presents *The Prompt* as both a magazine and an experiment in inquiry: meaningful progress with AI depends not just on increasingly capable systems, but on humans asking clearer, more imaginative, and more responsible questions.

Read original(opens in new tab)
figma3 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.

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

36 Questions to Fall (Back) in Love with Tech | Figma Blog

Technology once felt playful, creative, and limitless, but constant notifications, social comparison, and digital distrust have made it feel burdensome. Figma’s article explores this changing relationship through interviews with more than 20 product and technology professionals, using 36 questions inspired by the psychology of vulnerability and connection. Their stories suggest that technology remains most meaningful when it enables creativity, community, and human connection rather than merely increasing consumption or efficiency. ## Early Encounters with Technology - Many interviewees remember technology as an open frontier for experimentation and self-expression. - Cristina Cordova discovered college pathways through the College Confidential forum, finding peers and practical guidance unavailable in her family. - Kristy Tillman credits early design software with shaping her career and recalls a period of “pure creativity.” - Mig Reyes remembers customizing AOL Instant Messenger profiles as a playful way to experiment and express himself. - These experiences illustrate how early technology often encouraged curiosity, discovery, and personal agency. ## When the Digital Honeymoon Ends - The web’s promise has been complicated by advertising, fear of missing out, endless notifications, and social-media pressure. - Lauren McCann describes the alienation of seeing friends gather without her. - Shyvee Shi notes that social platforms present polished versions of people’s lives, encouraging unhealthy comparison. - Peter Yang argues that creating things is generally more valuable than passively consuming social content. - As digital tools became essential to work and daily life, they also introduced new obligations, including “Slack-lash” and constant availability. ## Technology as a Source of Community - Despite its problems, technology can create lasting relationships and communities. - Lenny Rachitsky met his wife through the dating site howaboutwe.com. - Sho Kuwamoto formed enduring friendships through the online forum Midwest Raves. - Forums, dating platforms, and other digital communities can connect people with mentors, friends, and partners who share their interests. - At its best, technology helps people overcome geographic and social barriers and build a sense of belonging. ## AI, Creativity, and the Future - AI dominates conversations about technology’s future, bringing both excitement and caution. - Mihika Kapoor sees creative AI tools as a way to help people turn ideas into reality and unlock broader innovation. - Marcel Weekes emphasizes that developers should consider whether and how something should be built—not only whether it can be built. - Automation could reduce tedious work and allow people to focus more on craft, judgment, and interesting problems. - Jenny Wen argues that technology should also make room for joy, rather than optimizing every experience solely for speed or productivity. ## Reflecting on Your Own Relationship with Tech - The article invites readers to use its 36 questions as a tool for reflection and conversation. - Questions explore first usernames, early technology experiences, online identity, creativity, connection, and hopes for the future. - Sharing these stories is intended to create the same vulnerability and intimacy that inspired the original “36 Questions That Lead to Love.” Technology is worth embracing when it helps people create, connect, and express themselves. The practical challenge is to design and use digital tools more intentionally—prioritizing human value and joy over endless consumption, engagement, and optimization.

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

2023-03-08 incident: A deep dive into our incident response

Datadog’s March 8, 2023 global outage tested an incident-response process designed for large-scale failures. The company’s monitoring, on-call structure, training, and blameless culture enabled a coordinated response, but the incident also exposed challenges in diagnosing and managing a rapidly evolving, global outage. Datadog’s central lesson is that effective response depends less on rigid runbooks than on preparation, clear ownership, autonomous decision-making, and continuous learning. ## Datadog’s Incident Response Model - Datadog follows a “you build it, you own it” operating model. - Teams instrument their services extensively and configure monitors to detect problems around the clock. - Independent, out-of-band monitoring checks Datadog’s APIs from outside its infrastructure, ensuring that monitoring still works if Datadog itself becomes unavailable. - Slack channels are automatically created for incidents to provide shared situational awareness and enable additional engineers to contribute. ## Handling High-Severity Incidents - Senior engineers rotate on call for incidents involving substantial customer impact or multiple teams. - The first senior responder becomes the incident commander and retains overall responsibility. - A communications lead may manage internal updates and coordination. - For the most serious incidents, an engineering executive and customer-support manager join to provide leadership, business context, and customer-facing communication. - The incident commander remains accountable for coordinating the overall response. ## Preparation, Training, and Postmortems - Datadog uses a relatively low threshold for declaring incidents, giving engineers frequent practice with its response process. - Engineers complete incident-response training before joining an on-call rotation and repeat refresher training every six months. - Training covers on-call responsibilities, response roles, and blameless investigation practices. - Every high-severity incident receives a detailed postmortem focused on preventing recurrence. - Automation prompts responders to begin postmortems while the incident is still fresh. ## Autonomy and a Blameless Culture - Because large systems change constantly, detailed recovery procedures can quickly become outdated. - Datadog therefore gives engineers authority to choose the best response based on their knowledge of the affected services. - The company treats failures as weaknesses in systems rather than evidence of individual fault. - Blamelessness is intended to encourage creativity, honesty, and effective decision-making under pressure. ## The March 8 Outage - A systemd upgrade began around 06:00 UTC and ultimately triggered the outage. - Monitoring detected the problem within three minutes, and engineering teams were paged shortly afterward. - A high-severity incident was declared at 06:18, with an incident commander joining five minutes later. - The first public status update was posted at 06:31, and the outage was officially diagnosed as global at 06:32. - By 07:20, responders identified a Kubernetes failure and unhealthy intake systems as central problems. - Engineers confirmed by 08:00 that the Kubernetes failure was not spreading to additional or newly provisioned nodes. - A working mitigation for the EU1 region was found by 08:30. - Most US1 compute capacity recovered automatically by 11:00, while teams began organizing a longer recovery effort. - At 11:36, unattended upgrades were identified as the triggering event. - Compute capacity in EU1—the first step toward recovery—was restored by 12:05. ## Practical Lessons Datadog’s experience demonstrates the value of independent monitoring, practiced incident roles, rapid communication, and empowered responders. Organizations operating complex systems should regularly rehearse incident management, invest in resilient observability outside the primary platform, and use blameless postmortems to turn major outages into improvements.

Read original(opens in new tab)
datadogOriginal article

2023-03-08 incident: A deep dive into our incident response | Datadog (opens in new tab)

Datadog’s first global outage on March 8, 2023, served as a rigorous stress test for their established incident response framework and "you build it, you own it" philosophy. While the outage was triggered by a systemic failure during a routine systemd upgrade, the company's commitment to blameless culture and decentralized engineering autonomy allowed hundreds of responders to coordinate a complex recovery across multiple regions. Ultimately, the event validated their investment in out-of-band monitoring and rigorous, bi-annual incident training as essential components for managing high-scale system disasters. ## Incident Response Structure and Philosophy * Datadog employs a decentralized "you build it, you own it" model where individual engineering teams are responsible for the 24/7 health and monitoring of the services they build. * For high-severity incidents, a specialized rotation is paged, consisting of an Incident Commander to lead the response, a communications lead, and a customer liaison to manage external messaging. * The organization prioritizes "people over process," empowering engineers to use their judgment to find creative solutions rather than following rigid, pre-written playbooks that may not apply to unprecedented failures. * A blameless culture is strictly maintained across all levels of the company, ensuring that post-incident investigations focus on systemic improvements rather than assigning fault to individuals. ## Multi-Layered Monitoring Strategy * Standard telemetry provides internal visibility, but Datadog also maintains "out-of-band" monitoring that operates completely outside its own infrastructure. * This out-of-band system interacts with Datadog APIs exactly like a customer would, ensuring that engineers are alerted even if the internal monitoring platform itself becomes unavailable. * Communication is streamlined through a dedicated Slack incident app that automatically generates coordination channels, providing situational awareness to any engineer who joins the effort. ## Anatomy of the March 8 Outage * The outage began at 06:00 UTC, triggered by a systemd upgrade that caused widespread Kubernetes failures and prevented pods from restarting correctly. * The global nature of the outage was diagnosed within 32 minutes of the initial monitoring alerts, leading to the activation of executive on-calls and the customer support management team. * Responders identified "unattended upgrades" as the incident trigger approximately five and a half hours after the initial failure. * Recovery was executed in stages: compute capacity was restored first in the EU1 region, followed by the US1 region, with full infrastructure restoration completed by 19:00 UTC. Organizations should treat incident response as a perishable skill that requires constant practice through a low threshold for declaring incidents and regular training. By combining out-of-band monitoring with a culture that empowers individual engineers to act autonomously during a crisis, teams can more effectively navigate the "not if, but when" reality of large-scale system failures.

figma3 min readCurated summary

The Future of Design Systems is Automated | Figma Blog

Design systems are moving from static libraries toward automated, extensible ecosystems powered by plugins, widgets, and AI. These tools can automate repetitive work, expand Figma’s capabilities, and increasingly generate or recommend design solutions using existing system components. The article argues that automation will change designers’ responsibilities, but not eliminate the need for human judgment, creativity, and strategy. ## Plugins and Widgets as Design-System Extensions - Plugins have a long history in design and publishing software, dating back to tools such as HyperCard and QuarkXPress. - They created a broader ecosystem in which users could build and share custom effects, brushes, styles, and workflows. - In modern design systems, plugins generally serve two purposes: - Automating repetitive existing tasks. - Extending product capabilities through analytics, testing, accessibility checks, and other functionality. - Widgets add collaborative and visual tools directly to the design workspace, helping teams organize information and communicate around design systems. ## Automating Repetitive Tasks - Plugins can reduce manual work involved in maintaining and applying design-system assets. - Automation allows designers to spend less time on mechanical operations and more time on problem-solving and decision-making. - The broader trend reflects a shift from tools merely supporting designers to tools actively performing parts of the design process. ## Extending Design-System Capabilities - Plugins can provide capabilities that are not included in a core design application. - Examples include: - Gathering usage and library analytics. - Testing designs. - Improving accessibility. - Connecting design workflows to other tools and systems. - This extensibility enables teams to adapt their design environment to specialized organizational needs. ## AI-Assisted Design - Earlier experiments, such as Airbnb’s 2017 work on generating code from low-fidelity wireframes, demonstrated the potential of machine-learning-assisted design. - More recent tools such as Diagram’s Genius can analyze Figma files and suggest designs using components from an organization’s design system. - These developments suggest that AI is beginning to make earlier prototypes practical. - AI tools may eventually help generate interfaces, recommend components, complete workflows, or produce code from design input. ## Changing Roles and Responsibilities - Automation raises concerns about whether designers and developers will be replaced by software. - The article frames this as a question about how tools shape professional practice, rather than simply whether they eliminate jobs. - As routine production becomes automated, human designers may focus more on: - Defining problems. - Making judgments and trade-offs. - Establishing product direction. - Applying empathy, taste, and contextual understanding. - The future of design therefore depends on how practitioners adapt alongside increasingly capable tools. Design teams should treat plugins, widgets, and AI as ways to expand human capability rather than substitutes for design thinking. The most effective systems will combine automation for repetitive work with human oversight, creativity, and strategic judgment.

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

The year ahead: a conversation with Soleio, Julie Zhuo, and May-Li Khoe | Figma Blog

The article explores how creative work may evolve in 2022 as remote and hybrid work become permanent. Soleio argues that collaboration will move further into digital tools, requiring stronger documentation, asynchronous processes, and organizational discipline. He also predicts that creative tools will spread across the workforce and increasingly incorporate automated, virtual collaborators. ## Hybrid Work Will Reshape Creative Collaboration - Creative work will increasingly reflect hybrid workforce models. - Institutional knowledge and team context will move from physical offices into digital environments. - Traditional brainstorming sessions may shift from conference rooms to tools such as FigJam. - Creative software will become more accessible and collaborative, encouraging people outside traditional creative roles to use it. ## London’s Growing Technology Ecosystem - Relocating from Silicon Valley to London required Soleio to adjust his understanding of the two technology ecosystems. - Whereas technology dominates the Bay Area, it remains a newer and more disruptive sector in many other regions. - London is attracting more early-stage investors and becoming a stronger home for ambitious startups. - This growth may allow founders to build major technology companies without moving to Silicon Valley. ## Global Teams Need Better Organizational Hygiene - Distributed teams must deliberately coordinate feedback and decision-making across time zones. - Clear writing, recorded video feedback, and structured processes will become more important. - Remote teams cannot rely on shared office space or informal conversations to maintain context. - Transparent documentation and decision-making will become a competitive advantage. ## Automation and Virtual Collaborators - Design exploration and feedback are expected to become increasingly automated. - Future knowledge work may involve non-human agents that provide feedback, support iteration, and perform tasks currently handled manually. - These tools could fundamentally change the nature of teamwork by making virtual collaborators part of everyday creative processes. Teams preparing for the future should invest not only in collaborative tools, but also in documentation, asynchronous communication, and transparent organizational practices.

Read original(opens in new tab)