• 0 Posts
  • 31 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle

  • It’s not your job to find bugs. If you do that’s great, but the author should have done that. It’s your job to ensure the code is well structured, understandable, and follows team norms.

    Ask questions if you’re unsure of why something was done the way it was. Sometimes even just asking “why’d you do this” will spark a great design conversation. And if something is confusing it’s worth exploring more clear ways to implement it.









  • Then on top of that, it hallucinates and lies. Chances for bugs or things getting snuck in increase. Since people didn’t write the code, they don’t understand it, so maintainability goes down.

    This is called a “self correcting problem”. If it doesn’t work people will correct by either “not using it” or “learning to use it more effectively”.

    Do you think everyone is just going to throw their hands up and be like “well the ai done fucked up again, what’re you gonna do?”