
What I like best about GitHub Copilot is how it speeds up everyday coding without feeling intrusive. It suggests code in real time as I type, and many times it correctly understands the context—whether I’m writing a function, API logic, or even test cases. This reduces a lot of repetitive work and lets me focus more on the actual problem rather than boilerplate code.
Another thing I appreciate is how well it integrates with editors like Visual Studio Code. The suggestions feel natural, and I don’t have to break my flow to search for syntax or examples. It’s especially helpful when working with new libraries or unfamiliar patterns—it gives a solid starting point which I can refine.
It also improves productivity during tight deadlines. Instead of writing everything from scratch, I can quickly generate drafts and then optimise them. Overall, it acts like a smart coding partner that saves time and reduces context switching. Análise coletada por e hospedada no G2.com.
What I dislike about GitHub Copilot is that its suggestions are not always reliable. Sometimes it generates code that looks correct at first glance but has logical issues or doesn’t fully match the requirement. You still need to carefully review and test everything, so it’s not something you can blindly trust.
Another drawback is context limitation. In large or complex codebases, it doesn’t always understand the full picture and may give suggestions that don’t align with project-specific patterns or architecture. This can lead to inconsistent code if not handled carefully.
It can also become a bit repetitive. At times, it keeps suggesting similar patterns even when you’re trying to implement something different, which can be slightly frustrating.
Lastly, there are concerns around code quality and dependency. Over-relying on it might reduce deep understanding, especially for junior developers. It’s a helpful assistant, but not a replacement for solid coding skills and design thinking. Análise coletada por e hospedada no G2.com.




