Register and share your invite link to earn from video plays and referrals.

Search results for ContinuousImprovement
ContinuousImprovement community
One keyword maps to one global community path.
Create community
People
Not Found
Tweets including ContinuousImprovement
Harness Engineering Practices P19. Turn Failures into Data Assets (The Harness's Own Retro Loop) 🎯 Point A harness that repeats the same failures is an unimprovable black box. Log failures and feed them back into harness improvement. 📝 Overview Log every human intervention, rollback, and escaped defect with its cause, then feed this into harness improvements (new gates, new instructions, new tools). The harness should have CI for itself. This is what separates maturity L3 (measuring) from L4 (continuously improving). 🔍 Explanation When agents fail, most organizations conclude "the model is bad." But the real question is "why couldn't the harness prevent this failure?" A human intervention means the harness lacked a guardrail or verification. A needed rollback means the circuit breaker didn't trigger. An escaped defect means the verifier was insufficient. Recording these events with root cause analysis and converting them into harness improvement actions (adding gates, updating instruction files, improving tools) is the loop that matures a harness into a product. 🛠 How to Practice - Record all human interventions, rollbacks, and escaped defects in structured logs with cause classification - Run regular retrospectives (weekly or biweekly) to identify recurring failure patterns - For each failure pattern, select and implement the most effective improvement action (new gate, instruction addition, tool improvement) - Measure improvement action effectiveness and retract low-impact ones to try different approaches 💼 Use Cases - Weekly analysis of issue-to-PR agent failures to identify harness improvement points - CI auto-maintenance: tracking false positive causes to improve triage logic - Incident response: deriving observability access improvements from cases where agent recommendations were inaccurate ⚠ Pitfalls Adding a rule after every failure leads to "Scaffolding Ratchet" (AP3). Turning failures into data assets isn't about adding more rules — it's about root cause analysis and choosing the most effective improvement. Logging without analysis accumulates data without generating value. Regular retrospective processes are essential. #HarnessEngineering# #ContinuousImprovement#
Show more
"I'm going to tell you my story because I think it's an amazing story of continuous improvement, of how teeny-tiny steps compound over time." Over the past year, my work has transformed completely—and it all started with a broken ankle and a willingness to get curious about AI. In this article, I share how I went from a skeptic to building multiple AI products, even though I had a limited engineering background. Here's what you'll learn: 🔧 How small experiments can snowball into real products (I launched my first AI tool just three weeks after starting to experiment) 🧠 Why AI evals became the missing discovery habit—a feedback loop that helped me continuously improve my products 🎯 How personal productivity experiments taught me the skills I needed to build production AI products 🤝 Why I still believes in talking to customers, but see new opportunities for AI to be additive rather than replaceable 💡 The hero's journey framework I used to make sense of my transformation 🚀 Real examples of the products I built: Interview Coach, Business Fundamentals Coach, AI-generated interview snapshots, and more The core message? You don't have to be an engineer to figure this out. You have access to expert tutors 24/7, and teeny-tiny steps compound over time. Read the article (or watch the talk): ❓ What's one small experiment or skill you've been curious about trying but haven't started yet? Share your thoughts in the comments below.
Show more
Sustainability is a shared responsibility. Through innovation, collaboration, and continuous improvement, Intel Foundry is working with customers, suppliers, and industry partners to help advance a more sustainable future for semiconductor manufacturing. #IntelFoundry# #Sustainability#
Show more
Practices for embedding AI agents into enterprise systems [Feedback Flywheel] 💡 Is your agent "deploy and forget"? You need a mechanism to channel production user feedback into a continuous improvement cycle. This pattern systematically collects user feedback, converts it into eval datasets, and drives ongoing quality improvement. 🔥 Problems it solves - No post-deployment quality improvement cycle exists - Quality degradation from model changes, data drift, or new query patterns goes undetected - No data to prioritize which problems to fix first 🏗️ Proposed pattern Collect both implicit signals (retries, abandonment, manual corrections) and explicit signals (thumbs up/down, text feedback, human escalations). Convert low-rated and escalated cases into eval datasets and add them to regression tests. Prioritize improvements by frequency and severity of negative feedback, then apply fixes to prompts, tools, routing, or RAG. Validate all changes through eval gates before redeployment. Since reviewing every interaction is impossible, start by sampling 100% of negative cases and 5-10% of successful ones, then adjust based on measured review capacity and improvement yield. ✅ Selection criteria - Good fit: Every production agent intended for ongoing operation - Not a fit: Throwaway experiments or PoCs ⚠️ Pitfalls - Ignoring implicit signals means you miss quality degradation that users never explicitly complain about - Without an operational process connecting collected feedback to improvement actions, data piles up with no impact - Failing to update golden datasets causes eval gates to become stale and miss new failure patterns 🛠️ Implementation Approach 1. Collect feedback via in-app UI and Slack reactions (thumbs up/down), and automatically detect implicit signals (retries, abandonment, manual corrections) as trackable events 2. Build a pipeline that automatically converts low-rated and escalated cases into eval datasets and adds them to the regression test suite 3. Create a dashboard that visualizes improvement priorities by frequency and severity of negative feedback (start with 100% of negative cases and 5-10% of successful ones as the sampling baseline) 4. Validate all prompt, tool, and routing changes through eval gates (P26) to confirm no quality regression before redeployment 5. Set up an A/B testing infrastructure combining LLM-as-judge automated evaluation with human review to quantitatively measure improvement impact #AIAgents# #EnterpriseArchitecture#
Show more
.@NSF is hiring the inaugural Head of its Office of Metascience to apply the scientific method to how we fund, organize, and evaluate research. Continuous improvement will accelerate discovery. If you care about the science of science, apply:

Show more
The black leather jacket wasn't the final form. 🥋 @JensenHuang was awarded an honorary black belt by the International @Judo Federation, recognizing his leadership and the shared values of judo and innovation: perseverance, respect, and continuous improvement.
Show more
KuCoin announced that its Artificial Intelligence Management System (AIMS) has officially achieved ISO/IEC 42001:2023 certification, reinforcing its capabilities in responsible AI deployment, governance, and continuous improvement. As the world’s first international standard for AI management systems, ISO/IEC 42001 establishes an internationally recognized framework covering KuCoin’s AI management and supporting functions to drive transparent, secure, and compliant AI integration across risk control, AML, fraud detection, market surveillance, and customer operations.
Show more
Zcash has unparalleled cryptographers, security engineers, and security researchers. And the community is heavily focused on continuous improvement and hardening the network. That's why it engages world class security researchers to look for bugs. And that's why the recent potential exploit was found. It wasn't by accident and it's a vote of confidence, not a cause for alarm. When it comes to any L1, there will be bugs. What's important is that there are world class researchers focused on hardening the network and staying ahead of the bad guys. This has always been and always will be the dynamic of building software that is secure. Onward.
Show more
0
496
1.5K
201
Forward to community
Another solid day at Hacker Summer Camp connecting with AppSec folks in the trenches. The recurring theme isn't just finding vulns, it's getting them fixed—and more importantly, preventing them upstream. That means working *with* developers, understanding their pain points, and making security less of a roadblock. It's about pragmatic wins and continuous improvement, not just tool deployment. If you're at Black Hat, swing by booth #4943# to share war stories and strategies for effective developer collaboration. Also, don't miss Katie Paxton-Fear and Milan Williams today at 1:30 PM at our booth, talking about 'Overcoming the Fear of Security Risk with AI-Assisted Development'—a critical topic for practitioner success.
Show more
A reminder from Atomic Habits by James Clear: “The purpose of setting goals is to win the game. The purpose of building systems is to continue playing the game. True long-term thinking is goal-less thinking. It’s not about any single accomplishment. It is about the cycle of endless refinement and continuous improvement. Ultimately, it is your commitment to the process that will determine your progress.”
Show more