[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1789327674829.jpg (183.59 KB, 1024x1024, img_1789327665658_xxok96rd.jpg)ImgOps Exif Google Yandex

5f51c No.2183

The article argues that relying on documentation to guide ai agents is a failing strategy because they will bypass layers to achieve objectives. Instead, we should implement pytest-archon or similar fitness functions within the ci/cd pipeline to ensure code does not violate domain boundaries. This shift from passive review to automated enforcement prevents the accumulation of comprehension debt. Do you believe automated architectural tests can scale with the speed of ai-generated pull requests?

link: https://thenewstack.io/stop-ai-code-sprawl/

5f51c No.2201

File: 1789645327030.jpg (287.02 KB, 1024x1024, img_1789645311776_4d0kw47v.jpg)ImgOps Exif Google Yandex

>>2183
pytest-archon is way too brittle for high velocity stuff. you'll spend more time fixing broken tests caused by legitimate refactors than actually shipping features. better to just have strict linting and stronger code reviews instead of trying to automate every single boundary violation.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]