idea regarding #code #review:
intentionally adding #bugs into #code to check if the #reviewer discovers them.
if the reviewer does not find them, then their #review is questionable.
of course the added bugs should be removed before merging ;-)
I am wondering if a concept like this already exists ...
#codequality #softwareengineering #quality #software #git #pullrequest #mergerequest
RE: https://social.heise.de/@heiseonlineenglish/116204871378593268
My preferred solution here is CI/CD without code reviews, with 100% code responsibility and AI disclosure per merge request. Anyone using AI must first disclose this and then explain how it has been used. If the code causes a failure, I, and I alone, am liable for it, even at 23:55.
#ai #llm #FckAI #FckLLMs #Amazon #MergeRequest #PullRequest #CICD #SoftwareDevelopment
Everyone who loves GitLab and SVG should vote for: "Render SVG files as images in MR diffs".
I know this is for a car, but many a thing cried out at a command line. 😅
Looking for resources on how to do good code reviews - technically, as a crafts-person, socially. Do you have suggestions?
I would love to read a zine by @b0rk on the subject 😊
One interesting article I recently read was “Understanding and Effectively Mitigating Code Review Anxiety” by @grimalkina and @CSLee. https://doi.org/10.1007/s10664-024-10550-9
#programming #codereview #softwareengineering #pullrequest #mergerequest
Anxiety about giving and receiving code reviews has been documented as a common occurrence that leads to developers avoiding code reviews by procrastinating and limiting their cognitive engagement with them. This avoidance not only increases anxiety in the long term, but also prevents developers, their teams, and their organizations from accessing the technical and sociocognitive benefits of effective and efficient code reviews. However, software research has not yet empirically examined code review anxiety, and from this, tractable intervention targets and strategies for mitigating code review anxiety. In this study, we present an empirical framework for understanding the factors maintaining and exacerbating code review anxiety. Utilizing a randomized waitlist control trial, we also tested the effectiveness of a novel single-session cognitive-behavioral workshop intervention. Our results show evidence that positive impact can be obtained from a brief intervention and suggest code review anxiety can be successfully mitigated by targeting developers’ cost bias, anxiety self-efficacy, and self-compassion.
Has someone attempted to build a #CodeReview tool that relies more on #git itself like using git notes and git trailers and such?
#VersionControl #VCS #PullRequest #MergeRequest #GitHub #BitBucket #GitLab #Gerrit #Gitea #forgejo #Codeberg #amCoding #amProgramming #softwareDevelopment #softwareEngineering #webDevelopment
When in doubt if your comment an a #PullRequest/ #MergeRequest/ #CodeReview or the like was substantial enough to be credited via a git trailer (e.g. Co-authored-by), what would you prefer that the other developer would do by default in that case?
#amCoding #amProgramming #softwareEngineering #softwareDevelopment #git #gitTrailers
Do you remember a couple of weeks ago when I complained that a very large #python contribution to #inkscape was poorly formatted and I felt embarrassed about pushing back and asking them to run a linter over it?
Yeah I'm not fucking embarrassed now, I'm furious. 🤬
Update: Apparently they meant a small section of it was, not the whole MR. I'm annoyed, but I'll have to take them at their word.
Ever found yourself needing that one fix from a PR on GitHub that hasn’t been released yet? How can you get the code, for example a Magento fix, into your code base? Copy-paste it? That might work for small changes, but for large and complex changes copy-pasting is no solution. Luckily, we can use GitHub to generate a patch file, which can then be applied with […]
Jakob Miksch
Lukas Rotermund
BuZZ-dEE ☮️ 🇺🇦 🇪🇺 🇩🇪
Martin Owens 
glamcode
Zuri (he/him) ❌️👑 | 🕐 CET
René de Hesselle
Kevin