I’m a developer working on a fairly complex hybrid stack: Django backend, Next.js frontend, and an Electron desktop client. Over the last year, I’ve undergone a total shift in how I work. I started with small AI-assisted tasks, but as my confidence grew, I moved to a fully agentic flow. Honestly? I haven’t manually written a line of code in over 6 months . My workflow now looks like this: Refinement: I spend my time “co-thinking” with the agent—honing user stories and requirements. Architecting: We define the high-level design together. I grill the agent on its plan until I’m satisfied. Execution & Review: I launch the agent. I don’t review the code myself, I use a separate “reviewer” agent for that. Learning Commit: Once a feature is merged, I have a specific step where the “knowledge” gained (new patterns, API changes, logic quirks) is absorbed back into the master context/documentation so the agent doesn’t “forget” how we do things in the next session. Here’s my problem: While agents are incredible at unit and API tests, they consistently struggle with the visual and state-heavy complexity of E2E. They’re both dead slow and create brittle/sometimes incorrect test scripts. Ironically, because I’m shipping so much faster now, I’ve become the manual bottleneck. My role has shifted from SWE to “Agent Orchestrator & Manual QA Tester.” I’m either clicking through flows myself or spending my saved “coding time” wrestling with Playwright scripts. Questions for others running agentic workflows: Does your role feel more like a PM/QA Lead than a SWE lately? Are you also finding that E2E is the “final boss” for agents? Have you found a way to automate the creation of reliable Playwright/Cypress tests using Claude or other agents? submitted by /u/arik-sh
Originally posted by u/arik-sh on r/ClaudeCode
You must log in or # to comment.