This is a funny article on why you shouldn't use your digital camera when trying to detect / prove the existance of ghosts. No not like a bad flat screen playing Quake, but like Casper the Friendly.
I actually signed a source agreement as the CTO at a dot com that used Fort Knox Escrow services for the code escrow. Always thought that was the coolest name. Funny, funny though... trying to put a link to it here I found that the site isn't up any more http://www.fortknowescrow.com So wonder where the code is? Bet finding it would be a lot of google searches away. As I remember you had to pay to get the code out of escrow a fairly decent penny, like $10k. But better than being high and dry. Definately a good provision to add to any contract, even with a smaller firm if you can find a cheap way to get it done.
Anyone know if this is using 2.4.20 or still 2.4.18 (like in 8.0)? I didn't see a link to what versions are included or what the major differences are.
Every single web based document management system I've ever seen has been a complete pain in the ass. As a consultant I've seen 3 or 4 at various client sites. No one ever knows how to use it right, it is always klunky and it mostly gets ignored.
What is important with whatever documentation you keep is that you have it easily available for everyone. Everyone also needs to be able to easily get the most current copy and be able to submit new information into the current copy.
Sound like version control to anyone? Yup, just use whatever version control software you have on your project. Something that the developers already know how to use. Put the docs under the same project as the source code. When I cvs update (or whatever) to get the current code, I should also get the current doc.
Using CVS will not be the most efficient if you are using Word for your docs, since you have to store the whole binary each time. This isn't usually a problem, but the storage can get big quick. Also you won't get what changed each time since it is a binary. Text files clears this up.
Getting your business guys to use CVS is another whole can of worms, but at least all the developers can get the docs easily.
I always thought that the only really good thing about measuring LOCs was that the number was easy to gather. Yes, the meaning is limitted. Yes, the number of lines you produce changes dramatically regarding where you are in the lifecycle of a project. Yes, the numbers are next to meaningly when comparing different languages or different developers. But you can calculate it easily. Pretty hard to measure the quality of the approach.
So the metric has value when used with care and caution.
If you are in a junit environment, doesn't measuring test cases passed really give you the best idea of progress?
Slashdot Mirror
I'm betting people are going to start selling 'sexy' IP addresses as well.
So I can make someone out there a great deal on 10.10.10.10 if they want it...
Hehe...
This is a funny article on why you shouldn't use your digital camera when trying to detect / prove the existance of ghosts. No not like a bad flat screen playing Quake, but like Casper the Friendly.
He seems real serious about it too....
You can get a 4.1 Giga pixel camera.
probably cost $25k+
No idea why you would want to...
I actually signed a source agreement as the CTO at a dot com that used Fort Knox Escrow services for the code escrow. Always thought that was the coolest name. Funny, funny though... trying to put a link to it here I found that the site isn't up any more http://www.fortknowescrow.com So wonder where the code is? Bet finding it would be a lot of google searches away. As I remember you had to pay to get the code out of escrow a fairly decent penny, like $10k. But better than being high and dry. Definately a good provision to add to any contract, even with a smaller firm if you can find a cheap way to get it done.
Anyone know if this is using 2.4.20 or still 2.4.18 (like in 8.0)? I didn't see a link to what versions are included or what the major differences are.
Thanks,
Adam
Every single web based document management system I've ever seen has been a complete pain in the ass. As a consultant I've seen 3 or 4 at various client sites. No one ever knows how to use it right, it is always klunky and it mostly gets ignored.
What is important with whatever documentation you keep is that you have it easily available for everyone. Everyone also needs to be able to easily get the most current copy and be able to submit new information into the current copy.
Sound like version control to anyone? Yup, just use whatever version control software you have on your project. Something that the developers already know how to use. Put the docs under the same project as the source code. When I cvs update (or whatever) to get the current code, I should also get the current doc.
Using CVS will not be the most efficient if you are using Word for your docs, since you have to store the whole binary each time. This isn't usually a problem, but the storage can get big quick. Also you won't get what changed each time since it is a binary. Text files clears this up.
Getting your business guys to use CVS is another whole can of worms, but at least all the developers can get the docs easily.
I always thought that the only really good thing about measuring LOCs was that the number was easy to gather. Yes, the meaning is limitted. Yes, the number of lines you produce changes dramatically regarding where you are in the lifecycle of a project. Yes, the numbers are next to meaningly when comparing different languages or different developers. But you can calculate it easily. Pretty hard to measure the quality of the approach.
So the metric has value when used with care and caution.
If you are in a junit environment, doesn't measuring test cases passed really give you the best idea of progress?