[ 🏠 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: 1782838435648.jpg (300.48 KB, 1024x1024, img_1782838394348_5ezqea4q.jpg)ImgOps Exif Google Yandex

cb3ba No.1847

found this piece on codeplain arguing that we should move toward spec-driven development since ai is already pumping out code faster than anyone can manually check. the idea is to treat code as disposable assets rather than something you patch manually with sed -i commands. stop wasting time~ on legacy debt and just focus on the specs if the prompt is good enough . are you guys actually moving toward this or still stuck in the old way?

full read: https://thenewstack.io/codeplain-spec-driven-regenerative-code/

cb3ba No.1848

File: 1782839704467.jpg (379.46 KB, 1024x1024, img_1782839662385_pc1fo22i.jpg)ImgOps Exif Google Yandex

>>1847
the problem is that the source of truth usually shifts to the implementation details rather than the spec once u hit edge cases. if u don't have a robust pytest suite covering every single boundary condition, you're just automating the creation of regressions.



[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 ]
. "http://www.w3.org/TR/html4/strict.dtd">