Earlier quoted context omitted.
> Microsoft has a history of monopoly behavior I just want to note that the case you link to was 25 years ago. The number of people working at Microsoft at the time who are still working there today is very small.
> I just want to note that the case you link to was 25 years ago. The number of people working at Microsoft at the time who are still working there today is very small. That's just a long way of calling Microsoft a bunch of monkeys :-) https://wiki.c2.com/?TheFiveMonkeys=
Copilot edited an ad into my PR
701–704 of 704 posts
Re: Copilot edited an ad into my PR
#702Earlier quoted context omitted.
Just to add to the feedback. No one, anywhere, ever wants this or anything like it. Do not inject anything that is outside of the context of the session, ever. This is how you get your software banned at large companies. Question for you, did anyone on the team really not push back? Does the team really think anyone wants ads in their copilot output? If the answer to both of these is no, you have a team full of yes m…
> did anyone on the team really not push back? This is the real question. If they are serious about not doing something like this again, they NEED to look at what process failed and let something like this get proposed, designed, implemented and pushed to production. Usually things get reviewed at each stage. Did the people who pushed back on this get steam rolled? If no one pushed back, that's an even serious cultur…
Re: Copilot edited an ad into my PR
#703A little bit off topic but our company recently enforced Microsoft Authenticator for account login. Which I was mildly annoyed about but now I'm super pissed off because they have started abusing the notification permission granted to allow authenticator to work to push out ads for Microsoft 365. It feels like we've gone back to 90s Microsoft when everyone hated them.
Re: Copilot edited an ad into my PR
#704Earlier quoted context omitted.
Telling someone you did something that you actually didn't do isn't a gray area, it's a lie. Using AI tools to code and then hiding that is unethical imo.
> Telling someone you did something that you actually didn't do isn't a gray area, it's a lie. Pre-LLMs, various helper tools (including LSPs), would make code changes to improve the quality of the code - from simple things like adding a const specifier to a function, to changing the actual function being called. No one insisted that the commit shouldn't have the human's name on it.
The gray area is in the gap of "how much" help is given. Does a tool that does most of the coding, thinking and implementation for you still count as your work if you gave it the goal, guidance and architecture? Yes. And what I want to know as the peer of the person using such a tool, call it AI, is to what degree it did the work and how much of it you validated.
Since the other tools pre-AI were more validated by the humans using them, I as the peer know the outputs pass a basic level of quality. I know the human was mostly involved in their production and creation. AI breaks this assumption and now many humans are producing outputs that require an unpredictable level of review by peers - as this is a big change in the norms of our society, I think its OK to call it out as a requirement to label output as AI-assisted/generated and/or to specify how much and how AI was involved and call it unethical if not done so. (I think it's not necessary or helpful to call out the use of the pre-AI era tools as unethical or a lie, even though they are too).