https://pvolkov.com/en/Recent content on Technical ArticlesHugoen-USSun, 16 Aug 2026 00:00:00 +0000https://pvolkov.com/en/articles/sdd-in-production/Sun, 16 Aug 2026 00:00:00 +0000https://pvolkov.com/en/articles/sdd-in-production/<p>In Findrates.ai, <strong>Agentic SDD</strong> (autonomous spec-driven development) runs every day: we have closed over 240 plans through this pipeline. Our actual process differs significantly from conference slides where classical SDD is presented as an effortless silver bullet.</p> <h2 id="the-limits-of-vibecoding">The Limits of Vibecoding</h2> <p>With the rise of LLMs, developers initially relied on &ldquo;vibecoding&rdquo;—prompting a chatbot to &ldquo;build feature X.&rdquo; For quick scripts and prototypes, this was enough. On an existing codebase, however, vibecoding quickly caused loss of context: models forgot constraints between sessions, broke neighboring modules, and generated unmanaged technical debt.</p>https://pvolkov.com/en/articles/digital-employee-18-days/Wed, 05 Aug 2026 00:00:00 +0000https://pvolkov.com/en/articles/digital-employee-18-days/An owner&rsquo;s report after 18 days: how an autonomous employee runs on schedule, closes its own hypotheses, catches its own mistakes, and stops where the decision belongs to a human.https://pvolkov.com/en/articles/claude-codex-concierge/Fri, 31 Jul 2026 00:00:00 +0000https://pvolkov.com/en/articles/claude-codex-concierge/A practical breakdown of a personal AI concierge for Claude Code and Codex: how it understands incoming requests, resumes the right sessions, tracks assignments, and returns results.https://pvolkov.com/en/articles/autonomous-digital-employee/Tue, 21 Jul 2026 00:00:00 +0000https://pvolkov.com/en/articles/autonomous-digital-employee/A practical breakdown of an autonomous digital employee: schedule, authority, memory, engineering intuition, a research pipeline, and risk boundaries.https://pvolkov.com/en/articles/ai-tech-teams-workflow/Thu, 09 Jul 2026 00:00:00 +0000https://pvolkov.com/en/articles/ai-tech-teams-workflow/A practical breakdown of a system of autonomous AI engineering teams: roles, task queue, QA, audit, retrospectives, and the release loop.https://pvolkov.com/en/about/Mon, 01 Jan 0001 00:00:00 +0000https://pvolkov.com/en/about/<p>This is the public home of my technical writing.</p> <p>Here I document practical engineering systems: autonomous AI teams, product development, QA, releases, infrastructure, and repeatable workflows.</p> <h2 id="author">Author</h2> <p><strong>Pavel Volkov / Павел Волков</strong> — AI architect and engineer.</p> <ul> <li>LinkedIn: <a href="https://www.linkedin.com/in/psvolkov/">psvolkov</a></li> <li>GitHub: <a href="https://github.com/ak40u">ak40u</a></li> </ul> <h2 id="how-to-read-these-articles">How to Read These Articles</h2> <p>The articles here are long and practical. You can read them as breakdowns of how a system works: roles, boundaries of responsibility, checks, logs, retrospectives, the release workflow, and infrastructure decisions.</p>