What changed when I stopped using SOL for everything in Codex

Описание и применение

<p>I’ve been developing web sites and applications for years, and lately Codex has become a pretty big part of how I work.</p> <p>At first my workflow was simple. Open the project, use SOL, explain what I want, let it inspect the code, implement the feature, run the tests, fix whatever breaks, and continue.</p> <p>It worked.</p> <p>The problem was that after a while I started noticing how much of SOL’s time was being spent on work that didn’t really require SOL.</p> <p>A difficult architectural decision? Sure.</p> <p>Trying to understand why a bug exists across several parts of the application

Задача

<p>I’ve been developing web sites and applications for years, and lately Codex has become a pretty big part of how I work.</p> <p>At first my workflow was simple. Open the project, use SOL, explain what I want, let it inspect the code, implement the feature, run the tests, fix whatever breaks, and continue.</p> <p>It worked.</p> <p>The problem was that after a while I started noticing how much of SOL’s time was being spent on work that didn’t really require SOL.</p> <p>A difficult architectural decision? Sure.</p> <p>Trying to understand why a bug exists across several parts of the application

Результат

<p>I’ve been developing web sites and applications for years, and lately Codex has become a pretty big part of how I work.</p> <p>At first my workflow was simple. Open the project, use SOL, explain what I want, let it inspect the code, implement the feature, run the tests, fix whatever breaks, and continue.</p> <p>It worked.</p> <p>The problem was that after a while I started noticing how much of SOL’s time was being spent on work that didn’t really require SOL.</p> <p>A difficult architectural decision? Sure.</p> <p>Trying to understand why a bug exists across several parts of the application

Доказательства

What changed when I stopped using SOL for everything in Codex

Источник