I have not had a chance to test the office integrations (and the $30 price tag may keep it that way,) but I’ve been testing the web chat version, and once toggled to “precise” mode I find it close to chatgpt. Just a little more prone to lapse into acting like a bing chat app and very limited in conversation length…
I think the trick is to treat it like a junior assistant or maybe an intern who might make mistakes and not as a seasoned, experienced employee who always puts out perfect work.
$30? Idk how it is in the consumer space, but in the Enterprise world the initial opening for copilot required 300 seats of E3 or better, and then a purchase of 300 seats of copilot 365 at $30 each. They were supposed to drop the 300 copilot 365 seat req q1 but I’m not sure if they did.
3030012=108,000 per year for copilot. E3 is 36 a month, 30012=129,600.
Big money.
I’m told they dropped the seat requirements. Yeah $30 is the business rate. No discounts for education. I suspect the backend costs on this are still rather high but should improve once hardware catches up to demand.
Ah. Well as far as I was told two months back, they didn’t plan on dropping the E3/E5*300 seat requirements, only the 300 seat of copilot requirements. But I haven’t kept on top of it, all my companies clients are too small fish to drop 100-200k a year on unproven tech
From what I’m told, Ms was basically running things at a loss when they first opened the doors.
So people are surprised that GPT-4 is performing as well as GPT-4 always has?
Copilot isn’t GPT4, as far as I know. GPT4 hallucinations are quite minimal.
Copilot isn’t actually bad for developers, it’s just that you need to be careful with it and recognize its limitations.
Writing a bunch of REST endpoints for an API and need to implement all the typical http verbs, and you already have all the matching methods for reading, updating, and deleting values in a complex SQL database for each endpoint to call? Copilot can turn a ten minute chore into a ten second one. Very handy.
Writing those complex SQL methods in the first place? Yeah… Copilot will probably make a ton of mistakes and its work will need to be triple-checked. You’ll save time just doing it yourself if you know how. (And if you don’t, you have no business calling yourself a developer.)
Copilot is best for easy boilerplate and repetitive code. Problems arise as soon as you ask it to get “creative.”
Copilot isn’t actually bad for developers, it’s just that you need to be careful with it and recognize its limitations.
Is it me or is this a weird statement for what’s supposed to be an exact science?
Imagine working in construction and using a level and you’re told “it’s not that it’s a bad level, you just gotta be careful with it”.
How much margin for error should we allow for getting our code right? Is it now acceptable if we only get 80% right?
It’s more like you get some kind of weird construction multitool that promises to be a level, a drill, a hammer, and a dozen other things, and it turns out to be a really good, innovative, and helpful level… and a really bad everything else.
This is about the other copilot.
microsoft and its names… like the VS editor and the other VS editor.
Yeah, I figured that out eventually, but also figure the same probably applies to the other Copilot. Same underlying technology.
Wish Microsoft would use different names for different implementations.
