AI

331 posts

meta3 min readCurated summary

AI for American-Produced Cement and Concrete

Meta is expanding its use of AI to help concrete producers create stronger, more sustainable, and more domestically sourced mixes. Its new open-source model, Bayesian Optimization for Concrete (BOxCrete), uses existing performance data and lab results to identify promising formulations faster than traditional trial-and-error methods. Early projects show that AI can improve curing speed and reduce cracking while supporting greater use of U.S.-made cement and materials. ## The Case for AI-Designed Concrete - The U.S. produces about 400 million cubic yards of concrete annually. - Although ready-mix concrete is generally produced domestically, roughly 20–25% of cement consumption is supplied by imports. - Concrete mix designers must balance: - Structural strength - Curing speed - Workability and slump - Cost - Sustainability - Traditional design depends on laboratory experimentation, engineer judgment, and historical knowledge, making it slow and expensive to adapt. - Different cements have different chemistries, so a formulation that works with one cement may fail with another. ## Supporting Domestic Cement Production - Greater use of U.S.-made cement could strengthen domestic manufacturing, jobs, and investment. - Reshoring and foreign direct investment have returned more than 1.1 million jobs to the U.S. since 2020. - The cement and concrete sector contributes over $130 billion annually and supports approximately 600,000 jobs. - AI can help producers reformulate mixes around locally available materials without compromising performance. ## BOxCrete and Open Data - Meta is releasing BOxCrete on GitHub as an open-source model for concrete mix design. - Compared with earlier models, BOxCrete is more robust to noisy data and can predict concrete slump, an important measure of workability. - Meta is also publishing the foundational dataset used to develop the concrete mix for its Rosemount, Minnesota, data center. - The associated research paper describes the model, data, and methodology. ## Results in Minnesota - Meta, Amrize, Mortenson, and the University of Illinois used BOxCrete to design a mix for a data center foundation. - The mix used domestically sourced materials. - It reached full structural strength 43% faster than the original formulation. - It reduced cracking risk by nearly 10%. - After meeting structural requirements, the mix was approved for use in additional parts of the data center. ## Industry Partnerships in Illinois and Pennsylvania - Meta is working with Amrize and the University of Illinois to apply AI to industrial-scale concrete production. - Amrize operates 18 cement plants, 141 cement terminals, and 269 ready-mix sites across North America. - Amrize has introduced a “Made in America” cement label and announced nearly $1 billion in planned 2026 investments, partly aimed at increasing domestic cement production. - Pennsylvania-based Quadrel integrated Meta’s open-source framework into its ready-mix software. - Quadrel uses the technology for data preprocessing, batch and test normalization, feature engineering, customer-specific model training, and quality-control workflows. - Its models improve continuously as new field-test results are incorporated. ## Adaptive Experimentation - Meta’s Adaptive Experimentation platform uses Bayesian optimization to search the large space of possible concrete formulations. - The system: - Learns from historical mix designs, laboratory results, and performance metrics. - Proposes candidate mixes likely to satisfy target specifications. - Compares the performance of domestic and imported materials. - Applies technical and ingredient constraints before testing. - Updates its predictions after each new experiment. Meta’s work suggests that open-source AI can make concrete development faster, more data-driven, and better suited to domestic materials. Producers can use BOxCrete and adaptive experimentation to reduce laboratory costs, improve performance, and support more sustainable and resilient U.S. cement and concrete supply chains.

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

How Stripe Radar helps prevent free trial abuse

Free trial abuse is accelerating, particularly among AI companies whose trials provide access to costly compute resources. Stripe detected 6.2 times more abusive trials between November 2025 and February 2026, with self-serve AI startups facing especially high exposure. Stripe argues that AI-powered fraud detection can identify abuse at signup and prevent substantial downstream losses. ## The rise of free trial abuse - Fraudsters increasingly cycle through free trials or use invalid payment methods without converting to paid plans. - AI companies are especially vulnerable because free trials can grant access to expensive compute and APIs. - AI startups with self-serve signup and direct API access experience 10 times more attempted abuse than enterprise AI companies. - Similar patterns affect SaaS companies, marketplaces, and other businesses offering free trials. ## Stripe Radar’s abuse-prevention controls - Stripe Radar now offers a one-click control to detect behavior violating common trial terms, including repeated signups and missed cancellations. - The system predicts abusive behavior with 90% accuracy. - A new analytics page displays blocked high-risk payments and, for unenrolled businesses, shows transactions that would have been blocked. - The model analyzes payment instruments, devices, payment history, card BIN data, virtual card indicators, email domains, session timing, and other risk signals across Stripe’s network. ## Results for AI companies - Cursor and other AI businesses use Radar to block suspicious users before they consume costly compute. - Within two months, Stripe blocked over 550,000 high-risk free trials across four high-growth AI companies. - Stripe estimates this prevented $4.4 million in downstream compute-related losses. Stripe recommends its free trial abuse control for businesses across industries. Companies interested in early access can contact Stripe directly.

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

Our First 2026 Heroes Cohort Is Here! | Amazon Web Services

AWS has announced its first 2026 Heroes cohort, recognizing Maurizio, Ray Goh, and Sheyla Leacock for combining technical expertise with community leadership. Their work spans cloud architecture, generative AI, machine learning, and cybersecurity, while emphasizing mentorship, education, and meaningful human connections. Together, they demonstrate how technology leaders can expand access to skills and strengthen communities globally. ## Maurizio – Pignola, Italy - CTO and organizer of the AWS User Group Basilicata. - Has spent more than a decade developing cloud communities and technology ecosystems in areas where they previously did not exist. - Founded an international technology conference in a small mountain village, connecting global experts with local developers. - Covers topics including cloud architecture, DevOps, and web scaling, alongside creative networking opportunities. - Mentors children, university students, and professionals transitioning into cloud careers. - Combines technical leadership with inclusive, cross-generational community building. ## Ray Goh – Singapore - AI and machine learning community leader involved in AWS programs since 2018. - Founded The Gen-C in 2024, offering public library workshops on generative AI, LLM fine-tuning, and AWS AI agents. - Has spoken at major AWS events and contributed to the AWS Machine Learning Blog. - Led DBS Bank’s AWS DeepRacer initiative, which trained more than 3,100 employees. - Trained over 1,300 ASEAN students in LLM techniques in 2025. - Supports skills-based programs teaching AI and machine learning to women, children, and young people. ## Sheyla Leacock – Panama City, Panama - IT security professional, mentor, technical writer, and international speaker. - Leads the AWS User Group in Panama and participates in AWS Community Days and regional meetups. - Has spoken at AWS Summits, AWS re:Invent PeerTalk sessions, and more than 20 international conferences. - Publishes educational content focused on AWS cloud computing and cybersecurity. - Works with universities as a guest lecturer to help develop future technology and security professionals. - Strengthens the cloud and cybersecurity ecosystem through education, knowledge sharing, and community leadership. The new cohort highlights the broader impact of community-driven technology leadership. Readers can visit the AWS Heroes webpage to learn more about the program or connect with a Hero.

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

Investing in the people shaping open source and securing the future together

Open source security depends on supporting the maintainers who sustain critical software, not merely hosting their code. GitHub argues that funding, education, practical security tools, and AI assistance can reduce maintainer burnout while improving the broader software supply chain. Its new commitments focus on making security work more manageable as AI accelerates both vulnerability discovery and attacks. ## A $12.5 Million Open Source Security Commitment - GitHub is joining Anthropic, AWS, Google, and OpenAI in committing $12.5 million to the Linux Foundation’s Alpha-Omega initiative. - The funding will help integrate emerging AI security capabilities into existing open source workflows. - The effort builds on GitHub’s broader role as a provider of security tools, education, and long-term maintainer support. ## Expanding Maintainer Resources - More than 280,000 GitHub maintainers are eligible for free access to: - Core GitHub services - GitHub Copilot Pro - GitHub Actions - Code scanning and Autofix - Secret scanning and push protection - Dependency alerts - GitHub’s Secure Open Source Fund is adding $5.5 million in Azure credits and funding for training, expertise, community support, and new partners such as Datadog, Open WebUI, the Atlantic Council, and OWASP. - GitHub Security Lab is improving security advisories and Private Vulnerability Reporting to reduce low-quality reports and ease the burden on maintainers. ## Results from Security-Focused Funding - Previous Secure Open Source Fund programs supported 138 projects and more than 200 maintainers across 38 countries. - Participating projects produced: - 191 new CVEs - More than 250 prevented secret leaks - More than 600 detected and resolved leaked secrets - These projects collectively affect billions of monthly software downloads. - GitHub concludes that security improves when maintainers receive dedicated time, funding, education, and tools that fit naturally into their workflows. ## Using AI to Reduce Maintainer Burden - AI has increased the speed and scale of vulnerability discovery for both attackers and defenders. - Maintainers are facing more automated pull requests and security reports, often with poor signal-to-noise ratios, contributing to burnout. - GitHub’s goal is to use AI for triage, pull request review, vulnerability identification, and remediation—not simply to generate more findings. - GitHub has open sourced an AI-powered security research framework so maintainers, rather than only specialized security teams, can benefit from it. - Copilot Pro provides eligible maintainers with AI-assisted code review, agentic security remediation workflows, and access to multiple leading models. GitHub’s overall recommendation is to treat AI as a force multiplier and pair it with sustained funding, education, and workflow-integrated security tools. Supporting maintainers directly is presented as the most effective way to protect the wider software ecosystem.

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

Design’s Influence Is Expanding, and Here’s Why That Feels Hard | Figma Blog

Design is expanding into more products, interactions, and strategic decisions, especially as AI introduces new software categories and interfaces. Although AI makes design work faster, it also increases output, expectations, and workload rather than reducing effort. This leaves designers divided: the field is growing, but many are unsure whether it is improving. ## Design’s Expanding Influence - Each technological shift—from graphical interfaces to the web and mobile apps—has increased design’s scope. - AI is creating new categories such as agent orchestration systems and answer engines. - Existing products are gaining generative, conversational, and predictive features. - Users now interact through prompts, speech, and image uploads, creating new design challenges: - Translating ambiguous input into clear intent - Making automated experiences understandable and human - Designing beyond traditional screen-by-screen navigation - Survey results show mixed sentiment: - 36% of designers think the profession has improved - 35% think it has worsened - 29% see no change - Meanwhile, 82% of hiring managers say demand for designers has increased or remained steady, though only 20% believe the industry itself is improving. ## AI Expands the Work - AI helps teams address new design problems more quickly, but it does not necessarily reduce the amount of work. - Product builders reported a 17.5% year-over-year increase in the number of tasks they perform. - Research from UC Berkeley found that AI users work faster while also taking on more tasks and working longer hours. - Workers often feel more productive without feeling less busy. ## The Jevons Paradox in Design - As AI makes creation cheaper and easier, teams produce more designs, explore more options, and iterate more deeply. - This follows the Jevons Paradox: efficiency increases can lead to greater overall consumption rather than reduced consumption. - Software development experienced a similar pattern when cloud infrastructure made releases easier, resulting in more frequent releases and redesigns. - AI has changed the rhythm and volume of design work rather than eliminating it. Designers should view AI as a force multiplier, not a shortcut to less work. Its benefits will depend on managing rising expectations and workload while developing clearer approaches to complex, automated interactions.

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

Improving breast cancer screening workflows with machine learning

Google Research’s AIMS studies evaluated whether machine learning could support the UK’s mammography double-reading workflow. Across five NHS screening services, the AI system improved cancer detection sensitivity without reducing specificity, detected some cancers missed by human readers, and processed cases far faster. The studies also showed that safe deployment requires local calibration, monitoring for distribution shifts, and evaluation of how clinicians interact with AI results. ## NHS Screening Challenges - The UK NHS uses two human readers for each mammogram, with arbitration when their assessments require review. - A projected shortage of clinical radiologists—currently around 30% and expected to reach 40% by 2028—threatens the sustainability of this model. - AI could help increase detection while reducing pressure on radiology services. ## Study 1: Standalone Performance - The retrospective evaluation included mammograms from approximately 116,000 women screened across five NHS services. - The services represented three different double-reading and arbitration workflows. - AI thresholds were calibrated separately for each service to account for local populations and procedures. - Performance was measured against the original first reader using a 39-month follow-up period, including interval and subsequent-round cancers. - Researchers also assessed: - Comparisons with second and consensus readers - Lesion-level localization - Performance across demographic groups ## Study 1: Results - Cancer detection increased from 7.54 to 9.33 cases per 1,000 women. - The AI system achieved significantly higher sensitivity than the original first reader without compromising specificity. - It detected 25% of interval cancers missed by the original double-reading process. - Performance was especially strong for invasive cancers and women attending their first screening. - The study found no notable systematic disparities by age, ethnicity, breast density, or socioeconomic status. ## Prospective Technical Deployment - The system was deployed non-interventionally at 12 sites across two London screening services. - It processed 9,266 cases over roughly two months per service. - Mammograms were pseudonymized and sent to a secure Google Cloud-based system. - Median AI processing time was 17.7 minutes, compared with more than two days for the first human read. - The deployment detected a distribution shift between historical training data and current clinical data. - Researchers adjusted operating points during deployment to maintain safe and appropriate recall rates for local workflows. ## Study 2: AI in the Double-Reading Workflow - The second study examined how human readers performed when using AI as part of arbitration, rather than evaluating AI in isolation. - Twenty-two readers reviewed thousands of cases using real screening-service rules. - Two workflows were compared: - **Standard care:** decisions from the historical first and second human readers - **AI-enabled care:** the historical first-reader decision paired with the AI decision - This design aimed to assess the practical effects of replacing the second human read with an AI reader. The findings support AI as a potential second reader in breast cancer screening, but broader prospective clinical validation is still needed. Successful adoption should include phased deployment, local calibration, continuous monitoring, and careful evaluation of human-AI decision-making.

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

Google Research at The Check Up: from healthcare innovation to real-world care settings

Google Research argues that AI is entering a new phase in healthcare: moving beyond isolated tools toward personalized care, clinical collaboration, public-health planning, and scientific discovery. The post highlights research partnerships, open models, and real-world deployments designed to make healthcare more accurate, accessible, and proactive. Google emphasizes that these advances must be developed responsibly through clinical validation, peer review, and collaboration with healthcare institutions. ## AI for Personalized Healthcare - A Fitbit collaboration studied how AI could support preventative care across the United States. - The research found that a Personal Health Agent (PHA) modeled on a collaborative health team could provide more effective long-term support than single-purpose fitness or tracking apps. - The PHA combines: - Data analysis - Medical and domain expertise - Health coaching - Large multimodal models can transform wearable data into personalized guidance about sleep, fitness, and overall health. ## AI as a Clinical Collaborator - Google’s breast cancer research with Imperial College London and the UK’s NHS used diverse datasets and expert-validated ground truth data. - The experimental system identified 25% of “interval cancers”—cancers missed during screening and later detected after symptoms appeared. - Integrated into clinical workflows, the system could reduce radiologists’ workload while maintaining safe detection performance. - Google’s diabetic retinopathy screening model has been deployed through partnerships with medical institutions in India, Thailand, and Australia. - It has supported more than one million screenings. - Patients can receive results in roughly two minutes. - AMIE, a multi-agent medical AI system, can reason across medical histories, laboratory results, and medical images to identify overlooked patterns. - Google is testing AMIE with Beth Israel Deaconess Medical Center to assist with pre-visit history-taking and flag urgent symptoms. - An IRB-approved national study with Included Health will evaluate AI-supported telehealth care. ## Open Models for Healthcare Developers - Google’s Health AI Developer Foundations (HAI-DEF) provides free open-weight models and open-source tools for building healthcare applications. - MedGemma supports: - Medical text and image interpretation - High-dimensional 3D imaging - Medical-specific speech recognition - The All India Institute of Medical Sciences is using MedGemma for outpatient triage and dermatology screening. - Singapore’s Ministry of Health is adapting the model for locally relevant primary- and specialty-care applications. - The MedGemma Impact Challenge received more than 850 submissions aimed at turning AI research into practical, human-centered healthcare tools. ## AI for Public Health - Google Earth AI combines geospatial models and datasets to study connections between environmental conditions, population behavior, and health outcomes. - Researchers at Mount Sinai and Boston Children’s Hospital/Harvard used Google data and surveys to estimate childhood MMR vaccination coverage at ZIP-code resolution. - The resulting “super-resolution” maps identified pockets of under-vaccination that corresponded with recent measles outbreaks. - Such analysis could help public-health officials target outreach and prevention efforts more effectively. ## AI for Biomedical Discovery - Co-Scientist and Gemini Deep Think are being used to generate scientific hypotheses and support research across fields including single-cell analysis, public health, and neuroscience. - Google is also exploring evolutionary coding agents that run scientific-computing experiments in parallel. - DeepSomatic, a genomic analysis tool, is designed to improve the detection of cancer-related genetic mutations across multiple cancer types. Google’s broader recommendation is to treat AI as a validated collaborator and infrastructure layer rather than a replacement for clinicians or researchers. Continued clinical testing, expert oversight, transparent publication, and open developer access will be essential to translating these systems into safe, practical benefits.

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

Issue no.15: The State of Design | Figma Blog

AI is reshaping design by blurring the boundary between code and canvas, while expanding—not eliminating—the need for designers. Figma’s research suggests designers are adapting to new expectations by strengthening both AI-related capabilities and enduring creative fundamentals. The future favors people who can move fluidly across tools, teams, and stages of product development. ## AI’s impact on design work - 91% of surveyed designers say AI tools are helping them improve their work. - “Better design” means different things to different designers, including: - Visual polish - More thoughtful problem-solving - More intuitive user experiences - These differing priorities influence how designers understand and experience their jobs. - Design is increasingly defined by outcomes and problem-solving rather than by a single medium. ## Design hiring remains strong - AI is not reducing demand for designers according to Figma’s research. - 82% of surveyed hiring managers say their need for designers has either remained stable or increased. - Demand is growing beyond technology companies. - Organizations are seeking designers who can help translate new AI capabilities into useful products and experiences. ## Skills for the AI era - Designers are exploring emerging practices such as: - Prompting - MCP-related workflows - Connecting AI tools and processes - Translating between design, engineering, product, and other teams - AI-specific skills complement rather than replace foundational design abilities. - Communication, judgment, craft, and the ability to understand user and business needs remain essential. - The strongest designers are likely to combine technical fluency with human-centered thinking. ## Product teams are prototyping earlier - Product managers are using Figma Make to explore ideas and build conviction more quickly. - Teams at ServiceNow, Ticketmaster, and Affirm use prototypes to: - Communicate complex product behaviors - Test and develop ideas - Make better roadmap decisions - Prototyping is becoming accessible beyond traditional design roles. ## Code and canvas converge - Ideas can begin in code, visual design, or anywhere in between. - Figma presents the future of design as a continuous movement between code and canvas. - This shift makes designers less defined by their tools and more by their ability to shape ideas across mediums. Designers should treat AI as an extension of their creative and problem-solving toolkit, while continuing to develop core design judgment, communication, and craft. The most valuable practitioners will be those who can connect AI-enabled workflows with strong product thinking and cross-functional collaboration.

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

Finding Real Threats Among Hundreds of Millions of Security Signals — Transforming the Security Monitoring Paradigm with AI

Kakao argues that monitoring hundreds of millions of daily security events cannot scale through human analysts and increasingly complex rules alone. Its solution is a hybrid AI pipeline that filters noise early, analyzes only high-value events with multiple models, and continuously improves through verified feedback. The goal is not to generate more alerts, but to understand context and identify threats worth investigating. ## The Scale Problem: Finding Threats in a Haystack - Endpoint activity such as process execution, network connections, file changes, and privilege escalation produces hundreds of millions of events. - The volume grows rapidly as services expand, while the proportion of genuine attacks remains very small. - Increasing the number of analysts alongside event volume is economically and operationally unsustainable. - AI is needed to correlate events, interpret behavior statistically and contextually, and dynamically distinguish normal activity from anomalies. ## Limitations of Rule-Based Monitoring - Rules can identify what happened, but not why, who initiated it, or whether it fits the environment. - Legitimate deployment commands can resemble backdoor installation, causing high false-positive rates. - Analysis quality varies by analyst experience, shift, and time of day. - Analysts must manually assemble host information, network sessions, process histories, and related logs into an incident narrative. - Expanding detection categories—behavior sequences, statistical anomalies, multi-source correlations, and rare events—makes manual rule maintenance impractical. - SIEM correlation improves on single-event rules but remains limited to predefined scenarios and struggles with unknown attack patterns. - As rule sets and event volumes grow, both maintenance costs and matching performance become problematic. ## A Funnel-Based Hybrid Architecture - Kakao filters events through multiple stages before using AI: - Rule-based filters remove obvious noise. - Learned normal patterns are automatically excluded. - AI performs detailed analysis only on the small remainder requiring judgment. - Rules handle clear, deterministic patterns quickly, while AI evaluates complex contextual situations. - The framework is designed to accommodate new threat types and detection categories without creating a separate system for each scenario. ## Multi-Model Verification and Operational Resilience - Multiple AI models independently analyze the same event and cross-check one another. - Disagreement is treated as an uncertainty signal that can trigger deeper analyst review. - Model diversity helps reduce bias, false positives, and missed detections. - It also provides resilience against model failures, API outages, and quality changes after model updates. - The design balances cost, processing speed, and accuracy rather than optimizing only for detection precision. ## Teaching AI the Environment’s Context - Generic LLMs initially misclassified legitimate activity because they lacked knowledge of Kakao’s infrastructure. - The system supplies structured context, including: - Host roles - Services running on each host - Accounts used for automation - Normal communication and operational patterns - This context allows the model to act more like an analyst familiar with the organization than a generic security classifier. ## Analyzing Complete Behavior Flows - Individual commands such as `curl`, `chmod`, and script execution can occur in both normal deployments and attacks. - Kakao therefore reconstructs activity at the host level, linking: - Process execution history - Network sessions - File changes - Temporal ordering - The same command can have different meanings depending on when, where, and in what sequence it occurred. - AI evaluates the complete sequence to distinguish routine operations from intrusion behavior. ## Translating Events into AI-Usable Data - Sending raw events directly to an LLM wastes tokens on irrelevant information and reduces accuracy. - Different detection tasks require different signals; statistical anomaly detection and sequence analysis cannot rely on one fixed format. - Kakao introduced: - A standardized event schema - Dynamic feature construction tailored to each detection type - This reduces token usage while improving the relevance and precision of AI analysis. ## WALT: A Self-Learning Detection Loop - Initially, analysts had to manually convert AI conclusions into new detection policies. - Kakao developed WALT, or **Whitelist-Assisted Learning and Tuning**, to automate this feedback process. - Repeatedly verified normal patterns are converted into exception policies. - Those policies filter future matching events before they reach the AI engine. - Thousands of detection policies are reportedly being generated and operated this way, allowing accuracy to improve over time. ## Cost and Performance Constraints - Sending every event to an AI model caused unsustainable costs and processing delays. - The funnel architecture addresses this by reserving expensive AI analysis for events that survive earlier filtering. - The overall system must continuously balance economic cost, response speed, detection accuracy, and reliability. Kakao’s practical recommendation is to treat AI as part of a carefully designed security pipeline—not as a replacement for rules or analysts. Effective large-scale monitoring combines deterministic filtering, contextual multi-model analysis, structured data, and a controlled feedback loop that learns from verified outcomes.

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

Protecting cities with AI-driven flash flood forecasting

Google Research is expanding Flood Hub with urban flash flood forecasts that can provide up to 24 hours’ warning. The system addresses the lack of historical flood observations by using Gemini to extract verified events from public news reports, creating the Groundsource dataset for model training. Its global, lower-resolution approach aims to extend useful warnings to regions that lack expensive sensors and forecasting infrastructure, particularly in the Global South. ## The Need for Earlier Flash Flood Warnings - Flash floods cause roughly 85% of flood-related deaths worldwide and kill more than 5,000 people annually. - They often develop within six hours of intense rainfall, making rapid warnings essential. - Even 12 hours of warning can reduce flood damage by about 60%. - Early warning coverage remains highly unequal: fewer than half of developing countries have access to multi-hazard warning systems. - Flood Hub previously focused mainly on slower-moving riverine floods, covering more than 2 billion people across 150 countries. ## The Data Problem: “Invisible” Floods - River flood models can rely on stream gauges that record water levels and flow. - Flash floods may occur far from gauges, especially in cities where rainfall, impermeable surfaces, drainage, and terrain interact unpredictably. - Building detailed physical simulations globally would be computationally expensive. - Historical, precisely located flash flood records are also scarce, preventing conventional supervised machine learning. - Google’s Groundsource method uses Gemini to analyze public news reports, verify flood locations and times, and assemble a historical flash flood dataset. ## Scaling from Local Systems to Global Coverage - Local flash flood systems can be highly accurate using rain sensors, radar, water-level monitors, and flow measurements. - These systems are expensive to deploy and require location-specific calibration and engineering expertise. - Broader systems such as WMO’s FFGS, ERIC, and the U.S. NWS warning system depend on high-resolution maps, radar forecasts, and skilled hydrologists. - Those resources are often unavailable in the Global South. - Google’s model instead uses globally available products, including NASA IMERG, NOAA CPC, ECMWF’s IFS HRES forecasts, and Google DeepMind’s medium-range weather model. - Forecasts currently operate at a 20-by-20-kilometer resolution, constrained by the resolution of global data sources. ## The Urban Flash Flood Model - The model estimates whether a flash flood is likely in a given area during the next 24 hours. - It uses a recurrent neural network with a long short-term memory (LSTM) component to process meteorological time series. - Inputs also include static geographic and human-environment factors: - Urbanization density - Topography - Soil absorption rates - The initial rollout targets urban regions, where news coverage is denser and most of the world’s population lives. - It currently predicts impacts in areas with population densities above 100 people per square kilometer. ## Evaluation and Reported Performance - Precision was measured against the Groundsource dataset, but raw precision likely understates actual performance because some genuine floods are never reported. - A manual review of 100 alerts per continent found that many apparent false positives were confirmed flood events. - Recall was also evaluated against major floods recorded by the Global Disaster Awareness and Coordination System (GDACS). - Results indicate comparable precision and recall in regions such as South America and Southeast Asia and in wealthier countries with better instrumentation. The approach demonstrates how AI and unstructured public information can help provide scalable flash flood warnings where conventional monitoring infrastructure is limited. Its current urban focus and 20-kilometer resolution make it a broad early-warning tool rather than a replacement for highly localized sensor networks.

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

Superhuman Launches First-of-Its-Kind Agent-Specific Attribution With Grammarly Authorship Update

Superhuman is expanding Grammarly Authorship into its AI-native Docs workspace with agent-specific attribution and default-on tracking. The update records whether AI contributed to research, generation, or revision, while students retain control over whether reports are shared. The company argues that transparent authorship can help schools replace blanket AI bans and detection-based enforcement with more informed, responsible AI education. ## Agent-Specific Attribution - Authorship can now identify which Superhuman AI agents contributed to a document and how they were used. - It distinguishes among: - Research support - Content generation - Revision and feedback - This gives educators more context for evaluating the writing process rather than only the final submission. - Featured agents include: - **Reader Reactions:** Predicts audience responses and suggests improvements. - **Citation Finder:** Locates supporting or challenging sources and formats citations. - **Proofreader:** Improves clarity, flow, correctness, and stylistic consistency. - **Fact Checker:** Finds evidence that supports or disputes claims. ## Default-On Authorship in Docs - Authorship is now available by default in Superhuman Docs. - Students no longer need to manually activate tracking. - The system records human writing, AI-generated content, and AI-edited text as work progresses. - Students still control access: instructors cannot see a report unless the student chooses to share it. ## Supporting Academic Integrity - Authorship is intended to reduce reliance on potentially inaccurate AI-detection tools and false positives. - More than 5 million Authorship reports have been generated since its beta launch in October 2024. - Rowan-Cabarrus Community College reported a 96% reduction in academic integrity violations in one semester after adopting the tool. - The company says process visibility can help educators teach responsible AI use instead of focusing primarily on punishment or prohibition. ## Institutional Controls and Availability - Educational administrators can configure which AI agents are available to students and faculty. - Authorship is available in Docs at no additional cost and is also supported in: - Google Docs - Microsoft Word - Canvas - The feature is part of Superhuman’s broader effort to provide AI transparency wherever students write. Superhuman recommends using Authorship as a foundation for nuanced AI policies and process-based assessment. By showing how AI was used while preserving student choice over sharing, the tool aims to support both academic integrity and practical AI literacy.

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

Analyzing first-party fraud trends: Account, free trial, and refund abuse

First-party fraud is rising as legitimate customers exploit account, trial, and refund policies rather than using stolen credentials. Stripe’s analysis identifies account abuse, free-trial abuse, and refund fraud as rapidly growing problems, with AI companies particularly exposed because free access consumes costly compute resources. Stripe is expanding Radar with tools to detect these behaviors across the customer lifecycle. ## Account Abuse at Sign-Up - Users create multiple accounts to repeat free trials, reuse promotional offers, or evade fraud detection. - A single payment method may be linked to dozens or hundreds of emails, IP addresses, and names. - About 20% of consumers admit to using different contact details to access promotions repeatedly; the figure rises to 29% among Gen Z and 27% among millennials. - AI companies are especially vulnerable because repeated free-tier access consumes compute resources. Stripe found suspected multiaccount abuse in 7.4% of AI-company sign-ups. - Stripe is introducing Radar capabilities to assess sign-ups and login events, helping businesses distinguish genuine prospects from repeat abusers. ## Free-Trial Abuse and Virtual Cards - Customers may cycle through multiple trials to extend free access beyond the stated terms. - AI startups with self-serve registration and direct API access experience 10 times more attempted abuse than enterprise AI offerings. - Blocking virtual cards is no longer an effective solution because many legitimate customers use them for privacy and security. - Stripe’s new solution predicts common trial-term abuse with 90% accuracy. - Radar also provides analytics showing blocked high-risk payments and, for businesses without the control enabled, payments that would have been blocked. ## Refund Abuse After Purchase - Customers may falsely claim that products were defective or never delivered while keeping the merchandise. - Stripe estimates global refund-abuse losses at roughly $100 billion annually. - “Wardrobing”—wearing items briefly before returning them—was admitted by 27% of shoppers who returned an online purchase, rising to 49% among Gen Z shoppers. - Social-media shopping hauls can create costs through return shipping, processing, markdowns, and unsellable inventory. - Organized abusers may use more than 100 email variations and multiple cards to bypass refund limits and “no questions asked” policies. - Because purchases often use valid credentials, the abuse may only become visible after the refund is issued. - Stripe is developing tools to identify refund abuse and is seeking preview participants. ## Stripe’s Broader Fraud-Prevention Strategy - Stripe plans to use its network data, existing AI infrastructure, and Radar to detect repeat abusers, fake-account networks, and emerging first-party fraud tactics. - The broader objective is to monitor and reduce abuse throughout registration, trial access, payment, and post-purchase refund processes. Businesses should treat first-party fraud as a lifecycle-wide risk rather than relying only on transaction-time fraud checks. More targeted, AI-based detection can reduce abuse without unnecessarily rejecting legitimate users, especially those using virtual cards.

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

5 Design Skills To Sharpen in the AI Era | Figma Blog

AI is changing product creation by accelerating experimentation and expanding who can participate in design. Figma argues that designers should strengthen adaptable, technology-oriented skills rather than rely only on traditional craft. The first priority is becoming fluent with AI tools and learning to prompt them effectively, while maintaining human judgment and design fundamentals. ## AI Fluency and Prompting - AI skills are becoming essential for designers and increasingly important in non-design roles such as product management, development, and marketing. - More than half of designers and hiring managers consider AI design capabilities—such as rapid prototyping and “vibe coding”—important hiring skills. - Among designers who adopted AI during the past year: - 91% say it helps them create better designs. - 89% say it helps them work faster. - AI can support many activities, including: - Editing images directly within a workflow. - Building prototypes instead of writing traditional product requirements documents. - Testing assumptions and creating tangible artifacts for team alignment. ## Writing Better Prompts - Clear, structured prompts produce more reliable AI-generated results. - Figma recommends organizing prompts around: - The task - Context - Required elements - Behavior - Constraints - Prompting is presented as a repeatable design practice, not merely a way to get a one-off output. - Strong prompts help turn AI into a consistent design partner rather than an unpredictable experimentation tool. ## Broader Changes to Design Work - AI is lowering barriers to participation and blurring boundaries between product roles. - Designers are increasingly expected to work across disciplines and use AI to extend their capabilities. - Prototyping is becoming a faster way to communicate ideas, validate assumptions, and build momentum than relying solely on written documentation. Designers should build practical fluency with AI tools, practice structured prompting, and use prototypes to make ideas concrete—while applying their own judgment to guide and evaluate the results.

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

Vishal Kapoor’s 10 Rules for Building Honest Products with AI | Figma Blog

AI product development is ultimately a trust challenge, not merely a technical one. Vishal Kapoor argues that AI should accelerate exploration and execution without replacing human judgment, empathy, or accountability. His approach centers on building products that remain transparent, secure, emotionally aware, and honest—especially in sensitive areas such as personal finance. ## Start with First-Principles Thinking - Break complex problems into their fundamental components before reaching for an AI solution. - AI can accelerate ideation and iteration, but it cannot replace human intuition, taste, or a distinctive product perspective. - Question basic assumptions to uncover better alternatives. For example, Affirm challenges why customers receive three payment-plan options rather than one, five, or a customizable plan. - Thoughtful disagreement among people remains essential for generating meaningful insights; AI is best used to explore possibilities more quickly. ## Stay Close to Human Emotions - Product teams should regularly observe customers, conduct UX research, read app-store reviews, monitor social media, and speak directly with users. - Metrics and dashboards identify patterns, but they do not fully explain the emotions behind customer behavior. - Financial products especially require sensitivity to anxiety, frustration, trust, and relief—not just transactional outcomes. - Affirm uses an internal AI tool called Pluto to investigate recent customer disappointments, while still relying on human observation and empathy to interpret those experiences. ## Treat AI as a Teammate - AI is neither a guaranteed productivity multiplier nor an inevitable replacement for employees; it is another participant in a collaborative product-development process. - Tools such as Figma Make help teams convert customer insights into prototypes and test ideas faster. - AI can audit large numbers of screens and interaction patterns across web, mobile, and desktop experiences, identifying outdated or inconsistent designs. - Moving repetitive auditing and prototyping work from engineers to designers and product managers increases iteration speed and creates more room for creativity. ## Test the Edge Cases - Trustworthy products cannot be designed only around the happy path. - Teams should deliberately explore unusual inputs, failure modes, and unexpected customer situations rather than assuming normal usage. - The article begins this rule by emphasizing that authentic product quality depends on examining the difficult and overlooked scenarios where users are most likely to encounter confusion or harm. The overall recommendation is to use AI aggressively for exploration, prototyping, and repetitive analysis—but keep humans responsible for defining the problem, understanding customers, challenging assumptions, and ensuring the final product is honest.

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

Scaling AI opportunity across the globe: Learnings from GitHub and Andela

GitHub and Andela argue that AI opportunity should not depend on geography or employer resources. Their AI Academy trained 3,000 engineers by embedding GitHub Copilot into real production work rather than isolated exercises. The approach improved developers’ ability to understand unfamiliar systems, work with legacy code, and focus more time on higher-value decisions—while preserving human review and accountability. ## Unequal Access to AI Skills - Developers across Africa, South America, and Southeast Asia have substantial technical talent but uneven access to: - Emerging AI tools - Mentorship and structured training - Reliable connectivity and high-performance computing - Affordable cloud services and data - Much existing training assumes constant internet access, well-resourced environments, and localized content. - Contract-based or informal work can leave developers with limited time and financial capacity for reskilling. - Without affordable access and regionally relevant learning communities, AI could deepen existing technology inequalities. ## Learning AI Within Production Work - Mid-career developers generally cannot leave live systems and deadlines to experiment with new tools. - Simply giving teams access to AI does not guarantee adoption; organizations also need: - Clear role and use-case definitions - Training tied to actual responsibilities - Updated review and quality standards - Andela selected developers whose work involved complex production systems and incorporated Copilot into: - IDE workflows - Pull request reviews - Refactoring and maintenance - This made training practical and exposed AI tools to legacy code, architectural complexity, and real production risks. ## Faster Orientation in Unfamiliar Systems - One of the first benefits was not raw code-generation speed but faster understanding of existing systems. - Developers used AI to: - Generate unit tests before changing legacy code - Reveal system behavior and architectural patterns - Draft refactors and clarify control flow - Sketch diagrams of system boundaries - Tests provided safer boundaries for modifying poorly covered legacy code. - AI suggestions still required cleanup and could introduce subtle errors, making disciplined review essential. ## Confidence and Productivity Gains - After several weeks, developers reported: - Faster onboarding - Greater confidence handling ambiguous work - Less time spent on setup and more on business and engineering decisions - Senior engineer Daniel Nascimento estimated that Copilot increased his productivity by about 50%. - The main value was not merely completing tasks faster, but freeing time to understand business needs and focus on meaningful impact. ## Practical Model for AI Adoption - AI training is most effective when it is: - Embedded in everyday development - Based on real systems and responsibilities - Supported by structured guidance - Evaluated through production-quality standards - Organizations should treat AI as a capability developed through practice, not as a standalone certification or experiment. The GitHub–Andela experience suggests that inclusive AI adoption requires more than tool access. Pairing affordable, structured training with real production work can help developers worldwide build confidence, improve productivity, and participate more fully in the AI-driven future.

Read original(opens in new tab)