This Perplexity AI Bug Ruins Your Code (C# Field Naming Problem)

In this video, I demonstrate a critical issue with Perplexity AI when used for software development — especially in C# projects. If your codebase follows the common convention of using underscores (_) for private field names, you might run into a frustrating problem. When Perplexity rewrites or updates your methods, it often removes or ignores underscores, leading to compilation errors when you paste the code back into Microsoft Visual Studio. I walk you through a real example where: A method is rewritten using Perplexity AI The updated code looks correct at first glance But after pasting, multiple errors appear due to missing underscores in field names This means developers have to manually fix each field — which can be time-consuming and error-prone. 🔍 What you’ll learn: Why this issue happens when using Perplexity AI How it affects C# field naming conventions Practical ways to avoid or minimize the problem Whether you should change your naming conventions or adjust your prompts If you're using AI tools like Perplexity for coding, this is something you need to be aware of to avoid breaking your workflow. 💬 Have you faced similar issues with AI-generated code? Share your experience in the comments! 🔁 Don’t forget to like, share, and subscribe for more real-world insights on AI in software development. #PerplexityAI #CSharp #DotNet #Programming #AIForDevelopers #VisualStudio #CodingTips