Here is the proposed addition for the ToU that @Gusted and I agreed on post-assembly for the upcoming membership vote. 🙏
The discussion for this proposal is available for Codeberg e. V. members in the forum: https://forum.codeberg.org/d/139-resolutions-for-assembly-on-codeberg-taking-a-stand-a...
Why though? Aside from blind hate, good written JIRA stories are almost oneshot now in many occasions. You can spend more mental energy on logic correctness rather than translation of requirements into code.
Not only it is faster, but you can deliver greater quality faster. Slopware is a result of trying to crank the dev speed to the max without following proper sdlc with proper dod.
Very cringe thing to do when the whole industry jumps on LLM-automation wagon. This way you filter out people who actually do stuff professionally.
Good to know though. Would avoid.
The only acceptable use in the industry is using it as a code analysis tool - vibe-coding is not.
Why though? Aside from blind hate, good written JIRA stories are almost oneshot now in many occasions. You can spend more mental energy on logic correctness rather than translation of requirements into code.
Not only it is faster, but you can deliver greater quality faster. Slopware is a result of trying to crank the dev speed to the max without following proper sdlc with proper dod.