11–20 of 35 posts
That’s a fun take on a real issue, but… > Your code is only sent to the model provider (OpenAI) When has this become an acceptable « privacy » statement? I feel we are reliving the era of free mobile apps at the expense of harvesting any user data for ads profiling before GDPR kicked in…
That’s a fun take on a real issue, but… > Your code is only sent to the model provider (OpenAI) When has this become an acceptable « privacy » statement? I feel we are reliving the era of free mobile apps at the expense of harvesting any user data for ads profiling before GDPR kicked in…
That's not the privacy statement though. I feel like we're reliving the era of RTF... oh wait, we never left.
So yes this is the second part of the privacy statement
I would probably be putting devs on a pip or firing them if they failed these quizzes often...understanding your own prs is the bare fucking minimum, even without AI help.
> AI Agents are starting to write more code. How do we make sure we understand what they're writing? This is a good question, but also how do we make sure that humans understand the code that _other humans_ have (supposedly) written? Effective code review is hard as it implies that the reviewer already has their own mental model about how a task could/would/should have been done, or is at the very least building thei…
If someone were to submit this code for review:
getUser(id: number): UserDTO {
return this.mapToDTO(this.userModel.getById(id));
}
Just submit a PR that removes the action so it doesn't run on the branch before the merge! If devs aren't reviewing the code anyways, will they even catch that kind of change?
Just submit a PR that removes the action so it doesn't run on the branch before the merge! If devs aren't reviewing the code anyways, will they even catch that kind of change?
You could set up some hardcoded rules so that the PR is never merged without human review if it touches the github actions.