I recommend PS to people but the price is prohibitive to say the least. This is where Gimp owns the competition and particularly PS
For me The Gimp is better because it is free as in free speech, not free as in free beer. I'd pay money for a stable version of The Gimp (if I needed to).
Re:Top 10 Rules of Debugging
on
Debugging
·
· Score: 3, Interesting
10. Code is _always_ Beta. It's never done until it's no longer in use or support no longer exists.
What about the opposite. Anyone against versioning? Tried and failed in Google to find an "Against versioning" campagin. I mean, somebody must be out there who only wants version 1.0 for all software.
I guess the issue is in the meaning we attach to version numbers. What about a program as a well-specified function that, once is implemented (at least for a fixed platform) needs no "enhancements"?
(E.g. Don Knuth adds a digit to each version of TeX, implying that he doesn't plan to add anything substantial, or else he'll be running into very long version numbers).
Slashdot Mirror
I entirely agree!!!!
I recommend PS to people but the price is prohibitive to say the least. This is where Gimp owns the competition and particularly PS
For me The Gimp is better because it is free as in free speech, not free as in free beer. I'd pay money for a stable version of The Gimp (if I needed to).
10. Code is _always_ Beta. It's never done until it's no longer in use or support no longer exists.
What about the opposite. Anyone against versioning? Tried and failed in Google to find an "Against versioning" campagin. I mean, somebody must be out there who only wants version 1.0 for all software.
I guess the issue is in the meaning we attach to version numbers. What about a program as a well-specified function that, once is implemented (at least for a fixed platform) needs no "enhancements"?
(E.g. Don Knuth adds a digit to each version of TeX, implying that he doesn't plan to add anything substantial, or else he'll be running into very long version numbers).
Not me. It would be interesting to have a rule of thumb for the real economic cost of debugging this way.
We all (except Dijstra, perhaps) take trade-offs, for a reason. Perhaps that reason is only ignorance, but then we wouldn't get anything done.
What about Google keeping track of your searchers and inferring when you're having trouble to find something?
I guess something could be done with sequences of consecutive searches.
I wonder if they could tell the difference between the world underneath those satellites, and a simulated version of it.
Of course its all being outsourced to India now
where they can just hire more developers if
complex problems arrise
Uhum, you missed there the problem of scalability in software engineering...
I mean, a problem ten times bigger is not solved by ten times as many people.