3 ms·
Do other companies not have static analysis integrated into the CI/CD pipeline? We by default block any and all PRs that contain funky code: high cyclomatic co
by beAbU 2y ago
Do other companies not have static analysis integrated into the CI/CD pipeline?
We by default block any and all PRs that contain funky code: high cyclomatic complexity, unused variables, bad practise, overt bugs, known vulnerabilities, inconsistent style, insufficient test coverage, etc.
If that code is not pristine, it's not going in. A human dev will not even begin the review process until at least the static analysis light is green. Time is then spent mentoring the greens as to why we do this, why it's important, and how you can get your code to pass.
I do think some devs still use AI tools to write code, but I believe that the static analysis step will at least ensure some level of forced ownership over the code.
- ericmcer 2y agoThat is a softball question for an AI: this block of code is throwing these errors, can you tell me why?
- lrem 2y agoJust wait till AI learns how to pass your automated checks, without getting any better in the semantics. Unused variables bad? Let’s just increment/append whatever every iteration, etc.
- whatevertrevor 2y agoAnd then we'll need AI tools to diagnose and profile AI generated code to automagically improve performance. I can't wait to retire.
- liontwist 2y agoI think it’s a good thing to use such tools. But no amount of tooling can create quality. It gives you an illusion of control. Rules are a cheap substitute for thinking.