Peer review keeps us honest. That’s why open source code has to be better. You have to plan for the inevitable future when, if anyone ever cares at all about the code, other people will read it. You can’t just hide your obfuscated tangle of “we don’t know why it works, don’t change it or you’ll break it” spaghetti behind binary compilation.
Just looking at the title of this post, before the post is even written, I’m struck by the myriad interpretations that could be applied to it. It can be read in any number of ways, spanning a wide and varied spectrum of meanings. We’ll see, by the time I’m done, how many of those might still apply:
I’ve written elsewhere about why open source code has to be more secure. I didn’t use a title so cryptic and protean in its meaning at the time, of course, because it was written for professional publication — where the kind of word play I used in the title here is generally a no-no. As such, I also constrained the content somewhat to avoid directly addressing many of the potential meanings of the phrase “why open source code has to be more secure”. Think about this, though: peer review means exactly that your code has to be more secure. What code must be as secure as code that could be viewed — and reviewed — by (almost) literally anyone, for a period without known limits? It has to be more secure, because you never know who’s going to see it, and your reputation as a programmer is attached to that code. Open source development is probably the fastest way to build a reputation for yourself as a programmer, but there’s nothing that says that reputation has to be a good one other than your ability to turn out good code.
Please read more… Great post! Click the link below.
read more | digg story