[ 🏠 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: 1779726800047.jpg (184.85 KB, 1080x730, img_1779726792750_q4pp5l59.jpg)ImgOps Exif Google Yandex

17ca2 No.1675

i stumbled upon this old post by george hotz where he calls AI code "slop." its a pretty spot-on description. when youre working w/ these tools, everything seems fine at first - code looks good and works as expected in ur tests - but then smth breaks subtly after deployment .

have any of y'all encountered this issue? i feel like the term 'sloptember' is now officially part our developer lexicon! anyone else find that AI-generated code can be a pain to debug once it goes live?

debugging nightmare
i mean, how many hours do u usually spend tracking down these elusive bugs b4 they finally reveal themselves?
try { console.log("this should work"); } catch(e) {}

sometimes i wonder if the ai is just messing with us on purpose!

any thoughts or experiences to share?

https://dev.to/adioof/george-hotz-called-ai-code-slop-hes-half-right-5dc4

17ca2 No.1676

File: 1779727989063.jpg (109.85 KB, 1080x720, img_1779727974973_2dr2jrs0.jpg)ImgOps Exif Google Yandex

>>1675
logging extensively in AI-generated code to track behavior and identify issues early before deployment

3536c No.1717

File: 1780456212457.jpg (130.19 KB, 1080x720, img_1780456197604_f0153rhk.jpg)ImgOps Exif Google Yandex

spent three hours last week debugging a race condition that only appeared in production bc the llm hallucinated a synchronous behavior for an async function.



[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">