codeinabox ( codeinabox@programming.dev ) to Programming@programming.devEnglish · 1 month agoThe End of Code Review? Or an Opportunity to Rethink it?thelastsoftwareengineer.substack.comexternal-linkmessage-square9linkfedilinkarrow-up12
arrow-up12external-linkThe End of Code Review? Or an Opportunity to Rethink it?thelastsoftwareengineer.substack.comcodeinabox ( codeinabox@programming.dev ) to Programming@programming.devEnglish · 1 month agomessage-square9linkfedilink
minus-squareMonkderVierte ( MonkderVierte@lemmy.zip ) linkfedilinkarrow-up1·1 month ago Ai will not catch that. Static testing won’t catch this. Test suites running on the piece of hardware we had, wouldn’t catch this. Only a human reviewer would. This explains a lot of lsecurity issues in the last few years. Also, can’t compilers catch that and complain?
minus-squarevrek ( vrek@programming.dev ) linkfedilinkEnglisharrow-up1·1 month agoWell basically it’s just a ‘magic number’. If you ban all of those many programs will either break or at minimum suffer sever performance degradation.
minus-squareMonkderVierte ( MonkderVierte@lemmy.zip ) linkfedilinkarrow-up1·1 month agoNot ban, warn about fixed string assigned to variable. Ok, guess that would be hard to distinguish on compiler level.
This explains a lot of lsecurity issues in the last few years.
Also, can’t compilers catch that and complain?
Well basically it’s just a ‘magic number’. If you ban all of those many programs will either break or at minimum suffer sever performance degradation.
Not ban, warn about fixed string assigned to variable. Ok, guess that would be hard to distinguish on compiler level.