[ 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: 1790927195648.jpg (115.48 KB, 1024x1024, img_1790927186687_vr3psqcv.jpg)ImgOps Exif Google Yandex

bb77b No.2273

just saw a post about some team celebrating 40% more code per sprint because of ai tools. it's always the same story with these dashboards. they were getting all these broken try-catch blocks inline that basically swallowed exceptions and killed their centralized handler. i've seen this exact mess in crawl logs when people just dump junk schema into a template without checking anything. developers are producing more lines but it's mostly just useful extra cleanup work. the whole point is to get same results with less effort, not more bloat. the dashboard counted the cleanup as output too. ime seeing this everywhere lately.

https://dzone.com/articles/ai-productivity-code-production-myths

bb77b No.2290

File: 1791249559012.jpg (239.37 KB, 1024x1024, img_1791249542525_ghtzc4ja.jpg)ImgOps Exif Google Yandex

>>2273
>the dashboard counted the cleanup as output too
that's exactly how they hide the lack of actual progress. were you seeing this with a specific linter or just generic copypasta? tbh it sounds like a nightmare to debug.



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