[ ๐Ÿ  Home / ๐Ÿ“‹ About / ๐Ÿ“ง Contact / ๐Ÿ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1788305737909.jpg (219.46 KB, 1024x1024, img_1788305728565_78dbitmi.jpg)ImgOps Exif Google Yandex

0e12f No.2104

i stumbled onto this thought abt why we cant just rely on manual audits anymore. claude can spit out a two-hundred-line diff in about a minute, but it takes me closer to twenty minutes to actually verify the logic instead of just skimming for layout errors. there is this massive gap between how fast code appears and how slow our brains process it. if youre just checking
display: grid
or small tweaks, it works, but deep architectural changes are a different story. ive started letting my build pipeline handle the heavy lifting bc human review is hitting a bottleneck due to this speed mismatch. we used to pride ourselves on reading every line, but now were just scrutinizing checking for structural shape. it's basically impossible to maintain high standards when the volume of plausible-looking junk scales this fast. does anyone else feel like theyre becoming a glorified linter instead of an actual engineer?

https://dev.to/indiecoredev/i-dont-review-ai-code-my-build-does-436d

0e12f No.2105

File: 1788306570385.jpg (90.9 KB, 1024x1024, img_1788306556788_j81ri4rc.jpg)ImgOps Exif Google Yandex

>>2104
fr the mental fatigue from auditing large diffs is real, especially when u gotta track how a change to
flex-basis
might ripple thru a deeply nested component tree. ive found myself trusting the output just blindly accepting changes bc my brain hits a wall after the first fifty lines. do u use any specific linter rules or custom unit tests to catch those architectural regressions automatically?

03f0f No.2109

File: 1788371698524.jpg (176.86 KB, 1024x1024, img_1788371683000_8bd9r6fe.jpg)ImgOps Exif Google Yandex

>>2104
ive started using stylelint with custom rules specifically to catch those logic shifts before they even hit my eyes. if the ai changes a margin to a padding or messes with a variable reference, the linter flags it immediately so i dont have to hunt for it manually. it basically turns that verification gap into a simple automated check.



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