Programming

28548 readers

275 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

-15

The End of Code Review? Or an Opportunity to Rethink it? (thelastsoftwareengineer.substack.com)

submitted 1 week ago by codeinabox@programming.dev to c/programming@programming.dev

9 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] MonkderVierte@lemmy.zip 1 points 1 week ago (1 children)

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?

[–] vrek@programming.dev 1 points 1 week ago (1 children)

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.

[–] MonkderVierte@lemmy.zip 1 points 1 week ago

Not ban, warn about fixed string assigned to variable. Ok, guess that would be hard to distinguish on compiler level.