• 2 Posts
  • 138 Comments
Joined 3 years ago
cake
Cake day: July 10th, 2023

help-circle








  • You must work in dreadful places. I’ve seen it a few times, but most places have been productive.

    It needs a good lead dev to set the culture though.

    Whitespace change debates can be avoided by using rule sets in IDEs and agreeing standards within the team.

    Good static code analysis tools in pipelines and IDEs handle most technical issues leaving reviewers to focus on design, maintainability, clarity and readability.

    You can avoid pickiness if you communicate why, so they learn and understand. If you use PRs as a training and learning tool they’re quite productive. If not sure, ask why something was done.

    And if you get picky comments respond with “personal preference and not part of team rules”. But also, you cannot be defensive in your PRS. You have to be open to feedback and points and happy to discuss. Be polite even when feedback is invalid. Defendivesness kills constructive feedback and no matter how old you are and how long you’ve been doing it, you can still improve. Oh and if you been doing it that long, you’re a senior or lead and can influence how things are done.










  • I watched. He used a prompt with exact wording from an example and obviously it’s the most logical continuation, so AI would generated it. We know how they’re trained. But how many open source prompts will start with exact code and comment? Unlikely to ever happen in real world. So unlikely to he direct infringement. Someone could easily sue the AI companies with these examples to prove it infringes copywrite work, but then govs are going to protect them so it won’t happen.

    It’s unlikely to get identical output without intention, but it’ll also take the infringed actively taking steps to sue that case. Stastical likelihood of this happening in real world is low.

    I’m with you in wanting to watch the AI industry collapse. But I’m unfortunately in a minority without the lobbying power, so it won’t happen.



  • They can. They just need to find the first instance of AI, branch from the commit before and start with that as a basis for master. Then push that branch to their own remote.

    If someone cannot do that, they probably aren’t competent enough to maintain a project of this importance. They can then cherry pick commits that are good and merge those. Or request others recreate new PRS with them with correct attribution. It’s tedious, but easy.

    Maintainership isn’t fun. The hardest problem is finding someone that cares enough to take it on. Many would give advice if someone was willing.

    Sounds like Lutris dev was burnt out, so it would probably quickly replace it.