Lou SaccoCTODaisyHealth
Startup engineering. About a month of near-daily use. WebStorm with TypeScript and NestJS microservices.
DaisyHealth's CTO Substack, published Read the write-up (opens DaisyHealth's CTO Substack in a new tab)
Observation
DaisyHealth's CTO used Junie to take test coverage on complex modules from zero to nearly complete.
- Takeaway
- Use Junie for discrete tasks and tests, start a fresh session without stacking prompts on a flawed first attempt, keep rollback in reach, and review for framework conventions the agent skips.
- What happened
- After a month of near-daily WebStorm use, Sacco reports gains in unit tests and understanding unfamiliar services, including onboarding. Junie raised coverage on some complex modules from 0% to nearly 100% in a few sessions. It also built a custom cache from scratch, ignoring NestJS's cache-manager, and lost direction in long prompt windows.
- Public engineering write-up
- Results reported by the author
- Model named
Deployment details
Startup engineering. About a month of near-daily use. WebStorm with TypeScript and NestJS microservices.
- Public engineering write-up
- Results reported by the author
- Model named
- Duration
- About one month of near-daily use
- Workload
- JavaScript and TypeScript services, including NestJS microservices
- Product version
- Junie in WebStorm, upgraded from AI Pro to AI Ultimate
- Model
- Claude Sonnet 3.7, then Junie's default, with Sonnet 4 available
- Measurement
- Code coverage before and after on selected modules