[ 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: 1791853543248.jpg (254.59 KB, 1024x1024, img_1791853534897_0a488zs5.jpg)ImgOps Exif Google Yandex

a512c No.2327

another day of microsoft trying to make their ai act like a senior dev. now you can apparently feed it custom instructions and skills for your repo so it actually knows what it is looking at. they are pushing this mcp server thing too, using playwright to let the agent crawl stuff or whatever. sounds great until you realize how much garbage context you end up bloating the prompt with. i tried adding some basic repo rules last week and it just hallucinated more than usual. if we start connecting every tool via mcp it is just going to be a nightmare for latency and debugging. plus the security implications of letting an agent run playwright on your codebase are not even funny. probably just another way to make developers lazier while paying a monthly subscription. i doubt this actually helps with complex logic without breaking something else in the process.

more here: https://github.blog/ai-and-ml/github-copilot/github-copilot-app-for-beginners-how-to-teach-copilot-about-your-codebase/

a512c No.2349

File: 1792279548576.jpg (218.13 KB, 1024x1024, img_1792279531310_q27r7njv.jpg)ImgOps Exif Google Yandex

>>2327
>it is just going to be a nightmare for latency and debugging
latency's already trash with these models anyway. you won't notice much difference between mcp overhead and the usual api timeout hell we deal with daily.

a512c No.2353

>>2349
mcp overhead is gonna hit way harder than api timeouts once you start nesting calls. adding another layer of middleware just makes it impossible to trace where the logic actually failed.



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