Is a code review which uses only code comments a good idea?
In case of some question/issue reviewer create comment with special label, like “REV”. Such label MUST not be in production code — only on review stage:
Reusable VS clean code – where’s the balance?
Let’s say I have a data model for a blog posts and have two use-cases of that model – getting all blogposts and getting only blogposts which were written by specific author.
How important is positive feedback in code reviews?
Is it important to point out the good parts of the code during a code review and the reasons why it is good? Positive feedback might be just as useful for the developer being reviewed and for the others that participate in the review.
How is the Linux repository administrated?
I am amazed by the Linux project and I would like to learn how they administrate the code, given the huge number of developers. I found the Linux repository on GitHub, but I do not understand how it is administrated. For example the following commit: https://github.com/torvalds/linux/commit/31fd84b95eb211d5db460a1dda85e004800a7b52
How can you get constructive criticism for your code?
My team rarely does code review, mainly because we don’t have enough time and people lack the energy and will to do so. But I would really like to know what people think about my code when they read it. This way, I have a better understanding how other people think and tailor my code accordingly so it’s easier to read.
What is the way to understand someone else’s giant uncommented spaghetti code? [duplicate]
Possible Duplicate:
I’ve inherited 200K lines of spaghetti code — what now?
Does studying other people’s programs help in self growth? [closed]
Closed 9 years ago.
As a solo programmer, of what use can Gerrit be?
Disclaimer: I’m aware of the questions How do I review my own code? and What advantages do continuous integration tools offer on a solo project?. I do feel that this question aims at a different set of answers though, as it is about a specific software, and not about general musings about the use of this or that practice or tech stack.
Can notes/to-dos in code comments sent to code-reviews result in an effective refactoring process?
I want to start/improve a culture of collective code ownership at my company but at a geographically distributed level… I’d say there is some current collective code-ownership mentality, but only at single geographical sites.
How would you react if someone told you your code is a mess?
Want to improve this post? Provide detailed answers to this question, including citations and an explanation of why your answer is correct. Answers without enough detail may be edited or deleted. I am a good programmer, or so I thought before. I always love to program. And I want to learn many things about programming […]