The Surface has a place. 90% of the corporate world use x86 apps, good luck running those on any other tablet.
Good luck running them on the surface pro too, when you discover you can't actually click the tiny buttons, hover over things, or right click on things.
There's a reason those god awful windows XP tablets from years ago never caught on –it's because they weren't actually capable of running any of the software that "ran" on them.
Surface Pro is the best tablet that can run x86 applications. Show me another machine that is as thin, light, and powerful with a stylus. You can't.
The problem is that it isn't good at it, as the parent pointed out.
So I want to run an x86 windows application... What's that? I need to tap on a very small area to activate this button designed for use with a mouse? Crap. What's that? I need to hover over this item as I could if I had a mouse? Crap. What's that? I need to right click this item, as it was designed to work with a mouse? Crap.
Running x86 windows applications is not an advantage on a tablet.
Actually, Sony would probably be relatively pleased. It's in their interest to get game devs using APIs like OpenGL and OpenAL for their engines, only Microsoft would see it as a bad thing as it would help unlock their D3D lock out.
Linux isn't what people are being asked to have confidence in. Valve is. Valve is a big name. People have confidence in it, especially in the games industry.
Do you honestly believe that Valve, singlehandedly, is capable of producing enough content on their own exclusively for their device (because if they also make it for windows, then people won't generally bother getting the console because it is traditionally exclusive content that moves consoles), that people would bother to get one?
How much unique content did Sony or MS manage to create for the PS3 or XBox 360? The answer is not very much, they don't need to, and nor do Valve –only have the content the others do, plus one or two interesting titles. Every console maker has been able to do this when they've released their new shiny box. And just like Sony could do it for the PS/PS2/PS3, Valve will be able to do it for the Steambox, because they have clout.
And what incentive will other game studios have to make games for this console that is running an OS that's been around for 20 years, and not once gotten to even 2% of the end-user consumer computer use outside of the server market?
The exact same incentive they had to make games for the PS3, which runs an OS that hadn't even existed for 1 year, and not once got to even 0.0000001% of the end user market share. That it has a major manufacturer behind it, who has a lot of clout, and can make it happen.
Valve will then of course do exactly what Nintendo/Sony/MS do to make sure games studios get working on games for their device. This in turn will have the side effect that every game released for steambox will also be available on Linux. Given that almost all of the APIs for linux (and I'd bet heavily 100% of the ones Valve say are guaranteed to be available) are also available on Mac OS, and I'd bet that you're looking at all those games also being available for Mac OS.
That will if nothing else, significantly weaken MS's strangle hold on the gaming world.
They would bother because the only thing that's currently holding them back from using linux/Mac OS is having their games available.
And since when have they announced their pricing for the steam box? They announced that their dev kit was roughly as fast as a $1000 PC (though the specs look more like $7-800 to me). Given that it'll only be launched in about a year, that'll mean that that speed will be achievable with $5-600 consumer parts. Add into that that valve will be getting OEM prices, and it'll likely be $400-450 to them, add to that that they'll probably launch it at a loss, and you're looking at $300 for their high end version. That's an entirely reasonable price for a console in this day and age.
It was not stringy because the chef knew what he was doing. Coincidentally, it was very rare because the chef knew what he was doing. Horse meat has very little fat, and needs to be cooked very little and very fast, or it ends up tough.
Yep, and actually they did even more than that, Apple had the first unprotected music legally available too –they got EMI to make the switch. The rest of the then big 4 then decided to use it as a bargaining chip.
Besides, just because "not all drives are TLC", the point still remains that manufacturers are only interested in high margins by selling MLC and now TLC drives, and fuck reliability and longevity.
Except that's the point – the reliability of longevity of these drives is still well above the average of a hard disk (you can reasonably get 7-10 years out of even a TLC 250GB SSD).
Add to that that the short term failure rates of SSDs are much lower than those of HDDs (you're talking 0.5-1.5% per year for non OCZ SSDs, and about 4-5% per year for HDDs), and that the failure mode of SSDs when the flash does finally wear out is that you simply can't write (but can read), and I'll take a TLC SSD over an HDD any day from a reliability stand point.
So, in SSDs' favour:
Reliability
Failure mode
Speed (particularly random access)
Capacity per unit volume (SSDs have actually just overtaken HDDs here, with 1TB fittable in a 7.5mm 2.5" drive compared to HDDs which still need a 9.5mm drive for that)
In HDDs' favour:
Capacity per dollar, but even that lead is being eroded fast, as SSDs are currently keeping up with moore's law, while HDDs aren't keeping up with the equivalent law for spinning rust rather than transistors.
Most employment contracts require you to turn up, and do what someone else tells you to do while present. If you don't do what they tell you to do, then you're certainly in breach of contract.
If he had been a contractor, and simply had to produce the goods, this might have been different.
The key to this is very simple. Carpal tunnel problems do not have to do with being too weak, instead, too strong They're caused by the tendons slowly getting bigger through use, and then rubbing. The rubbing then causes the tunnel of sinews they travel through to inflame, further constricting them and compounding the problem.
Strengthening the tendons further will not help, it will hinder the problem.
Regardless of right or wrong the other thing to expect is that sometimes the other guy will be able to better argue their position than you can defend yours. In that case you may find yourself "made redundant" by an ass hat. If that's the case chalk it up to experience and find a better place to work.
Alternatively, if they have arguments that you can't answer, realise that you were in fact in the wrong, and fix your code. This applies to newbies, and old hats alike, you should be listening to other people's arguments and figuring out if they're actually right or not (based on whether you can actually find an answer for why they're wrong).
How do you know the question you asked isn't in some sort of interview prep? You know that's a hot topic. If you like his presented code, ask the programmer to talk about why he did some things in the code in phase 2? You'll know pretty fast if he wrote it.
Because as I said right at the top, a lot of the point of this is to give you something to talk about in the interview –you ask them about their bugs in the telephone interview, check they understand what's wrong, ask them what they'd do to fix it, ask them how they would change it given more time, ask them where they think it would be useful code, ask them why they made certain choices over certain others, etc.
I don't understand why employers don't just ask to see some code the developer has already written.
I expect to see that in the CV, and it's a prerequisite of getting to the "now write me some simple code in very little time" stage. The latter test stage eliminates the people who submitted code someone else wrote.
Heh, your pseudo code is sufficient that I would actually reject you even though it's "correct".
You have a conceptual type error. You conflate integers and booleans as being one type, that kind of muddy thinking makes for poor code (even when programming in languages like C where the two really are conflated).
You only interview people with significant credentials.
You've never interviewed people clearly. The number of people claiming to have done all kinds of things they've never done on their CV is *way* too high to interview people who simply claim to have good credentials.
If someone has 10 years of experience doing bleeding edge stuff, asking him "can you spend a few days of your time, that is worth $1000/day, to do something trivial and entirely useless for free, just to see if you're at least as good as a college graduate?" is not really a good idea.
Who said anything about "a few days of your time" – we're talking about a 45 minute test here...
Which is why you follow up the 45 minute test with a phone interview (which costs more of my time, so I want to do on only people I know are at least BSc level), and that again followed up by a real interview (which costs me yet more time, so I want to do on only people I know can talk reasonably about code design to me over the phone).
Slashdot Mirror
The Surface has a place. 90% of the corporate world use x86 apps, good luck running those on any other tablet.
Good luck running them on the surface pro too, when you discover you can't actually click the tiny buttons, hover over things, or right click on things.
There's a reason those god awful windows XP tablets from years ago never caught on –it's because they weren't actually capable of running any of the software that "ran" on them.
Surface Pro is the best tablet that can run x86 applications. Show me another machine that is as thin, light, and powerful with a stylus. You can't.
The problem is that it isn't good at it, as the parent pointed out.
So I want to run an x86 windows application... What's that? I need to tap on a very small area to activate this button designed for use with a mouse? Crap. What's that? I need to hover over this item as I could if I had a mouse? Crap. What's that? I need to right click this item, as it was designed to work with a mouse? Crap.
Running x86 windows applications is not an advantage on a tablet.
Actually, Sony would probably be relatively pleased. It's in their interest to get game devs using APIs like OpenGL and OpenAL for their engines, only Microsoft would see it as a bad thing as it would help unlock their D3D lock out.
Linux isn't what people are being asked to have confidence in. Valve is. Valve is a big name. People have confidence in it, especially in the games industry.
Do you honestly believe that Valve, singlehandedly, is capable of producing enough content on their own exclusively for their device (because if they also make it for windows, then people won't generally bother getting the console because it is traditionally exclusive content that moves consoles), that people would bother to get one?
How much unique content did Sony or MS manage to create for the PS3 or XBox 360? The answer is not very much, they don't need to, and nor do Valve –only have the content the others do, plus one or two interesting titles. Every console maker has been able to do this when they've released their new shiny box. And just like Sony could do it for the PS/PS2/PS3, Valve will be able to do it for the Steambox, because they have clout.
And what incentive will other game studios have to make games for this console that is running an OS that's been around for 20 years, and not once gotten to even 2% of the end-user consumer computer use outside of the server market?
The exact same incentive they had to make games for the PS3, which runs an OS that hadn't even existed for 1 year, and not once got to even 0.0000001% of the end user market share. That it has a major manufacturer behind it, who has a lot of clout, and can make it happen.
Oops, forgot to follow up.
Valve will then of course do exactly what Nintendo/Sony/MS do to make sure games studios get working on games for their device. This in turn will have the side effect that every game released for steambox will also be available on Linux. Given that almost all of the APIs for linux (and I'd bet heavily 100% of the ones Valve say are guaranteed to be available) are also available on Mac OS, and I'd bet that you're looking at all those games also being available for Mac OS.
That will if nothing else, significantly weaken MS's strangle hold on the gaming world.
They would bother because the only thing that's currently holding them back from using linux/Mac OS is having their games available.
And since when have they announced their pricing for the steam box? They announced that their dev kit was roughly as fast as a $1000 PC (though the specs look more like $7-800 to me). Given that it'll only be launched in about a year, that'll mean that that speed will be achievable with $5-600 consumer parts. Add into that that valve will be getting OEM prices, and it'll likely be $400-450 to them, add to that that they'll probably launch it at a loss, and you're looking at $300 for their high end version. That's an entirely reasonable price for a console in this day and age.
You're right, but as you say –you need fat for braising it slowly. And would need to add it from another source.
It was not stringy because the chef knew what he was doing. Coincidentally, it was very rare because the chef knew what he was doing. Horse meat has very little fat, and needs to be cooked very little and very fast, or it ends up tough.
Not at all –British and American attitudes towards slaughtering/eating horses are very similar. We're not the Belgians you know ;)
wasn't amazon selling non-drm music for years before apple?
No, Apple were first with EMI. The rest of the big 4 held back from apple, so amazon were the first to have all their catalog unlocked.
Yep, and actually they did even more than that, Apple had the first unprotected music legally available too –they got EMI to make the switch. The rest of the then big 4 then decided to use it as a bargaining chip.
You mean all of plusnet's user's IP, not mine :P
Besides, just because "not all drives are TLC", the point still remains that manufacturers are only interested in high margins by selling MLC and now TLC drives, and fuck reliability and longevity.
Except that's the point – the reliability of longevity of these drives is still well above the average of a hard disk (you can reasonably get 7-10 years out of even a TLC 250GB SSD).
Add to that that the short term failure rates of SSDs are much lower than those of HDDs (you're talking 0.5-1.5% per year for non OCZ SSDs, and about 4-5% per year for HDDs), and that the failure mode of SSDs when the flash does finally wear out is that you simply can't write (but can read), and I'll take a TLC SSD over an HDD any day from a reliability stand point.
So, in SSDs' favour:
In HDDs' favour:
Most employment contracts require you to turn up, and do what someone else tells you to do while present. If you don't do what they tell you to do, then you're certainly in breach of contract.
If he had been a contractor, and simply had to produce the goods, this might have been different.
The key to this is very simple. Carpal tunnel problems do not have to do with being too weak, instead, too strong They're caused by the tendons slowly getting bigger through use, and then rubbing. The rubbing then causes the tunnel of sinews they travel through to inflame, further constricting them and compounding the problem.
Strengthening the tendons further will not help, it will hinder the problem.
If it didn't exist, then why the need to do something about it, or look like they were doing so?
Regardless of right or wrong the other thing to expect is that sometimes the other guy will be able to better argue their position than you can defend yours.
In that case you may find yourself "made redundant" by an ass hat.
If that's the case chalk it up to experience and find a better place to work.
Alternatively, if they have arguments that you can't answer, realise that you were in fact in the wrong, and fix your code. This applies to newbies, and old hats alike, you should be listening to other people's arguments and figuring out if they're actually right or not (based on whether you can actually find an answer for why they're wrong).
I know that one
You just lost the job.
"I know that one" means I'm not thinking about problems, I'm regurgitating solutions I read on stack overflow.
To be fair, you can write an entirely clear one "like" the second one.
main = putStrLn . unlines . map fizzBuzz $ [1..100]
fizzBuzz :: Int -> String
fizzBuzz x | x `mod` 15 = "fizzbuzz"
fizzBuzz x | x `mod` 3 = "fizz"
fizzBuzz x | x `mod` 5 = "buzz"
fizzBuzz x = show x
How do you know the question you asked isn't in some sort of interview prep? You know that's a hot topic. If you like his presented code, ask the programmer to talk about why he did some things in the code in phase 2? You'll know pretty fast if he wrote it.
Because as I said right at the top, a lot of the point of this is to give you something to talk about in the interview –you ask them about their bugs in the telephone interview, check they understand what's wrong, ask them what they'd do to fix it, ask them how they would change it given more time, ask them where they think it would be useful code, ask them why they made certain choices over certain others, etc.
I don't understand why employers don't just ask to see some code the developer has already written.
I expect to see that in the CV, and it's a prerequisite of getting to the "now write me some simple code in very little time" stage. The latter test stage eliminates the people who submitted code someone else wrote.
Heh, your pseudo code is sufficient that I would actually reject you even though it's "correct".
You have a conceptual type error. You conflate integers and booleans as being one type, that kind of muddy thinking makes for poor code (even when programming in languages like C where the two really are conflated).
You only interview people with significant credentials.
You've never interviewed people clearly. The number of people claiming to have done all kinds of things they've never done on their CV is *way* too high to interview people who simply claim to have good credentials.
If someone has 10 years of experience doing bleeding edge stuff, asking him "can you spend a few days of your time, that is worth $1000/day, to do something trivial and entirely useless for free, just to see if you're at least as good as a college graduate?" is not really a good idea.
Who said anything about "a few days of your time" – we're talking about a 45 minute test here...
Which is why you follow up the 45 minute test with a phone interview (which costs more of my time, so I want to do on only people I know are at least BSc level), and that again followed up by a real interview (which costs me yet more time, so I want to do on only people I know can talk reasonably about code design to me over the phone).