←back to thread

Google AI Ultra

(blog.google)
320 points mfiguiere | 1 comments | | HN request time: 0s | source
Show context
julianpye ◴[] No.44045838[source]
Why do people keep on saying that corporations will pay these price-tags? Most corporations really keep a very tight lid on their software license costs. A $250 license will be only provided for individuals with very high justification barriers and the resulting envy effects will be a horror for HR. I think it will be rather individuals who will be paying out of their pocket and boosting their internal results. And outside of those areas in California where apples cost $5 in the supermarket I don't see many individuals capable of paying these rates.
replies(6): >>44045887 #>>44045980 #>>44045988 #>>44046833 #>>44047069 #>>44063589 #
verdverm ◴[] No.44045988[source]
We just signed up to spend $60+/month for every dev to have access to Copilot because the ROI is there. If $250/month save several hours per month for a person, it makes financial sense
replies(3): >>44046043 #>>44046149 #>>44046196 #
tacker2000 ◴[] No.44046149[source]
How are you measuring this? How do you know it is paying off?
replies(2): >>44046269 #>>44046844 #
Aurornis ◴[] No.44046844[source]
$60/month pays off if it saves even an hour of developer time over a month.

It's really not hard to save several hours of time over a month using AI tools. Even the Copilot autocomplete saves me several seconds here and there multiple times per hour.

replies(1): >>44049580 #
kikimora ◴[] No.44049580[source]
But doesn’t it also waste a few seconds of your time here and there when it fails to autocomplete and writes bad code you have to understand and fix?
replies(1): >>44054926 #
1. verdverm ◴[] No.44054926[source]
Typically you have to confirm additions and cancellation is just a press of ESC key. Ctrl+z is available too.

Even when the code is not 100% correct, it's often faster to select it and make the small.fix myself than to type all of it out myself. It's surprisingly good about keeping your patterns for naming and using recent edits as context for what you are likely to do next around your cursor position, even across files.