And remember that any attempt to circumvent locking out third-party memory is a heinous violation of the DMCA and will leave *you* the crimino-consumer liable for a big fine or jail.
No it isn't. A memory card is not a protected work under the DMCA.
It's bad enough that we have an over-restrictive law in the first place. Don't make things worse by making people think it covers things that it doesn't.
I'd say the results are pretty meaningless. If you toss a coin 16 times, you've got something like a 1 in 8 chance of getting 6 heads and 10 tails. Chance of at least 10 heads is closer to 1 in 4. Hardly astronomically impossible that they were all choosing randomly, but they could have just had a disproportionate number of people with below average hearing, or people who are more used to the sound of AAC (i.e. iPod users). Similarly, they might have just played a song that happens to work well with low bitrate AAC.
Uhm, actually, game developers and academic 3D graphics researchers tend to think very differently. Game developers are interested in a specific effect for a specific case. Academics are more interested in generalising the problem and being as precise in their terminology as possible. This means that to understand an academic paper, you have to learn a completely different language.
You can apply the pure mathematics solution to real time software once you understand it, but in virtually all cases, it isn't essential to understand the principles at so fundamental a level. In all cases, given a number of options, some from academic texts, and others from informal game development articles, I'll go for the game development articles first.
"Silly" comments in code. Occasionally acceptable to have a sense of humour but it has to actually be funny because it's relevant rather than because it's random. But you'll often get the "funny" guy in the office who doesn't realise that he's not.
"Chatty" - Yes, this is more typical of coders. Not someone who spends a lot of time talking. More that he doesn't get hints. There seems to be a borderline aspergers type that has a high correlation with programmers. You can simply tell them to go away because your busy and they will.
Inappropriate conversations - happens in all sectors. Some people just don't know what's appropriate.
True. This might have more of a chance though. The iPhone hasn't quite saturated the market yet. There are plenty of potential customers who aren't locked in.
Historically, America has been the land of opportunity. It was the place people went to to start a completely new life. None of the squalor, starvation, and domestic wars of Europe. None of the harsh totalitarianism of China. Of course, a journey for the family would cost a fortune, so it was only going to be one way.
It's just not like that any more. It's a nice place to live, but so is everywhere else if you have money. Money can be earned if you have experience. And flights are quick and cheap. Even people from relatively poor countries can afford a flight to another continent.
Returning home was always the plan. People miss their home. Returning home after a few years and getting a good job in their home country has always been part of the plan. If you have a few years' experience working at a major US tech firm, everyone wants you to work for them.
Not so much these days, and rarely when it's still playing. often it's the same day or sometimes even a day or so earlier. Surrogates has been out since 25th September in Britain,
But anyone with a CS degree at least should understand the basics of why big primes make good private keys
Indeed. Although it should be noted that Mersenne primes are sort of useless for this. If you know one of the factors is a Mersenne Prime then there are only 47 candidates.
I have one. The stylus input device works quite well for drawing, but the UI sucks. There's not even a delete function. Battery life seems to be very good though.
Yes. Polarised sunglasses have the same polarisation on each lens. Presumably different levels of glare in each eye is going to be slightly disorienting. Although probably not enough as to need a warning.
Basic depth perception has its uses. Mainly this is for perceiving depth. But binocular vision is just one of the clues the brain uses. We get a certain amount of depth perception just from perspective.
Add head tracking. It would allow the user to look around 3D windows. Items could actually float within the screen (and even in front to an extent).
Which one will you tend to pick? The one who sees every problem as a nail and uses a complicated process to solve simple problems? It seems a remarkable poor metric for determining skilled programmers.
It strikes me as a highly illogical question. Are you suggesting that a computer programmer wouldn't see programming as a solution to a problem that by definition needs software?
I think I'd provide some hypothetical examples of problems that might be solved and ask them how to go about it. Some of the problems may well have an existing solution. I'd ask the applicant about their solutions, and suggest alternative solutions and ask them about the pros and cons of them.
Or they're perfectly competent engineers who know how to learn, have interesting and varied projects at work, and have other interests.
Learning an API doesn't take long. Even learning a new programming language doesn't take long if it's similar enough to one you know. Very few jobs use the same language and API for a particularly long time. The skills they learn in their free time are not all that likely to be relevant to the job that you hire them for. Not programming in your free time doesn't mean not using computers in your free time. Very few problems at home need programming to solve them.
Someone with experience in C++ will use exceptions, STL, and the new/delete operators, because these are much nicer than the C equivalents. They'll rarely need to worry about the actual size of a data type. Knowing the C specific parts of C++ is certainly very important but that doesn't actually mean you'll know how to write a decent C program.
I'd actually be more inclined to hire a C++ programmer for a C# project than a C project.
In terms of memory, 64 bits can address 18 exabytes. Even Google isn't going to be using that for a decade or so. Assuming Moore's law continues, it will be about half a century before PCs need that much RAM. Dealing with 128 bit numbers for mathematics is of limited use (if you do want to deal with them, you'll probably have a need for 256 byte and 512 byte numbers as well).
And it's not like there's been much perception of a need for 128 bit CPUs. 64 bit processors have been around since the 1960's with fairly mainstream CPUs sine the early 90s. I don't think this is like RAM. I think there's a limit to how many bits we can use.
It leads to an interesting problem though. Suppose I sell you a copy of a GPL product and the source code on two separate CDs. You then sell Person B the source code CD and he sells it to person C. Is Person B obliged to provide the source to Person C on request even though he isn't capable for doing this?
Slashdot Mirror
And remember that any attempt to circumvent locking out third-party memory is a heinous violation of the DMCA and will leave *you* the crimino-consumer liable for a big fine or jail.
No it isn't. A memory card is not a protected work under the DMCA.
It's bad enough that we have an over-restrictive law in the first place. Don't make things worse by making people think it covers things that it doesn't.
I'd say the results are pretty meaningless. If you toss a coin 16 times, you've got something like a 1 in 8 chance of getting 6 heads and 10 tails. Chance of at least 10 heads is closer to 1 in 4. Hardly astronomically impossible that they were all choosing randomly, but they could have just had a disproportionate number of people with below average hearing, or people who are more used to the sound of AAC (i.e. iPod users). Similarly, they might have just played a song that happens to work well with low bitrate AAC.
Uhm, actually, game developers and academic 3D graphics researchers tend to think very differently. Game developers are interested in a specific effect for a specific case. Academics are more interested in generalising the problem and being as precise in their terminology as possible. This means that to understand an academic paper, you have to learn a completely different language.
You can apply the pure mathematics solution to real time software once you understand it, but in virtually all cases, it isn't essential to understand the principles at so fundamental a level. In all cases, given a number of options, some from academic texts, and others from informal game development articles, I'll go for the game development articles first.
"Silly" comments in code. Occasionally acceptable to have a sense of humour but it has to actually be funny because it's relevant rather than because it's random. But you'll often get the "funny" guy in the office who doesn't realise that he's not.
"Chatty" - Yes, this is more typical of coders. Not someone who spends a lot of time talking. More that he doesn't get hints. There seems to be a borderline aspergers type that has a high correlation with programmers. You can simply tell them to go away because your busy and they will.
Inappropriate conversations - happens in all sectors. Some people just don't know what's appropriate.
True. This might have more of a chance though. The iPhone hasn't quite saturated the market yet. There are plenty of potential customers who aren't locked in.
Historically, America has been the land of opportunity. It was the place people went to to start a completely new life. None of the squalor, starvation, and domestic wars of Europe. None of the harsh totalitarianism of China. Of course, a journey for the family would cost a fortune, so it was only going to be one way.
It's just not like that any more. It's a nice place to live, but so is everywhere else if you have money. Money can be earned if you have experience. And flights are quick and cheap. Even people from relatively poor countries can afford a flight to another continent.
Returning home was always the plan. People miss their home. Returning home after a few years and getting a good job in their home country has always been part of the plan. If you have a few years' experience working at a major US tech firm, everyone wants you to work for them.
It's not a morality issue. They just try to spin it that way. It's a business decision.
They don't want people playing that are costing them money.
The UK *always* gets their movies after we do
Not so much these days, and rarely when it's still playing. often it's the same day or sometimes even a day or so earlier. Surrogates has been out since 25th September in Britain,
Yes. I write the movie reviews column:P
But anyone with a CS degree at least should understand the basics of why big primes make good private keys
Indeed. Although it should be noted that Mersenne primes are sort of useless for this. If you know one of the factors is a Mersenne Prime then there are only 47 candidates.
True. I don't think I ever would. I can see how some people might though.
Depends what my plans are for immediately before and after.
I tend to walk to the cinema. I've also known people travel by bus and train. This is not the US. People don't all drive everywhere.
The cameras on laptops tend to be pretty cheap things that are designed for video conferencing. They'd be abysmal for recording a movie.
On the other hand, smuggling in a reasonable quality camera would be fairly easy. I dare say it would be possible to bring in a tripod as well.
It makes sense if it's a simple business decision rather than a boycott.
If a partner business makes your business unprofitable, then it makes sense not to do business with them.
I have one. The stylus input device works quite well for drawing, but the UI sucks. There's not even a delete function. Battery life seems to be very good though.
Yes. Polarised sunglasses have the same polarisation on each lens. Presumably different levels of glare in each eye is going to be slightly disorienting. Although probably not enough as to need a warning.
Basic depth perception has its uses. Mainly this is for perceiving depth. But binocular vision is just one of the clues the brain uses. We get a certain amount of depth perception just from perspective.
Add head tracking. It would allow the user to look around 3D windows. Items could actually float within the screen (and even in front to an extent).
Which one will you tend to pick? The one who sees every problem as a nail and uses a complicated process to solve simple problems? It seems a remarkable poor metric for determining skilled programmers.
It strikes me as a highly illogical question. Are you suggesting that a computer programmer wouldn't see programming as a solution to a problem that by definition needs software?
I think I'd provide some hypothetical examples of problems that might be solved and ask them how to go about it. Some of the problems may well have an existing solution. I'd ask the applicant about their solutions, and suggest alternative solutions and ask them about the pros and cons of them.
Or they're perfectly competent engineers who know how to learn, have interesting and varied projects at work, and have other interests.
Learning an API doesn't take long. Even learning a new programming language doesn't take long if it's similar enough to one you know. Very few jobs use the same language and API for a particularly long time. The skills they learn in their free time are not all that likely to be relevant to the job that you hire them for. Not programming in your free time doesn't mean not using computers in your free time. Very few problems at home need programming to solve them.
My last coding job, I was doing AI research and optimisation. Sometimes software development jobs are interestng.
Really? When I talk to my wife, a completely different message is received by her half the time.
Someone with experience in C++ will use exceptions, STL, and the new/delete operators, because these are much nicer than the C equivalents. They'll rarely need to worry about the actual size of a data type. Knowing the C specific parts of C++ is certainly very important but that doesn't actually mean you'll know how to write a decent C program.
I'd actually be more inclined to hire a C++ programmer for a C# project than a C project.
In terms of memory, 64 bits can address 18 exabytes. Even Google isn't going to be using that for a decade or so. Assuming Moore's law continues, it will be about half a century before PCs need that much RAM. Dealing with 128 bit numbers for mathematics is of limited use (if you do want to deal with them, you'll probably have a need for 256 byte and 512 byte numbers as well).
And it's not like there's been much perception of a need for 128 bit CPUs. 64 bit processors have been around since the 1960's with fairly mainstream CPUs sine the early 90s. I don't think this is like RAM. I think there's a limit to how many bits we can use.
It leads to an interesting problem though. Suppose I sell you a copy of a GPL product and the source code on two separate CDs. You then sell Person B the source code CD and he sells it to person C. Is Person B obliged to provide the source to Person C on request even though he isn't capable for doing this?