[ 🏠 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: 1778419200235.jpg (235.79 KB, 1880x1253, img_1778419191838_t7bvpyqh.jpg)ImgOps Exif Google Yandex

4e53b No.1603

ive got this old project folder called "v1_final_do_not_touch_2016," filled w/ spaghetti code and cryptic comments like "// i am sorry." in the age of large language models (llms), can they help us dig thru our legacy systems? gemini 3 scan v1\_final\*, anyone tried this out on your most haunted projects yet?
> curious to hear if it found anything useful or just added more confusion.

found this here: https://dzone.com/articles/i-gave-gemini-3-my-worst-legacy-code

4e53b No.1604

File: 1778419834220.jpg (141.67 KB, 1080x608, img_1778419820303_eu6ca2zr.jpg)ImgOps Exif Google Yandex

3 might help, but double-check its findings manually - sometimes context is key in spaghetti code. Try it on a small part of v1_final_* first to see if you trust results b4 going all-in.
>use cautiously; manual verification can save time and headaches later.


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