Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
-
@Codex404 good point of view :). They will find me by commit records though. I would have gotten away if not for meddling git.
-
@aviophile if they are smart enough to not stop looking past the author tag they are smart enough to not ask dumb questions
-
If you mean the tag @author withing the code, DUDE!!!! that is disgusting, any comment within the code means the code is not self explanatory.
Hughhh!!! who the hell keeps comments in his code anymore? -
@arcioneo he should have used “<name>_” tag in filename, function name and variables, I agree.
-
@aviophile ye ye, thats what I mean. There's no use in using the in-code tags, much less so to update them. All the names are already in the repo. Which is why, in our company, we stopped using the @Author tag.. and our IDEs are configured to not generate those at all.
People that update the @Author tag are annoying! :) -
@aviophile it is possible to keep history and authors when switching. Dont ask me how but one project I worked on did that.
When refactoring and reusing code, is it even ethical to change author?
I am on a project of creating reusable library from another project. Original code is perfectly written, easy to understand. I will just prune the code and fix minor bugs.
I have seen colleagues replacing the original author field in the same scenario with their names, feels wrong. Can I add non-standard maintainer field in doxygen format?
question