Please wait...
No, that isn't the reason. the reason is that it is helpful in several areas. One of them is saving me time with coding, or finding bugs. Forgetting the time required for me to 'plan', It can do things faster than i can type.
Not to mention image and music generation.
Fri May 22 2026 15:09:02 EDT from zelgomerThe only reason you don't is because you think it's "AI."
Google: "We've created a brand new tool for you, that will require you to build an entirely new workflow!"
Also Google: "Your existing tools will stop working in four weeks."
I think I'm going to like the 'agy' (antigravity) command line toolset way better than the Code Assist plugin for VS Code, but geez guys, just one month for the whole world to change their workflows? I guess one month is an eternity in the world of AI.
Here lately, it is.
Speaking of, another album went up this week on YT.
I guess one month is an eternity in the world of AI.
So i have a minimal ( tiny ) windows 11 VM to access VDI since where i work, they are butt-heads and turned off Linux and web access ( and ChromeOS )
I ended up installing a 3rd party browser ( with tiny, you get nothing ) so that i could login, as it needs a web browser to do authentication. Worked fine for the last year or so. At some point installed chrome so i could flash a recovery USB for ChromeOS ( flex ). ( now i can find official images to burn directly, so its not needed. "Recovery" wont work on Linux, only windows, which is really odd.
I still use the 3rd party one as it ignores the "don't save password" nonsense on the login for the VDI stuff. Saves me a (small) step. Today, im now getting popups "don't you want to use chrome instead"
Really google? That is a move Microsoft makes..
agy just sits there in the console and you interact with it, and it just goes and does what you tell it to, asking for permission to open files, run commands, etc. as it needs to. Paired with neovim in another terminal window it's getting the job done quite well.
And I found a use for AI code assistance at the opposite end of the spectrum from where it is usually applied. Over the last couple of days I've been giving it some of my oldest, sloppiest code and having the thing clean it up. Reindentation, refactoring to remove ugly loops, more meaningful variable names, removal of dead code and variables, the works. It's really quite nice in that area. It's better than using AI to replace the human in writing code from scratch (which generates slop) or rewriting it in Rust (which contaminates the whole world).
Whether it's new code or reworking old code, I'm working in small, incremental, understandable scopes. And when doing so on a well established code base, it writes code the way I would write it.
Right, the same way people should code, in my opinion anyway. Draft up requirements and put a stake in it. Get the data dictionary in order. Get the overall flow documented by breaking it all up into small functional pieces. Cover your wall with the design chart and data flows.. then start working.
Whether it's new code or reworking old code, I'm working in small, incremental, understandable scopes.