Comment by svick
18 days ago
You don't want them to experiment with new tools? The main difference now is that the experiment is public.
18 days ago
You don't want them to experiment with new tools? The main difference now is that the experiment is public.
It's pretty obviously a failed experiment. Why keep repeating it? Try again in another 3 months.
The answer is probably that the Copilot team is using the rest of the engineering organization as testers. Great for the Copilot team, frustrating for everyone else.
> It's pretty obviously a failed experiment
For it to be "failed" it would have to also be finished/completed. They are likely continuously making tweaks, this thing was just released.
"This thing has just released"
"It would have to be finished/completed"
Do you honestly not see a problem with those two statements in such close proximity? Is it finished or is it released? The former is supposed to be a prerequisite for the latter.
3 replies →
I wouldn't necessarily call that just an experiment if the same requests aren't being fixed without copilot and the ai changes could get merged.
I would say the copilot system isn't really there yet for these kinds of changes, you don't have to run experiments on a language framework to figure that out.
By all means. Just not on one of the most popular software development frameworks in the world. Maybe that can wait until after the concept is proven.
Yeah, seems to me that breaking .NET with this garbage will be, uh, extremely bad
Nah I'd prefer they focus on writing code themselves to improve .NET not babysitting a spam-machine