4 ms·
Is all of the code you are writing open source? If not, then you may not want to release it to third parties, and they may not want to read it. Also, getting a
by jacobscott 18y ago
Is all of the code you are writing open source? If not, then you may not want to release it to third parties, and they may not want to read it.
Also, getting a reasonable code review on a large project pretty much requires the reviewer to be versed in your codebase. Depending on what you're doing, it may be more costly (in time/money) to bring someone up to speed.
- ggruschow 18y agoIs all of the code you are writing open source? If not, then you may not want to release it to third parties, and they may not want to read it. I was speaking of closed source parts. Open-source has a reasonable enough review process already. Although I don't want the code publicly available, I don't want to waste my life being paranoid. Depending on what you're doing, it may be more costly (in time/money) to bring someone up to speed. Very true. Fortunately, I control the requirements, and I'm almost compulsive about simplicity. I want to be able to keep the code small and be able to rewrite parts quickly. I'm very much into quantity over quality (http://www.codinghorror.com/blog/archives/001160.html http://www.codinghorror.com/blog/archives/001160.html), so if it's useful, I'd be happy to start from scratch just to bring reviewers up with me. That said, I want to be able to bring other developers up to speed on the project later, and it might be time well invested trying to make the project easier to get up to speed on. That'd also reduce the dependency on particular people that are in some part of the world I'll likely never see.