Data Generation

2 posts

google4 min readCurated summary

Designing synthetic datasets for the real world: Mechanism design and reasoning from first principles

Synthetic data generation should be treated as dataset-level mechanism design rather than one-sample-at-a-time prompting. Google’s Simula framework uses reasoning models to control coverage, diversity, complexity, and quality independently, enabling seedless, reproducible datasets for scarce or privacy-sensitive domains. Experiments across five domains show that thoughtfully designed data can outperform larger datasets, but the best configuration depends on the target task and model. ## Why Real-World Data Is Insufficient - Specialized AI applications often lack accessible data because domains are uncommon, expensive to label, or privacy-sensitive. - Manually creating datasets is costly, slow, and error-prone. - Real-world datasets are static, limiting rapid iteration and making it difficult to proactively generate safety edge cases. - Synthetic-first workflows can make data programmable, versioned, reproducible, and inspectable. ## Limitations of Existing Synthetic Data Methods - Many approaches depend on manual prompts, evolutionary algorithms, or large amounts of seed data. - These dependencies reduce scalability and explainability. - Generation parameters are often entangled, making it difficult to independently control diversity, difficulty, and correctness. - Most methods optimize individual samples instead of designing the dataset’s overall distribution. ## Simula’s Reasoning-First Design - Simula constructs datasets from first principles using reasoning models rather than opaque generation processes. - The framework is seedless and agentic, allowing improvements as the underlying models become better at reasoning. - It separates generation into independently controllable axes. ### Global Diversification - Reasoning models map a domain into deep, hierarchical taxonomies that serve as sampling scaffolds. - A recursive propose-and-refine process generates candidate categories, then evaluates, merges, and filters them with a critic model. - These taxonomies help datasets cover long-tail concepts instead of concentrating on common examples. - The approach was demonstrated with structures such as a Cyber Threat Intelligence taxonomy. ### Local Diversification - Taxonomy nodes are converted into “meta-prompts” representing scenarios. - Multiple distinct instantiations are generated for each scenario. - This reduces mode collapse—for example, representing SQL injection through varied contexts rather than repeating nearly identical questions. ### Complexification - A configurable portion of scenarios is made more elaborate or difficult. - Complexity can therefore be adjusted without changing the dataset’s semantic coverage. - The appropriate difficulty level depends on the capabilities of the model that will consume the data. ### Quality Checks - A dual-critic loop independently assesses whether outputs and answers are correct. - Independent verification helps reduce sycophancy and improves label reliability. - This enables quality control without requiring human review of every example. ## Reasoning-Based Evaluation - Conventional metrics such as embedding cosine distance offer only broad signals and limited practical guidance. - Simula introduces: - **Taxonomic Coverage**, which measures how thoroughly the conceptual space is represented. - **Calibrated Complexity Scoring**, which uses LLM-based batch comparisons and chess-style Elo ratings to estimate the difficulty of individual examples. - These metrics aim to evaluate diversity and difficulty in ways that better reflect downstream usefulness. ## Results Across Domains - Simula was evaluated using Gemini 2.5 Flash as a teacher and Gemma 3 4B as a student. - The experiments covered cybersecurity, legal reasoning, grade-school mathematics, and multilingual academic knowledge, with datasets reaching 512,000 examples per domain. - The full combination of global coverage, local diversity, and quality critique consistently outperformed simpler baselines. - High complexity improved math reasoning accuracy by 10% in GSM8k but harmed legal reasoning performance, where the teacher model was weaker. - Simula often achieved stronger downstream results with fewer examples, suggesting that data properties matter as much as volume. - The findings show that there is no universally optimal synthetic-data recipe; effective dataset design must be tailored to the domain and target model. Synthetic data is most effective when treated as an engineered system rather than a source of additional volume. Practitioners should separately tune coverage, variation, difficulty, and verification, then validate those choices against the downstream task.

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

Extend what’s possible with plugins for you and your team | Figma Blog

Figma’s post argues that plugins can turn repetitive, team-specific design tasks into fast, reusable workflows. Examples from GitHub, Atlassian, and Uber show how teams use plugins for component management, theming, realistic content, critique, and collaboration. The conclusion is that when no public plugin fits a specialized need, teams should build bespoke tools—and potentially combine them into a unified plugin. ## Building a Unified Plugin at GitHub Brian Lovin began creating plugins at GitHub after noticing how much time designers spent on repetitive operations. - A **borders utility** toggled the visibility of divider layers within list-item components. - This allowed GitHub to maintain one flexible component instead of multiple components for every divider size and placement. - A **color-theming plugin** helped designers manage light, dark, and high-contrast themes. - It searched functionally named styles and quickly switched entire designs between themes. - A **data population plugin** pulled live API data into designs. - It mapped avatars, usernames, and names to appropriately named component layers. - These tools were consolidated into a single “mono plugin,” giving the team one interface for several workflow improvements. ## Product-Specific Content at Atlassian Atlassian created the **ADG Data Generator** to prevent designers from using generic or misleading placeholder content. - Designers can generate data appropriate to specific products: - Jira projects and ticket numbers - Bitbucket branches and commit messages - The plugin keeps related content logically connected, such as matching project names with project descriptions. - For user imagery, it generates realistic but entirely artificial faces instead of using stock photos of real people. - Atlassian shared the generator’s source code with the broader community. ## Collaboration and Critique at Uber Uber’s design team developed more than four plugins to improve collaboration, consistency, and speed. - A **mobile design critique plugin** creates a QR code and URL for the selected Figma frame. - Critique participants can open the design on their own phones and experience it at the intended mobile scale. - This gives each reviewer a better sense of how the design feels in-hand than viewing it on a shared large screen. ## A Pattern for Identifying Plugin Opportunities The examples show that useful plugins often emerge from recurring friction rather than from abstract experimentation. - Look for repetitive tasks that require many clicks. - Target workflows tied to a company’s own products, components, data, or design system. - Automate tasks involving large sets of styles, layers, or content. - Combine related utilities into one accessible team tool when multiple plugins begin to accumulate. Teams should start by identifying a specific, repeated workflow problem and build the smallest tool that removes it. Over time, those focused tools can become a broader internal plugin tailored to the team’s design system and processes.

Read original(opens in new tab)