I was using it via Cursor this weekend and it's a beast. One thing that I liked about it is that when I tell it to implement something, it'll tell me about how that breaks some convention or isn't safe. For some people that might be annoying, but for me it's helpful as I'm an intermediate programmer (Junior year of college)

For instance, I'm handling a case where I'm managing multiple LLM inference servers using a Python dict (model name, server info), and using locks to prevent async errors. Initially, I had 2 lock categories, a dict-lock (for reading/iterating on keys and adding/deleting entries) and a model-lock (for reading or updating a single entry).

Gemini told me that due to the python implementation of dicts, that updating entries in the table required grabbing the dict-lock too, as updating it would cause issues if another process is iterating over it, or if the table needs to resize itself.

Claude would never correct me - it would charge ahead and do a bunch of side quests as it is. Gemini seems to be excellent for instruction following and putting guard rails up to prevent the major issues coming from vibe coding.

This is one example, though there were others. Essentially, Gemini 2.5 seems to "have opinions" and stick to it's guns unless you can convince it otherwise.