But not to the Navajo Nation, which covers northeastern Arizona and follows DST.
But the Hopi reservation would be OK. (It's in Arizona, surrounded
by the Navaho reservation, and does not follow DST.)
> Synthesizers are getting much better, and I think for some musicals they dont even bother with a pit orchestra.
That's not so much because synthesizers are better, but because they're cheaper than musicians and some audiences will accept the substitution.
Synthesizers aren't all that good at duplicating traditional instruments and players, if you look (listen) at all the musical aspects. Synthesizers are great at doing things that can't be done with traditional instruments and players.
The emphasis on fast development is a recent... development.
In the era just before the current one, the accepted wisdom
was to spend lots of time on requirements, design, code, and
test in order to save lots and lots of money on maintenance.
But since development took so long, many projects ran out
of money before producing any software. And those that did
produce SW didn't provide what the customer really wanted.
So some of the gurus of the SW world decided it would be better
to develop quickly and at least get something done,
and get some feedback from the customer before spending too
much time and money.
The information need not be (very) accurate. It can still be a useful input to some sort of statistical algorithm. Even slightly-more-accurate-than-random data can contribute to a solution. Of course, the data could be less-accurate-than-random... But it's all a matter of playing the odds, I think.
Don't make the new case too heavy. In many cases, the drive is held horizontal by the connectors at one end. If the case is too heavy, you'll stress the connectors. And as the case gets longer, the leverage makes the situation worse.
Synthesized (or sampled) versions of acoustic instruments somehow always sound different from the real thing, even on recordings or through amplification. On hearing, say, a synthesized/sampled trumpet, I think "hey, that sounds a lot like a trumpet". But it's easy to tell the difference.
Part of the difference may be in the way they're played, and by whom. A guitarist is going to play differently, inc. different notes, than a keyboardist imitating a guitar.
But a bigger part of the difference is probably the fact that the sampled/synthesized sounds don't really capture the original sound. The original attack is probably more complicated and variable (note to note). Acoustic instruments also have very different tone color from pitch to pitch (or note to note), either intentionally or because of the way the instrument is constructed.
I don't think the synthesized/sampled versions of instruments like pianos and guitars take into account the slight ringing of other notes when one note is played.
Hungarian notation is for cases where variable types can't be interchanged, but the computer can't detect violations of this rule (ex. most assembly language). Hungarian notation helps the programmer avoid breaking this rule.
The more that types can be mixed, and the the more that the computer can detect type problems, the less useful Hungarian notation is.
Something similar happened to me. Somebody charged $500 of VeriSign services to my Discover card. I called to complain. They wouldn't even talk about removing the charge unless I faxed all sorts of info to them. And they wouldn't tell me what services they were charging me for (I did manage to get the phone rep to say it involved some domain involving "graphics" and a Yahoo email address.
I let Discover handle it. They gave me an immediate temporary credit, and a few months later the credit became permanent.
While I was waiting for the matter to be resolved, I got a (postal) mail notice about renewing another set of domains I had nothing to do with (all containing the string "sony").
True, the C++ language spec explicitly specifies performance requirements for STL components. But only in terms of how the performance scales for large sets of data - the Big-0 performance. This doesn't require that any of it is actually fast on any absolute scale. (I think.)
Slashdot Mirror
But not to the Navajo Nation, which covers northeastern Arizona and follows DST. But the Hopi reservation would be OK. (It's in Arizona, surrounded by the Navaho reservation, and does not follow DST.)
> cout << "You are a bazooty head";
A better example of the problem is
current << size;
In that context, is << a shift operation or an output operation? You can't tell.
> Synthesizers are getting much better, and I think for some musicals they dont even bother with a pit orchestra.
That's not so much because synthesizers are better, but because they're cheaper than musicians and some audiences will accept the substitution.
Synthesizers aren't all that good at duplicating traditional instruments and players, if you look (listen) at all the musical aspects. Synthesizers are great at doing things that can't be done with traditional instruments and players.
In the era just before the current one, the accepted wisdom was to spend lots of time on requirements, design, code, and test in order to save lots and lots of money on maintenance. But since development took so long, many projects ran out of money before producing any software. And those that did produce SW didn't provide what the customer really wanted.
So some of the gurus of the SW world decided it would be better to develop quickly and at least get something done, and get some feedback from the customer before spending too much time and money.
Maybe the pendulum will swing the other way now.
The information need not be (very) accurate. It can still be a useful input to some sort of statistical algorithm. Even slightly-more-accurate-than-random data can contribute to a solution. Of course, the data could be less-accurate-than-random... But it's all a matter of playing the odds, I think.
Don't make the new case too heavy. In many cases, the drive is held horizontal by the connectors at one end. If the case is too heavy, you'll stress the connectors. And as the case gets longer, the leverage makes the situation worse.
VNC, for screen sharing and remote control.
Others can see anything you see on your screen.
Great for discussions and troubleshooting.
Free.
computer science != programming
Synthesized (or sampled) versions of acoustic instruments somehow always sound different from the real thing, even on recordings or through amplification. On hearing, say, a synthesized/sampled trumpet, I think "hey, that sounds a lot like a trumpet". But it's easy to tell the difference.
Part of the difference may be in the way they're played, and by whom. A guitarist is going to play differently, inc. different notes, than a keyboardist imitating a guitar.
But a bigger part of the difference is probably the fact that the sampled/synthesized sounds don't really capture the original sound. The original attack is probably more complicated and variable (note to note). Acoustic instruments also have very different tone color from pitch to pitch (or note to note), either intentionally or because of the way the instrument is constructed.
I don't think the synthesized/sampled versions of instruments like pianos and guitars take into account the slight ringing of other notes when one note is played.
Is it possible that there were compliant compilers before GCC? And that GCC was late at reaching compliance?
Yes. That's what I've seen. No unit testing. No regression testing. No automated testing.
Manual, very-high-level system testing only.
Tremendous amounts of time and money spent in the integration phase.
The first step to improvement is to just do some unit testing. Writing the tests before the code is secondary.
Most Perl software would be downloaded from CPAN, not sourceforge.
Hungarian notation is for cases where variable types can't be interchanged, but the computer can't detect violations of this rule (ex. most assembly language). Hungarian notation helps the programmer avoid breaking this rule.
The more that types can be mixed, and the the more that the computer can detect type problems, the less useful Hungarian notation is.
Something similar happened to me. Somebody charged $500 of VeriSign services to my Discover card. I called to complain. They wouldn't even talk about removing the charge unless I faxed all sorts of info to them. And they wouldn't tell me what services they were charging me for (I did manage to get the phone rep to say it involved some domain involving "graphics" and a Yahoo email address.
I let Discover handle it. They gave me an immediate temporary credit, and a few months later the credit became permanent.
While I was waiting for the matter to be resolved, I got a (postal) mail notice about renewing another set of domains I had nothing to do with (all containing the string "sony").
Every public class goes in a different file, IIRC. That file can also define other, non-public classes, both inner and non-inner.
True, the C++ language spec explicitly specifies performance requirements for STL components. But only in terms of how the performance scales for large sets of data - the Big-0 performance. This doesn't require that any of it is actually fast on any absolute scale. (I think.)