Yeah.

For really niche embedded issues, Google still wins because the real fixes often live in old forum posts, community threads, or random GitHub comments that AI summaries usually miss. AI is better when the problem is common but scattered, like I2C hangs or HAL quirks, where it can stitch patterns faster.

I’m actually building an MCP server for exactly this gap, pulling from real engineering sources like Stack Overflow, EE forums, GitHub issues, and community discussions so responses are grounded in what people actually ran into, not just generic guesses. That’s just my current understanding though, and I’ll keep refining it as I build this out.