Deschide articolul original într-un tab nou Schimbarea acestei opțiuni se aplică imediat și reîncarcă pagina.
LECTURA
← Înapoi la Urmăritori

Inversion of Coupling Control

blog.officefloor.net/feeds/posts/default
Vizitează site-ul

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 25

  1. The refactor run halfway

    (Inversion of Coupling Control)

    The last post set up a ladder.

  2. We told the AI about the Change Impact

    (Inversion of Coupling Control)

    A series on how software architecture shapes AI-driven code degradation.

  3. Telling the Agent the Cost Function

    (Inversion of Coupling Control)

    Preprint / cs.SE / Empirical Software Engineering Telling the Agent the Cost Function Two architectures.

  4. I took the metric away

    (Inversion of Coupling Control)

    The last two posts did one thing.

  5. We Gave the Agent the Metric

    (Inversion of Coupling Control)

    A series on how software architecture shapes AI-driven code degradation.

  6. Give the AI the formula: prompting or architecture?

    (Inversion of Coupling Control)

    In the last experiment I held the coding agent fixed and changed only the architecture.

  7. Change Impact in the Wild: A Defect Predictor Undone by File Size

    (Inversion of Coupling Control)

    Preprint / cs.SE / Empirical Software Engineering Change Impact in the Wild Twenty repositories.

  8. We Tested Our Complexity Metric Against Real Bugs. File Size Won.

    (Inversion of Coupling Control)

    Some files attract bug fixes over and over.

  9. The Same Complexity. One Unit or Twenty-Two.

    (Inversion of Coupling Control)

    A series on how software architecture shapes AI-driven code degradation.

  10. The Cold Reader Understood Spring Better

    (Inversion of Coupling Control)

    A series on how software architecture shapes AI-driven code degradation.

  11. Tests Are Not How the AI Gets It Right. They Are How You Find Out It Didn't.

    (Inversion of Coupling Control)

    A series on how software architecture shapes AI-driven code degradation.

  12. We Showed the Agent Every Test. It Wrote the Same Code.

    (Inversion of Coupling Control)

    A series on how software architecture shapes AI-driven code degradation.

  13. The Test Suite Crashed. The Harness Called It Regression

    (Inversion of Coupling Control)

    A series on how software architecture shapes AI-driven code degradation.

  14. Think a Better AI Would Change the Result? The Experiment Is Yours to Run

    (Inversion of Coupling Control)

    Every time I publish results from the architecture-degradation experiment, the same objection arrives.

  15. The Metrics, Revisited

    (Inversion of Coupling Control)

    A companion to the series on how software architecture shapes AI-driven code degradation.

  16. Adding Features Is Easy. Changing Them Is the Test.

    (Inversion of Coupling Control)

    Fifth in a series on how software architecture shapes AI-driven code degradation.

  17. Measuring the Blast Radius of Change

    (Inversion of Coupling Control)

    Fourth in a series on how software architecture shapes AI-driven code degradation.

  18. Complexity Is Not the Metric. Cohesion Is.

    (Inversion of Coupling Control)

    Third in a series on how software architecture shapes AI-driven code degradation.

  19. Architecture as the Independent Variable, Run 2: The Signal Was Real

    (Inversion of Coupling Control)

    The anchor post for a series on how software architecture shapes AI-driven code degradation.

  20. Why "Erosion" Washed Out: The Leaf-Function Trap

    (Inversion of Coupling Control)

    Second in a series on how software architecture shapes AI-driven code degradation.

  21. AI graded its own homework

    (Inversion of Coupling Control)

    A confound in measuring AI code degradation, and why we deleted every test to fix it.

  22. God Methods, Small Functions, and Who Gets to Maintain the Code

    (Inversion of Coupling Control)

    Early notes from an experiment that holds the AI fixed and lets the architecture vary.

  23. Beyond the Source. When an AI Coding Agent Searches Outside Your Project

    (Inversion of Coupling Control)

    I gave a coding agent one task and one directory.

  24. Mutation of existing logic showing to cause erosion

    (Inversion of Coupling Control)

    The redesigned PetClinic-Evolve experiment has produced its first complete run of each architecture.

  25. Improvements to experiment: more checkpoints, mutative checkpoints, blind regression measurements

    (Inversion of Coupling Control)

    This is a between experiments post.