Topic

AI Automation

All digests tagged AI Automation

How to use Jev to automate your business (Step-by-step w/ Treg) thumbnail

· 14:29

How to use Jev to automate your business (Step-by-step w/ Treg)

This talk introduces Jev, a specialized model designed for reliable, high-accuracy business automation rather than creative text generation. Unlike general-purpose LLMs, Jev is optimized for structured decision-making, providing probability distributions for a limited set of options. This makes it ideal for mission-critical workflows requiring near-100% accuracy, such as fraud detection, internal link mapping, and classifying user intent, while being significantly faster and cheaper than large general models.

Key takeaways

  1. Jev's Core Advantage

    Jev is designed for reliable, high-quality decision-making, outputting the probability of a list of given answers rather than predicting text token by token. This makes it extremely fast and cost-effective for high-volume business workflows.

  2. Confidence Scoring 2:00

    Every answer Jev provides comes with a probability distribution (confidence score). This allows developers to build sophisticated business logic (e.g., if confidence > 70%, auto-block; if 35% < confidence < 70%, request human review).

  3. Use Case: Browser Automation 3:40

    Jev can predict the next action (click, type) and the target UI element based on the DOM and interaction history, enabling fast and accurate browser and computer use for agent systems.

  4. Workflow Example: Fraud Detection 7:30

    By combining Jev with data services like Track, users can build automated pipelines to classify signups (e.g., fraud, upsell value, affiliate) using thousands of data points, making previously uneconomical automation possible.

Watch on YouTube Full article

One Designer + AI. Hundreds of Deliverables. — Vincent Wendy, AI Engineer thumbnail

· 16:48

One Designer + AI. Hundreds of Deliverables. — Vincent Wendy, AI Engineer

This talk details how one designer managed the massive scale of deliverables (signage, stickers, landing pages, etc.) for a large conference (7,000 attendees, 140+ sponsors, 300+ speakers). The solution involves implementing a structured design system and automating workflows using AI agents (like Devin) and tools like Figma. The core methodology emphasizes shifting from manual, linear processes to highly automated, validated pipelines to solve the 'scale problem.'

Key takeaways

  1. The Five Pillars of Scaling Design 0:04

    To manage massive deliverables, the process must focus on: 1) Building a solid foundation (design system, typography, components); 2) Making designs reusable; 3) Automating workflows; 4) Validating output; and 5) Removing friction. (4:45)

  2. AI Agents for Automation 0:09

    AI agents (e.g., Devin) are used to automate complex tasks, such as generating speaker announcement graphics and trading cards for 300+ speakers, or pulling live schedule data and exporting it as PNGs. (9:16)

  3. Systemic QA and Validation 0:13

    AI can be used for visual quality assurance (QA), such as checking 140+ sponsor logos on a banner for missing assets or detecting visual inconsistencies on merchandise. (13:15)

  4. Thinking as a User 0:14

    The most critical shift is to think like an end-user (attendee) rather than a designer, focusing on handling exceptions and ensuring all elements (wayfinding, schedules) are interconnected. (14:21)

Watch on YouTube Full article

Inside Kikimora: We Built a Dark Software Factory thumbnail

· 15:51

Inside Kikimora: We Built a Dark Software Factory

The video details the concept of a 'Dark Factory'—an autonomous software development model where processes run without continuous human supervision. The shift was catalyzed by coding agents (like Claude Code) accelerating development speed, which exposed bottlenecks in traditional workflows. This led to building internal orchestrators (e.g., Kikimora, Night Shift) that automate tasks from issue creation (Linear) through code generation and PR management (GitHub), fundamentally changing the role of the engineer from primary coder to system architect and trust validator.

Key takeaways

  1. The Dark Factory Concept 2:05

    A dark factory is an autonomous software building process where no humans are required for supervision. The core workflow involves creating a Linear issue, which is then picked up by an autonomous agent that solves it and opens/manages a GitHub PR until merge.

  2. The Bottleneck Effect 3:23

    As coding agents increased development speed (starting around November), existing processes designed for slower software began to break down, forcing the company to adopt a fundamentally different, highly autonomous model.

  3. Shift in Engineering Value 11:20

    The value of an engineer shifts from writing code (which agents can do better) to understanding complex system constraints, business logic, and the overall interlocking technical architecture. Trust in the automated results becomes the critical skill.

Watch on YouTube Full article

You Can Hand One AI Agent Your Worst Recurring Task. It Cleared 60% Of Mine. thumbnail

· 21:16

You Can Hand One AI Agent Your Worst Recurring Task. It Cleared 60% Of Mine.

The video details a shift in AI automation strategy from merely speeding up customer service responses (2024/2025) to fundamentally eliminating the need for the support ticket itself by identifying and resolving root causes (2026). The speaker outlines a structured process: recording the full, manual pain points of a process, using AI to analyze these patterns across multiple systems (email, Slack, Stripe), automating the research and context gathering, while retaining human approval for actions involving access or money. This approach allows teams to transition from reactive support to proactive system improvement.

Key takeaways

  1. Shift Focus from Speed to Prevention

    The goal of advanced AI automation is not just answering tickets faster, but ensuring the underlying problem never has to exist (root cause elimination). The speaker notes that a successful implementation can drop support volume significantly, such as reducing 52 cases down to 19.

  2. The Process of Root Cause Analysis

    To automate effectively, one must first write down the entire process—every step, including manual labor and judgment calls—rather than relying on ideal or written procedures. This 'pain recording' is crucial for feeding context to AI.

  3. AI's Role in Context Aggregation

    Advanced AI agents are capable of aggregating context from disparate systems (email, Slack, Stripe, direct messages) and identifying patterns across multiple failure points. This capability is key to solving complex issues that were previously considered 'uniquely human misery.'

  4. Maintaining Human Oversight (The Guardrails)

    While AI can automate research and preparation, the speaker emphasizes keeping human approval for any decision involving access or money to maintain quality and prevent service degradation.

  5. Measuring Success (The Scorecard)

    After automation, success must be measured by tracking metrics: total cases received, resolved cases, breakdown by cause, number of drafts corrected, and the percentage fully automated. This allows for continuous improvement.

Watch on YouTube Full article