Senior Developer's 34-Day Claude Code Project: Solid Engineering, Critical Blind Spots

Project Overview

A senior tech executive with 35+ years experience (VP Engineering, CIO, Head of Software Engineering roles) used Claude Code for a solo project over 34 days. The developer acted as product owner, architect, and team lead while Claude wrote all the code.

Technical Results

The project generated 300+ commits in 34 days. Both Claude and ChatGPT independently reviewed the codebase and found:

• Clean architecture with solid separation of concerns
• Good test coverage (272 tests)
• Thorough documentation described as "exceptional relative to the project's stage"
• Architecture that was "not aspirational; it is implemented"

Project Management Approach

The developer created a CLAUDE-md file with working rules for managing the AI assistant, including:

• Never describe code without reading it first
• Never advance without permission
• Diagnose before fixing

This management document was called "one of the best AI coding assistant management documents I have seen" by reviewers. Managing Claude Code felt like "managing a very fast, very literal junior developer."

The Project: Document Conversion Pipeline

The project was a complex document conversion pipeline with five stages:

1. Extract content from web pages
2. Sanitize content
3. Parse into structured model
4. Render as accessible HTML

The original concept was a CLI and library for developers to embed in their apps.

Critical Missed Opportunity

The developer knew about Firefox's Reader Mode extraction engine (Readability.js) but never asked: "is this also a standalone library I could use?" Instead, they viewed it only as a browser feature. This single question would have revealed that:

• The hard part was already solved
• The real value (typography, themes, accessible output) could be a browser extension on top of an existing engine

Neither the developer nor Claude surfaced this alternative approach, despite the developer's own engineering rule: "never build something if a solution already exists."

User Interface Pivot

The target users (parents, teachers, students) couldn't use a CLI or pipeline. The developer initially tried a simple HTML test page for feedback, but then built a full web interface:

• 100+ commits in eight days
• Five themes
• Responsive design
• Branding and deployment

This interface became the product instead of just a feedback mechanism.

Testing Infrastructure Expansion

The project developed extensive testing infrastructure:

• Evaluation harness with 16 quality metrics
• Benchmarks against 4,000+ web pages
• Comparison pipeline
• Screening tool

The cumulative effect was "five lines of testing infrastructure for every one line of product."

Developer Experience

The developer reported: "Working with Claude Code felt like managing a team again. Brainstorming to unblock problems, making architectural calls, watching things come together at speed. It was like having the Justice League writing my code."

However, this created a trap: "Every time I had a nagging doubt about whether I was on the right path, I could push it aside by building something else impressive. The quality of the work became its own justification for continuing."

User feedback was only collected on day 30 of 34.