The Semi-Manual to Automated FDE Approach
yangyi · x · 2026-07-17
This post discusses an **FDE (Forward Deployed Engineer)** implementation sequence: **semi-manual first, then validation, and finally automation**. The core idea is to avoid fully automating a workflow from day one. Instead, run a basic, semi-manual process in a live business environment for a month to verify feasibility. Next, spend two months validating the loop's effectiveness. Only then should you productize the workflow into a SaaS or CLI for Agent automation, while accumulating data and adding visualization to mitigate hallucination risks. The author emphasizes that confirming a workflow's viability requires seeing **three aligned positive signals**; a single success doesn't prove a systemic advantage.
Related event: FDE Strategy: Semi-Manual Before Automation(2 posts)→
More from coding & agent
- The author says Codex reached 20x and is now debugging spec decoding on a hybrid parallel setup — TheZachMueller · 2026-07-21
- Axcess adds an MCP connector for WCAG accessibility checks that scanners miss — modelcontextprotocol · 2026-07-21
- X post asks whether Cursor Composer, built on Kimi models, would also be banned — max_paperclips · 2026-07-21
- A developer’s Codex usage is draining pooled enterprise credits at a small company — Distinct_Relation_62 · 2026-07-21
- Qwen Code ships cua-driver-rs 0.7.3 with relative coordinates and MCP filtering — github-actions[bot] · 2026-07-21
- Matt Pocock says every new codebase turns legacy within days — mattpocockuk · 2026-07-21