Re:Microsoft Cancels Leases for AI Data Centers, Analyst Says
by vel0city on Monday February 24, 2025 @12:48PM
(#43162517)
I've been using Amazon Q Developer as it was provided and approved by my employer. It has been pretty good with Python codebases, Kubernetes configurations, and (not surprisingly) CDK/Cloudformation templates. I can pretty much just ask it "here's my python script, make everything I need to run it as a lambda, hook that lambda up to x, it should run in a vpc defined in this template over here", and it'll get all that stuff put together and its normally pretty solid code it generates. It seems to pull in a lot of the context of the project I have open. For instance, I can say "it should get those values from the outputs in other-cf-template.yml" and it knows the naming schemes and what not across templates, even if it didn't generate those templates.
I might go back and tweak some stuff, add some extra tags and what not, but often its pretty good at doing what I ask.
Sometimes its suggestions aren't what I was really wanting to do in my codebase, a handful of times it has made up methods or parameters of even well-known libraries. But usually, its suggestions are better than a basic IntelliSense-style autocomplete at least in my experiences.
I haven't used many of the other developer assistant plugins like say GitHub Copilot. I couldn't really say which is better or worse. But I do think using Q Developer has made me faster in many tasks.
I wouldn't expect a tool that doesn't have access to the context of my editor and the files I have open to be very useful for actually coding. There's a lot of context to understand in even a basic application. If you're just asking a locally running app in ollama "give me a method to do x", don't be surprised if it doesn't know everything else happening in your app. Maybe it'll give you a halfway decent example of doing something, but devoid of how it actually plugs in to whatever you're making it might be entirely worthless.
I might go back and tweak some stuff, add some extra tags and what not, but often its pretty good at doing what I ask.
Sometimes its suggestions aren't what I was really wanting to do in my codebase, a handful of times it has made up methods or parameters of even well-known libraries. But usually, its suggestions are better than a basic IntelliSense-style autocomplete at least in my experiences.
I haven't used many of the other developer assistant plugins like say GitHub Copilot. I couldn't really say which is better or worse. But I do think using Q Developer has made me faster in many tasks.
I wouldn't expect a tool that doesn't have access to the context of my editor and the files I have open to be very useful for actually coding. There's a lot of context to understand in even a basic application. If you're just asking a locally running app in ollama "give me a method to do x", don't be surprised if it doesn't know everything else happening in your app. Maybe it'll give you a halfway decent example of doing something, but devoid of how it actually plugs in to whatever you're making it might be entirely worthless.