It takes a few times of having been bitten by lazy coding that a programmer learns that those extra few lines of code actually make life easier. Unfortunately each generation must "burn its fingers on the stove", because that is the human animal.
OTOH, without this inclanation we would still be living in trees, because our parents were afraid to cross that savana....
I have done support for a while (a long time ago, in a place far, far away). It doesn't matter how good your product is. People WILL go 'stupid' on you.
No software is foolproof, because fools are so ingenious
I also want the criteria for a standard for what alpha and beta versions are.
alpha Not all the features / business cases are part of the code. The developers are still adding them.. The code may be unstable, that is crashes for no reason. May contain bugs that trash files. This level should never reach testers who cannot recover their hard drives.
beta All features coded. The application runs OK. Outside testers (outside the development group) are asked to test it. After a while a public beta may be used where people outside the company may try it.
This is the traditional way of separating the two. Of course recently some companies have passed off alpha level as beta, the beta level as release. But that's another story:-))
When I notice TV or radio advertisement it is usually to make a mental note to never buy that product (because I'm so damned irritated by it).
I heard a radio ad for Denny's 9 years ago that was so annoying (two women blathering on about their birthdays, high pitch voices, VERY memorable) that I have not gone to Denny's since.
Absolutely. There was a company that sold a device that was installed in a computer. If the computer was removed the device would destroy the CPU and RAM chips.
It would NOT destroy the hard drive. This made it completely useless IMHO. Who cares about the machine, it is trivial to replace. The data though....
Which would prove that most projects are 60% over time....
A lot of programmers do not do that.
A lot of novice programmers do not do that.
It takes a few times of having been bitten by lazy coding that a programmer learns that those extra few lines of code actually make life easier. Unfortunately each generation must "burn its fingers on the stove", because that is the human animal.
OTOH, without this inclanation we would still be living in trees, because our parents were afraid to cross that savana....
No. It's called "quantity control".
Society as we know it today will go away (good riddance).
A new society will replace it, and we will laze around all day. The machines will provide. And who fixes the machines? Why the priesthood!
Clavin lives!!!
We did a test on a private WAN and about 50% of the traffic was heartbeats.
The really interesting part is that this kid wasn't even a programmer.
The really interesting part is that he did not make the gun, just pointed it and pulled the trigger.
Don't you know that oil from the Middle East was used as fuel in those helicopters, and might even hve been used in the plastic stock on the M-16's?
Comments nothing
It's all those damn logging calls.
So how many bits does it take to stop a door? How high do they need to be piled?
Hmmm, must used higher massed bits.....
- .ca
- .us
- .tv
- .bus
- .wtf
web address.So what?
Goto Google, type in "my needs", and choose a Web site.
Who cares what the TLD is.
-----------
if you use your left hand.
-----------
Multi-media is redundant.
Multi-medium would be correct, or just Media.....
-----------
For more calls: Tech Tales
-----------
Jump to Tech Tales
I have done support for a while (a long time ago, in a place far, far away). It doesn't matter how good your product is. People WILL go 'stupid' on you.
No software is foolproof, because fools are so ingenious
-----------
I also want the criteria for a standard for what alpha and beta versions are.
:-))
alpha Not all the features / business cases are part of the code. The developers are still adding them.. The code may be unstable, that is crashes for no reason. May contain bugs that trash files. This level should never reach testers who cannot recover their hard drives.
beta All features coded. The application runs OK. Outside testers (outside the development group) are asked to test it. After a while a public beta may be used where people outside the company may try it.
This is the traditional way of separating the two. Of course recently some companies have passed off alpha level as beta, the beta level as release. But that's another story
-----------
Blank tapes...Sorry :)
No you were right the first time. Blank tapes are bland.
-----------
Quick, take out a patent!
-----------
When I notice TV or radio advertisement it is usually to make a mental note to never buy that product (because I'm so damned irritated by it).
I heard a radio ad for Denny's 9 years ago that was so annoying (two women blathering on about their birthdays, high pitch voices, VERY memorable) that I have not gone to Denny's since.
Yeah, ads work alright.....
Registration is useless. I registered MS DOS 1.0, and they NEVER got back to for an upgrade.....
Java is NOT platform independent as ANY Java programmer worth his/her weight knows.
Yes it is. You can of course write JNI, but that is discouraged.
I have written Java code that runs quite happily on AIX, AS/400, OS/2, and WinNT.
I was getting errors trying to connect through @Home, so I set up a script to ping and log the DSN and Gateway servers.
The servers go down EVERY DAY. Sometimes 3-4 times per day. Downtime duration is anything from 3 minutes to 1/2 hour.
And this is only on my segment....
Absolutely. There was a company that sold a device that was installed in a computer. If the computer was removed the device would destroy the CPU and RAM chips.
It would NOT destroy the hard drive. This made it completely useless IMHO. Who cares about the machine, it is trivial to replace. The data though....
Because they worry more about content than splash. You know, steak not sizzle.
So no one can EVER write a new FTP server because it emulates a current version?