Oh I agree, whatever term you use, it doesn't replace a good talk with the developer who wrote it to understand their thought process.
More often than not, bad code is not written because the developer thought to himself: "Fuck em all, here's some trash code!"
As someone pointed in the comments, git curious is a nice neutral term which could even be better because it can be used in a credit or blame context!
I'm totally sold on git curious.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Oh I agree, whatever term you use, it doesn't replace a good talk with the developer who wrote it to understand their thought process.
More often than not, bad code is not written because the developer thought to himself: "Fuck em all, here's some trash code!"
As someone pointed in the comments, git curious is a nice neutral term which could even be better because it can be used in a credit or blame context!
I'm totally sold on git curious.