Wow, Latin, you must be right. Or else you left out the part where he said that jitter correlated with the Audiophile results. Statistical correlation works rather well in the real world
It's their strategy. Bad money drives out good. If you drop a megastore into a small town where most businesses, the mom and pops (which usually provide better service) go under. Since these people can't easily relocate within town, they leave. The support services (doctors, lawyers, and so on) will follow when the business dries up. If too many people leave, the town dies, end of story.
It doesn't matter which assembly (though i pity thos who use x86 assembler). It matters that you can see what the computer is doing at a fairly low level.
My particular answer to this question is that you should learn
data structures and algorithms before worrying too much about a
particular language.
The long answer is that this is how I would spend the first couple
of years, moving from simple coding to a fairly broad understanding
of SoftDev.
First, it's important to have people you can ask questions and
get advice from. They can encourage good habits and explain the
reasons behind something that makes little sense at first.
Learn enough about the language to get by (I like C/C++, but Java
works too), then learn about Big-O notation and lists and trees
and sorting and all that fun stuff. You should also know what call
by reference, value, and that other one (Call by value return, I think)
mean and how they work.
Expand your knowledge of the language you've chosen in line with the
concepts
you use. When you have a decent grasp on the basics, poke around in the
obscure areas. You should know what the language can do, but don't feel
obligated to use every feature. Simple coding style is easier to read,
easier to port, and easier to debug.
In addition to syntax and data structures, there is the additional issue
of overall program organization. This is where structured programming
comes in; it involves dividing a program into modules and specifying
their interactions. This can be used to isolate bugs and simplify system
behavior. Object oriented programming is a refinement of this technique,
with the ability to compose a program of Objects that have specific
behaviors
and may also have explicit relationships. OO has more overhead associated
with
it, but it can be used to build larger systems successfully.
It is very important that you learn how to use these and other techniques
effectively to manage programs, as this will determine the success or
failure
of a project more than the quality of your code (assuming a base level of
ability).
By the time you are familiar with the first language, you should play with
several other languages - get familiar with the style they promote and
the tasks they are suited to. Some good starters are Perl, bourne shell
(as shell scripts go, the bourne shell (not bash) is the only one you can
really depend on to be portable), tcl, C, C++, java, some flavors of
assembly
(if only to see how it works).
You should also be expanding the theoretical side of the coin; all of the
previously mentioned languages are Imperative - they tell the computer to do
something specific. There are other types of languages - Declarative
languages
tell the computer what you want without saying how to get it (SQL).
Functional
languages dispense with side effects (Lisp). Some languages treat functions
as
first class objects (which can be passed as objects).
Your CEO, manager, or boss is the one who really makes the decision
Not if he knows what he's doing. He hired me for my technical knowledge. I do technical eval. He takes these evaluations and incorporates them into business decisions. Change this at your peril
How it works in a healthy org is that a manager or three gets together with a couple technical guys and says 'we want to do this'. They then find out what exactly this entails, budget it, and implement it. If they push a ZDnet propaganda piece, it's our job to deflate it.
The Boss Man decides the business focus and how much he's willing to spend. The tech guy spends the money on what will actually work
crapload of transmitters. Detect a 'rock traveling at 400 knots' and turn on the transmitters. Track the rock with the passive radar and Flak it when it gets close. Then move the AA.
You can be bigoted all you like, but you have no right to incorporate that into your hiring policy. I'll boycott a company if I don't like their politics or their products - they're not hurting anybody by being republicrat, but refusing to hire blacks hurts people directly, and it really is the place of the government to stop such behavior. Maybe you're a bigoted asshole, but if your kids play with the people you so despise, they might grow up more enlightened.
Sure, a corp doesn't have to give a job to some particular person, but that doesn't mean they can bar a whole class of people from employment. The only reason for these laws in the first place is bigoted assholes who refused to hire blacks, or women, or hispanics, or whatever.
Now, I'm a hostile nation that's anxious about invasion, so each city i care about will get several thousand beacons deployed around it at $1k a pop. Each beacon is hooked to main power, has a battery, and can spew on a known set of frequencies (configurable). These beacons can be manually activated or activate automatically if damage is detected in the defense network. I guess the remaining question is how much does it cost to build a passive fire control radar for mobile AA?
I heard somewhere that the IBM KoM is actually good for you - the feedback from the keys helps you out. I'm in the same boat wrt that, but all i find are Keytronics keyboards (not that they're bad or anything).
But I think a lot of ergo companies made a lot of money selling ergo stuff that they wouldn't have been able to sell without all the hype, or as the article put it, "hysteria".
Perhaps these companies have been selling stuff that reduces the pain so that it never gets to the point of damage.
And remember, two cpus running in parellel enjor a greater performance boost (on some tasks) then a single processor with twice the speed of either of the dual processors.
I think you have it backwards. two cpus almost never run at twice the speed of one. Usually, it's good for an extra 50-70 percent speed.
Slashdot Mirror
Actually, a 100W draw without ventilation just makes me nervous.
I just love this quote:
"Our slogan is 'Brute force and ignorance,'" says Gates. "If it blows up, it blows up."
Post hoc ergo propter hoc.
Wow, Latin, you must be right. Or else you left out the part where he said that jitter correlated with the Audiophile results. Statistical correlation works rather well in the real world
can't do that. You really want the Amp to be in one or two pieces, not spread around the room. It makes it easier to ventilate properly.
You have no idea how much money I spend on Needles......
You know, I can't tell if you're a junkie or a DJ
most people who learn to build a car have at least driven one first
Show me one college student who hasn't used a computer. Just one ;)
It's their strategy. Bad money drives out good. If you drop a megastore into a small town where most businesses, the mom and pops (which usually provide better service) go under. Since these people can't easily relocate within town, they leave. The support services (doctors, lawyers, and so on) will follow when the business dries up. If too many people leave, the town dies, end of story.
I do not shop at WalMart
It doesn't matter which assembly (though i pity thos who use x86 assembler). It matters that you can see what the computer is doing at a fairly low level.
My particular answer to this question is that you should learn
data structures and algorithms before worrying too much about a
particular language.
The long answer is that this is how I would spend the first couple
of years, moving from simple coding to a fairly broad understanding
of SoftDev.
First, it's important to have people you can ask questions and
get advice from. They can encourage good habits and explain the
reasons behind something that makes little sense at first.
Learn enough about the language to get by (I like C/C++, but Java
works too), then learn about Big-O notation and lists and trees
and sorting and all that fun stuff. You should also know what call
by reference, value, and that other one (Call by value return, I think)
mean and how they work.
Expand your knowledge of the language you've chosen in line with the
concepts
you use. When you have a decent grasp on the basics, poke around in the
obscure areas. You should know what the language can do, but don't feel
obligated to use every feature. Simple coding style is easier to read,
easier to port, and easier to debug.
In addition to syntax and data structures, there is the additional issue
of overall program organization. This is where structured programming
comes in; it involves dividing a program into modules and specifying
their interactions. This can be used to isolate bugs and simplify system
behavior. Object oriented programming is a refinement of this technique,
with the ability to compose a program of Objects that have specific
behaviors
and may also have explicit relationships. OO has more overhead associated
with
it, but it can be used to build larger systems successfully.
It is very important that you learn how to use these and other techniques
effectively to manage programs, as this will determine the success or
failure
of a project more than the quality of your code (assuming a base level of
ability).
By the time you are familiar with the first language, you should play with
several other languages - get familiar with the style they promote and
the tasks they are suited to. Some good starters are Perl, bourne shell
(as shell scripts go, the bourne shell (not bash) is the only one you can
really depend on to be portable), tcl, C, C++, java, some flavors of
assembly
(if only to see how it works).
You should also be expanding the theoretical side of the coin; all of the
previously mentioned languages are Imperative - they tell the computer to do
something specific. There are other types of languages - Declarative
languages
tell the computer what you want without saying how to get it (SQL).
Functional
languages dispense with side effects (Lisp). Some languages treat functions
as
first class objects (which can be passed as objects).
and after they kill the local economy, nobody has money, so they leave.
Your CEO, manager, or boss is the one who really makes the decision
Not if he knows what he's doing. He hired me for my technical knowledge. I do technical eval. He takes these evaluations and incorporates them into business decisions. Change this at your peril
How it works in a healthy org is that a manager or three gets together with a couple technical guys and says 'we want to do this'. They then find out what exactly this entails, budget it, and implement it. If they push a ZDnet propaganda piece, it's our job to deflate it.
The Boss Man decides the business focus and how much he's willing to spend. The tech guy spends the money on what will actually work
Revenge can be sweet:
He: I left my tools at your house. Give 'em back.
Me: You can pick them up between the hours of 7:25 and 7:35 Tuesdays and Thursdays
crapload of transmitters. Detect a 'rock traveling at 400 knots' and turn on the transmitters. Track the rock with the passive radar and Flak it when it gets close. Then move the AA.
You can be bigoted all you like, but you have no right to incorporate that into your hiring policy. I'll boycott a company if I don't like their politics or their products - they're not hurting anybody by being republicrat, but refusing to hire blacks hurts people directly, and it really is the place of the government to stop such behavior. Maybe you're a bigoted asshole, but if your kids play with the people you so despise, they might grow up more enlightened.
Sure, a corp doesn't have to give a job to some particular person, but that doesn't mean they can bar a whole class of people from employment. The only reason for these laws in the first place is bigoted assholes who refused to hire blacks, or women, or hispanics, or whatever.
Not bad at all
Now, I'm a hostile nation that's anxious about invasion, so each city i care about will get several thousand beacons deployed around it at $1k a pop. Each beacon is hooked to main power, has a battery, and can spew on a known set of frequencies (configurable). These beacons can be manually activated or activate automatically if damage is detected in the defense network. I guess the remaining question is how much does it cost to build a passive fire control radar for mobile AA?
I heard somewhere that the IBM KoM is actually good for you - the feedback from the keys helps you out. I'm in the same boat wrt that, but all i find are Keytronics keyboards (not that they're bad or anything).
But I think a lot of ergo companies made a lot of money selling ergo stuff that they wouldn't have been able to sell without all the hype, or as the article put it, "hysteria".
Perhaps these companies have been selling stuff that reduces the pain so that it never gets to the point of damage.
how many have you got? Anyone seriously considering a defense application will most likely deploy densely, so you'd need quite a few.
Name one.
System performance is going to be lower on the dual proc version just from multiproc overhead.
How about rampant stock speculation stemming from the practice of buying stock with 90% financed?
You mean it's not out on DVD? That's pretty unbelievable, considering that it's a Japanese flick.
Oh well, you can always drop Y4725 (~$40) on the VHS version
And remember, two cpus running in parellel enjor a greater performance boost (on some tasks) then a single processor with twice the speed of either of the dual processors.
I think you have it backwards. two cpus almost never run at twice the speed of one. Usually, it's good for an extra 50-70 percent speed.
I guess that makes the US terroristic as well.
I'll let them watch My neighbor Totoro any day of the week. Perhaps you should broaden your horizons.