Just when you least expected it, they will screw you.


 I was using Visual Studio Code with Gemini Code Assist to create a variation of an existing Python script. After a few minutes of back and forth, I got the desired code running. But when I try to run the same script again on the terminal, nothing happens. WTF? Thankfully, I asked Gemini to rebuild the file for me, and a few moments later, I got it back into my VSC editor. However, a minute later, the issue repeats itself. 

What good is it to have an IA to write code for you if the file content with the code disappears seconds or minutes later? And it's not that the file disappears, it is just that suddenly the file becomes 0 bytes long. When asked about it, Gemini hinted that, as I was working on a Dropbox folder, it might be a known synchronization issue of Dropbox. Knowing the possible cause of the problem helps, but being a paying customer of Dropbox makes me wonder if I want to keep on supporting them. This is not the first weird issue I have had with them, but other problems were happening on Linux on OSX; this time, it is in Windows.

I cannot rule out Git playing also a role here, as the problem was easily repeatable as long as the file was untracked, but once I added the file (being quick enough to commit before its content disappeared), the content of the file did not go away after I saved it from VSC.  The bottom line is that a five-minute IA thing turned into forty-five minutes of fighting with the computer. Computers will help us, they said.




Comments

Save Life said…
That sounds incredibly frustrating. It’s one thing to debug your own code, but quite another when the tools you rely on introduce new problems. The fact that the file drops to 0 bytes and then behaves differently once tracked in Git makes me think you uncovered a tricky interaction between Dropbox sync and VS Code’s save process. Even if Gemini pointed to Dropbox, as a paying user you shouldn’t have to deal with such reliability issues. Thanks for sharing this experience—sometimes these “edge cases” highlight how fragile our workflows can be when multiple tools (AI, editors, sync services, and version control) collide. It’s a bit like relying on a train ambulance during an emergency—you expect reliability, not surprises. Hopefully, your post helps others avoid the same pitfall.

Popular posts from this blog

VFD control with Arduino using RS485 link

Importing OpenSCAD designs into Onshape

Arduino mood light