Stealing your coworkers work (or shoddy code from the net) and passing it off as your own comes later. When you are a PROFESSIONAL. We call this "reuse."
Now, get back to drinking beer... er, I mean doing your assignments.
Software quality is inconsistant because...
on
Software Aesthetics
·
· Score: 1
...humans are the ones developing it.
Once a means of expressing unambiguous software requirements to a computer is developed machines will do all of our "development".
Modern programming languages are merely a step in this direction.
Because not everything that uses a CPU is a PC... that's why people need them.
A short list:
phones (cell and desk)
dvd players
cable boxes
dsl/cable modems
heat seeking missile sensors
hand held radios
EKG monitors
automobile fuel injection control systems
home security alarm systems
I am sure you can think of many more such devices.
..and Covad said not to worry, we'll pick up the slack.
By this time I was back using a modem.
Glad I didn't listen!
So much for the Covad "safety net."
... that is hard to defeat. Realtors tend to not list hot properties so that they can sell them to their preferred customers (mainly people who buy investment properties but also for friends that they know are looking, family, ect).
Additionally, sold houses will stay listed. Why? Because when you inquire about a place that is sold, they can then make a pitch to you to buy another place after they "sadly" inform you that your place of interest is no longer available.
It is quite fun - the MAI system may suck wind comapred to even a low end PC - it "basically" (hee hee) is a hopped up TRS-80 that runs nothing but Busniess Basic.
Every file is a flat text file (with indexing on a defined substring). Primitive, but it works!
The problem is that if it breaks they are hosed. Not only that but it is slow.... one report on a file with around 35,000 records takes an hour to run. I ran the same report on a 386 33SX(!) in 15 minutes, and on a P5 233 in 3 and a few seconds.
...of stealing GPL'ed code for their half hearted attempt at a POSIX compiliant OS, I'd wonder what commercial code they stole as I am sure you'd be able to frind sources for every single OS on the planet somewhere on their campus. After all, why settle for using Linux code when you can steal Solaris'?
But I digress.
I would be taking a look at Apple horking FreeBSD for OSX before accusing Microsoft.
Why don't they distribute the link verification much the same way SETI@Home does? They could then shoot a micropayment (say a penny or so) to the user for every work unit (say 10,000 or so links) that they verified.
This would primarily be for folks with always on access as it might tend to clog a thin pipe.
Feature enhancements and nug fixes generally appear faster.... as do new bugs and compatibility issues.
I a gree with the poster down below: if it sticks in your craw then stay with one distro - or try FreeBSD.
Both approaches have their advantages.
"The process happens generally like: the the 'buy' button is pressed by the shopper, the shopping cart passes a few things to the transaction gateway (among them the price)..."
Stop right there. I hope you can see why one would not want to design a system with this functionality. Perhaps it would be better to simply accept the user info, item number, and quanity instead - letting any price calculation be done on the server side - and submit THAT to the gateway.
Post de facto verification should be used as a last line of defense only.
While I agree with the sentiment, I feel it important to point out that this vulnerability isn't just limited to NT based commerce sites.
The strongest safe door won't do squat if you leave the damn thing open.
Slashdot Mirror
...is the best way to learn.
Stealing your coworkers work (or shoddy code from the net) and passing it off as your own comes later. When you are a PROFESSIONAL. We call this "reuse."
Now, get back to drinking beer... er, I mean doing your assignments.
...humans are the ones developing it.
Once a means of expressing unambiguous software requirements to a computer is developed machines will do all of our "development".
Modern programming languages are merely a step in this direction.
...that was already made (several times).
Remember the P120+? It was a 100 MHz chip.
...of Science Applications International Corporation.
That was it! That software was the WORST!
It is a scripting language for a X Window based RAD tool called Telesys(? - maybe that was the name of the company that made the software).
Because not everything that uses a CPU is a PC... that's why people need them.
A short list:
phones (cell and desk)
dvd players
cable boxes
dsl/cable modems
heat seeking missile sensors
hand held radios
EKG monitors
automobile fuel injection control systems
home security alarm systems
I am sure you can think of many more such devices.
I have a closetful of 486's, old cards, 5 inch drives, ect that I would love to sell.
..and Covad said not to worry, we'll pick up the slack. By this time I was back using a modem. Glad I didn't listen! So much for the Covad "safety net."
"Search warrant."
Fly away, little BSA bird.
Thanks for the letter.... now what are you going to do about that President you put into office?
...but unwieldy (and of course buggy). However, I find that COM/DCOM neatly solve this issue with little hassle (from the users point of view).
Programming that cr@p is a whole other issue: one that makes me ill.
... that is hard to defeat. Realtors tend to not list hot properties so that they can sell them to their preferred customers (mainly people who buy investment properties but also for friends that they know are looking, family, ect).
Additionally, sold houses will stay listed. Why? Because when you inquire about a place that is sold, they can then make a pitch to you to buy another place after they "sadly" inform you that your place of interest is no longer available.
Sadly, this is a fact of life.
Nope. It will happen - just a matter of figuring out how (and how long it will take).
It is definately an interesting problem!
It is quite fun - the MAI system may suck wind comapred to even a low end PC - it "basically" (hee hee) is a hopped up TRS-80 that runs nothing but Busniess Basic.
Every file is a flat text file (with indexing on a defined substring). Primitive, but it works!
The problem is that if it breaks they are hosed. Not only that but it is slow.... one report on a file with around 35,000 records takes an hour to run. I ran the same report on a 386 33SX(!) in 15 minutes, and on a P5 233 in 3 and a few seconds.
This is an interesting link. Thanks!
"In other words, your encrypted files may only be as secure as the computer and network on which the key resides."
Duh.
...they will either GIVE us a cure for cancer or blow us to smithereens and take off with all of the oil.
So. I say SETI@Home is the only worthwhile distro computing application.
...of stealing GPL'ed code for their half hearted attempt at a POSIX compiliant OS, I'd wonder what commercial code they stole as I am sure you'd be able to frind sources for every single OS on the planet somewhere on their campus. After all, why settle for using Linux code when you can steal Solaris'?
But I digress.
I would be taking a look at Apple horking FreeBSD for OSX before accusing Microsoft.
Why don't they distribute the link verification much the same way SETI@Home does? They could then shoot a micropayment (say a penny or so) to the user for every work unit (say 10,000 or so links) that they verified.
This would primarily be for folks with always on access as it might tend to clog a thin pipe.
Sheesh!
Feature enhancements and nug fixes generally appear faster.... as do new bugs and compatibility issues. I a gree with the poster down below: if it sticks in your craw then stay with one distro - or try FreeBSD. Both approaches have their advantages.
"The process happens generally like: the the 'buy' button is pressed by the shopper, the shopping cart passes a few things to the transaction gateway (among them the price)..."
Stop right there. I hope you can see why one would not want to design a system with this functionality. Perhaps it would be better to simply accept the user info, item number, and quanity instead - letting any price calculation be done on the server side - and submit THAT to the gateway.
Post de facto verification should be used as a last line of defense only.
While I agree with the sentiment, I feel it important to point out that this vulnerability isn't just limited to NT based commerce sites. The strongest safe door won't do squat if you leave the damn thing open.