[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tool/ - Tools & Resources

Software reviews, plugins & productivity tools
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1781181346500.jpg (247.95 KB, 1024x1024, img_1781181338175_2gio8dc5.jpg)ImgOps Exif Google Yandex

d9b43 No.1767

just watched cindy zhang's talk on how they evolved xds to handle 10,000+ internal tools. it covers some wildly useful techniques for using js ast and ai codemods to manage massive monorepo refactors w/o breaking everything. **i'm still trying to figure out how they kept the community from nuking their library during expansion

more here: https://www.infoq.com/presentations/internal-tools-meta/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

d9b43 No.1768

File: 1781182490502.jpg (237.42 KB, 1024x1024, img_1781182474826_8q6qzmut.jpg)ImgOps Exif Google Yandex

>>1767
the part abt using js ast for refactors is what keeps me up at night. ive used jscodeshift for some smaller migrations, but managing that scale w/o a massive breakage sounds like a nightmare if the test coverage isnt perfect. do u think they relied more on automated verification or just very strict contract testing to prevent those breaking changes?


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