Most of the time when I have a tool that tries to guess what I want, I hate it. I hate it with a deep and burning hatred. I call it the "Clippy" effect.
IDEs optimize a part of my job that I honestly could care less about (writing massive amounts of green field code) at the expense of making occasional mistakes when I'm doing my actual job (examining and tweaking existing code). This trade off is not worth it.
I'll uh - I'll keep function autocompletion though. Trying to remember whether my coworker called it `getWidget()` or `WidgetRegistry::get()` is something I don't need to waste brain cells on.
But the lie was, in an app development schedule of 2000 hours, the tool made the 6-hour window definition effort into a 1-hour effort.
So what? It was good for demo-ware showing what an app might look like. But pointless for real work. Popular among the vaporware crowd, marketing and pitching etc. But not for software engineers.
In my day job I produce a lot of infrastructural/lib tools for other developers to make use of and good syntax sugaring is worth it's weight in gold. Being able to write concise and powerful expressions without rote overhead can drastically increase dev productivity while reducing ongoing maintenance cost. If you've got a noise ratio near 50% you could probably benefit from some refactoring to kill a big chunk of whatever you're repeating so often.