1. Programming skill is more likely to have a power law distribution rather than a normal distribution. That is, lots of very unskilled people, a chunk of decently-skilled people, and a handful of "rock stars." This would more closely match the distributions (and success rates) of other skills. This also matches my experience working with programmers of varying skill levels for more than twenty years.
2. You can teach a lot of the concepts but there is an inherent knack for logical thinking that is very hard to teach. If one has this knack, new concepts are easily grasped, solutions to problems using currently-known tools are more easily found, and troubleshooting is simpler. If one DOESN'T have the knack, they can still be successful, but it is harder, requires substantially more effort, and more of their time will be taken at each step.
It's not always pobox where someone sits on the talent distribution. This is also not a perfect predictor of their ability to produce; some people are very bright but unmotivated and unmotivatable. I would rather have someone with Leeds talent who was willing to work and produce. It's also important for a team to code to roughly the same competence level; if you have one rock star who writes code that no one else understand, you create a bottleneck for yourself on that one person being able to work with that code.
I have an Android tablet (which I'm using right now to enter this post) and an iPad. I've had both for years and I've done some development for them.
People DO use these things to be productive, but they are the exception rather than the norm. Part of the challenge is that even five years in our whole thinking about what an application should be has been shaped by thirty years of desktop and laptop devices. Anything that truly needs a keyboard (like writing this post) becomes cumbersome, even with something like Swype or SwiftKey. Pens suck, unless you're using a tablet with proper pen support (Note devices are great for this) but even then, most people don't currently need a pen.
It's not just the touch thing, though. It's really, really hard to build a good UI for a powerful app, even on a LARGE screen. To do so on a small screen without eliminating "power" features is almost impossible. And those power features are what people really need for productive work. They might only need 10% of them, but if the one they need is missing, that work has to wait until they can get to a larger device.
I don't think this is incurable, but it's hard to argue that writing a long essay on a 10" touch screen with no hardware keyboard is fun. I know people who use an 11" MacBook Air as their primary coding platform, but I know that I'm far more productive sitting at a desk with a properly-sized monitor and keyboard. (My MacBook Pro plugs in to those things if I have to use it for any extended period.)
Productivity is all about removing obstacles to task completion. From that perspective, tablets satisfy a very narrow slice of uses and fail miserably at the rest.
For non-productive tasks, though... I can sit on the couch and look up stuff while watching TV (for those few things I still watch on TV) and the tablet is far more portable for movie-watching, news reading, and light emailing than a laptop, without being as constricting as even the biggest phones are. I don't carry one everywhere but it's definitely one of the things I think of as I'm walking out the door. My kids love tablets (so I regulate their time on them) and being able to video chat with family is a slam dunk.
You don't NEED a tablet but they are useful. They make excellent primary computing devices for people who ONLY have light computing needs. My late 87-year-old grandmother-in-law couldn't use a computer all that well but she rocked on her iPad.
I believe on the Atari ST version it didn't tell you explicitly like this, it just periodically "crashed" to a solid red screen and you had to reload from your last save, losing your progress and being docked ten points, just as if you had "died".
I already get spam that pretends to be my mail server and instructs me to open the attached file to figure out why "my" message was rejected. Do we really want to encourage this pattern?
Surely there are more targeted ways to advertise to doctors than on national TV during prime time. Those ads aren't for doctors, they're to increase demand among the general population, who can pressure their doctors into prescribing things whether it's in the patient's best medical interest or not.
I just did this math with T-Mobile, I figured I'd break even a little bit before the end of the first year. But it's really going to depend on which phone you try to use. T-Mobile's selection of phones for their monthly plans sucks. A Galaxy Nexus directly from Google looks a lot better, but it's hard to compare apples to apples.
In any case, I won't be staying on a contract plan once my current contract is up. If I elect not to buy new phones at all I'll start saving nearly $70/mo. by switching (two phones).
How many Android owners like it when NO other options exist?
Yes, Flash on phones is horrible. It's only slightly less horrible on tablets. And many SWFs designed for keyboard-and-mice-toting desktop PCs are useless.
All these problems, plus the poor battery life and general sluggishness of Flash, were certainly convenient scapegoats. They're even true. But Jobs wasn't an idiot. He knew that if Flash had been available in iOS, legions of developers would have used it to do an end-run around the app store's restrictions. That's not about money (what Apple makes from the app store is trivial compared to what it makes on hardware) but about protecting the brand. Jobs foresaw a future where Flash became the default development platform for the iPhone, with all the crappy performance it exhibits on Android, and he didn't want that reputation for his product. The iPhone was already taking enough heat from at first requiring devs to make HTML apps; remember that Jobs didn't want native apps available at all.
And for the record, I own no iOS devices, am not an Apple fan, and can completely see where Jobs was coming from.
I've has my Galaxy Tab 10.1 for a couple of months. Before that I had a Nook Color that I rooted. I started with the NC because I wasn't sure if I would have a use for a tablet, and the NC was half the price of the Tab.
There's no doubt these are primarily consumption devices; although they can be used for creation, that's not their strength and the more creative work you do on them the less fun it gets. What surprised me was just how much of my ordinary computer use was consumptive, and that now it's easier to squeeze in a bit of consumption here and there without resorting to a full computer. Instant on, super-long battery life, and an OS that's simplified make a huge difference.
As much as I was surprised how much I now do on my Tab (so much so that my regular computer gets dusty), imagine what it's like for people that really do want a computer "appliance". Apple created an entire market of consumers out of people who previously weren't consumers: people who didn't want the hassle of [another] computer. This is part of the magic of the iPad, and why nearly 30 million have been sold. The TouchPad's demise doesn't tell us much about the tablet market overall except that the TouchPad wasn't what people wanted compared to an iPad. Android has similar market-share (and mind-share) problems, only differing in degree.
Google should be throwing money at devs to write Android tablet apps if they want to catch up to Apple, our even just stay in the game. Otherwise they risk being marginalized, and if that happens on the tablet side it may leak over to the phone side.
The silly thing is, if you do it with a shader in WebGL you can do 3D raytraced fractals in real time in a browser. Doing this kind of thing in JavaScript really just shows how incredibly inefficient at number crunching JavaScript is. I mean, yes, you CAN do it... but really why should you? For the detail levels they're showing, a native application is 1000x* faster.
*Not directly measured. But I have some experience in this area.
Actually that's fine, too. If they start blocking people who don't spend enough money pre-emptively then suddenly they've sent potential future customers directly to their competitors. If you stop someone from even being able to be your customer, you can be certain they will never change their mind.
It's the same thing that happens to sites that have a following, then erect a paywall and discover nobody reads the site any more. They take the paywall down, but the users never come back. Any site that tries to block people based on their non-consuming will find themselves abandoned.
Oddly enough, people were suggesting that the price for the iPad would be $800 or $900 or so, and yet it came out at $500 or $600. Samsung hasn't officially announced their price yet. Speculation is that it will be high, but it might not be.
An Atari 2600 is so amazingly simple that there is little in there to fail. The PS3, on the other hand, has a bazillion failure points by comparison...
Shareholders don't invest money into MS to get no return on their investment; they want to see growth in the stock price and/or dividends, because that's what matters to them. If the stock price stays flat even while profits soar, investors are right to ask where the hell the return on their investment is.
Murdoch doesn't want a paywall. He wants Google to pay him, not the end user, because Google has deeper pockets and it's a battle that can be fought once and won. Getting users to pay would require winning them over constantly and is more work, especially when they're already used to free.
If only it were that simple. Users (a) aren't always aware that they're using an outdated browser and (b) will therefore simply blame your site rather than their browser. Unless you tell them explicitly their browser is at fault, they will not know.
The only reason for CHAP to exist is so that you can avoid sending the password in plaintext over an unencrypted channel. Proper encryption fixes that problem without introducing the greater problem of requiring plaintext password storage.
To be fair, many systems involving end users do store passwords in plain text because a frequent tech support issue is forgotten passwords. I have never built such a system because I've always disclosed up front that this is a bad idea, and we create alternative solutions that don't involve giving out passwords (just resetting them).
PHP being dangerous for novices doesn't make it a poor tool, it makes it a poor tool for novices. C is a useful tool too, and in many cases can be the best tool for the job, but in the hands of a novice it can be dangerous.
The problem isn't PHP specifically (because just about any web-oriented programming language can have similar problems) it's that there are lots of people interested in making dynamic web sites who don't understand the risks. Building and deploying dynamic web sites means subjecting them to possible attack from billions of other people. This is a far different (and bigger) challenge than simply deploying a desktop application, but we still have scads of "tutorials" that treat security as an afterthought.
Web programming is not, nor should it be, something anyone can "whip up" without understanding what they're doing. Think of it this way: "Hey Bob, while you're in that level 4 biohazard lab, why don't you check out this nifty tool I made. I'm pretty sure it won't damage your suit. What? No, I don't have any experience making bio lab tools. Or working in one. Does that matter?"
If Apple is developing an anti-consumer backlash, they have only themselves to blame. Poor customer service, poor developer relations. Obviously some of their competitors will be happy for them to get a bad rap, but you reap what you sow. Apple makes a great product, for as long as it works and you like what it does. When it breaks, or you want to get it to do something outside of Apple's plan for the product, that's where the pain starts.
And other than Hussein being a jerk, it was working--there's no evidence Iraq actually HAD any WMDs. The US just fabricated that story so they could go to war and depose Hussein. All while claiming to be "the good guys".
Depositing money in such a way as to avoid the $10K limit is called "structuring" and it's also illegal, IIRC.
The government does investigate large deposits, but primarily this is so that the IRS can make sure they get paid. I've had them send me a nastygram because I made a nice large deposit and they thought I didn't report it on my taxes; I had to respond and tell them exactly how they missed it. Not really very cool, but remember the primary reason is about money. Too many people deposit $10K or more perfectly legitimately for them to get their panties in a wad over every case.
Slashdot Mirror
1. Programming skill is more likely to have a power law distribution rather than a normal distribution. That is, lots of very unskilled people, a chunk of decently-skilled people, and a handful of "rock stars." This would more closely match the distributions (and success rates) of other skills. This also matches my experience working with programmers of varying skill levels for more than twenty years.
2. You can teach a lot of the concepts but there is an inherent knack for logical thinking that is very hard to teach. If one has this knack, new concepts are easily grasped, solutions to problems using currently-known tools are more easily found, and troubleshooting is simpler. If one DOESN'T have the knack, they can still be successful, but it is harder, requires substantially more effort, and more of their time will be taken at each step.
It's not always pobox where someone sits on the talent distribution. This is also not a perfect predictor of their ability to produce; some people are very bright but unmotivated and unmotivatable. I would rather have someone with Leeds talent who was willing to work and produce. It's also important for a team to code to roughly the same competence level; if you have one rock star who writes code that no one else understand, you create a bottleneck for yourself on that one person being able to work with that code.
This is why I don't like developing for Microsoft's stack. They seem to want to throw everything out every few years and start over.
Then again, it seems like the web business is like that, too. Damn. Doesn't anyone write non-disposable code any more?
I have an Android tablet (which I'm using right now to enter this post) and an iPad. I've had both for years and I've done some development for them.
People DO use these things to be productive, but they are the exception rather than the norm. Part of the challenge is that even five years in our whole thinking about what an application should be has been shaped by thirty years of desktop and laptop devices. Anything that truly needs a keyboard (like writing this post) becomes cumbersome, even with something like Swype or SwiftKey. Pens suck, unless you're using a tablet with proper pen support (Note devices are great for this) but even then, most people don't currently need a pen.
It's not just the touch thing, though. It's really, really hard to build a good UI for a powerful app, even on a LARGE screen. To do so on a small screen without eliminating "power" features is almost impossible. And those power features are what people really need for productive work. They might only need 10% of them, but if the one they need is missing, that work has to wait until they can get to a larger device.
I don't think this is incurable, but it's hard to argue that writing a long essay on a 10" touch screen with no hardware keyboard is fun. I know people who use an 11" MacBook Air as their primary coding platform, but I know that I'm far more productive sitting at a desk with a properly-sized monitor and keyboard. (My MacBook Pro plugs in to those things if I have to use it for any extended period.)
Productivity is all about removing obstacles to task completion. From that perspective, tablets satisfy a very narrow slice of uses and fail miserably at the rest.
For non-productive tasks, though... I can sit on the couch and look up stuff while watching TV (for those few things I still watch on TV) and the tablet is far more portable for movie-watching, news reading, and light emailing than a laptop, without being as constricting as even the biggest phones are. I don't carry one everywhere but it's definitely one of the things I think of as I'm walking out the door. My kids love tablets (so I regulate their time on them) and being able to video chat with family is a slam dunk.
You don't NEED a tablet but they are useful. They make excellent primary computing devices for people who ONLY have light computing needs. My late 87-year-old grandmother-in-law couldn't use a computer all that well but she rocked on her iPad.
I believe on the Atari ST version it didn't tell you explicitly like this, it just periodically "crashed" to a solid red screen and you had to reload from your last save, losing your progress and being docked ten points, just as if you had "died".
I already get spam that pretends to be my mail server and instructs me to open the attached file to figure out why "my" message was rejected. Do we really want to encourage this pattern?
Surely there are more targeted ways to advertise to doctors than on national TV during prime time. Those ads aren't for doctors, they're to increase demand among the general population, who can pressure their doctors into prescribing things whether it's in the patient's best medical interest or not.
I just did this math with T-Mobile, I figured I'd break even a little bit before the end of the first year. But it's really going to depend on which phone you try to use. T-Mobile's selection of phones for their monthly plans sucks. A Galaxy Nexus directly from Google looks a lot better, but it's hard to compare apples to apples.
In any case, I won't be staying on a contract plan once my current contract is up. If I elect not to buy new phones at all I'll start saving nearly $70/mo. by switching (two phones).
How many Android owners like it when NO other options exist?
Yes, Flash on phones is horrible. It's only slightly less horrible on tablets. And many SWFs designed for keyboard-and-mice-toting desktop PCs are useless.
All these problems, plus the poor battery life and general sluggishness of Flash, were certainly convenient scapegoats. They're even true. But Jobs wasn't an idiot. He knew that if Flash had been available in iOS, legions of developers would have used it to do an end-run around the app store's restrictions. That's not about money (what Apple makes from the app store is trivial compared to what it makes on hardware) but about protecting the brand. Jobs foresaw a future where Flash became the default development platform for the iPhone, with all the crappy performance it exhibits on Android, and he didn't want that reputation for his product. The iPhone was already taking enough heat from at first requiring devs to make HTML apps; remember that Jobs didn't want native apps available at all.
And for the record, I own no iOS devices, am not an Apple fan, and can completely see where Jobs was coming from.
I've has my Galaxy Tab 10.1 for a couple of months. Before that I had a Nook Color that I rooted. I started with the NC because I wasn't sure if I would have a use for a tablet, and the NC was half the price of the Tab.
There's no doubt these are primarily consumption devices; although they can be used for creation, that's not their strength and the more creative work you do on them the less fun it gets. What surprised me was just how much of my ordinary computer use was consumptive, and that now it's easier to squeeze in a bit of consumption here and there without resorting to a full computer. Instant on, super-long battery life, and an OS that's simplified make a huge difference.
As much as I was surprised how much I now do on my Tab (so much so that my regular computer gets dusty), imagine what it's like for people that really do want a computer "appliance". Apple created an entire market of consumers out of people who previously weren't consumers: people who didn't want the hassle of [another] computer. This is part of the magic of the iPad, and why nearly 30 million have been sold. The TouchPad's demise doesn't tell us much about the tablet market overall except that the TouchPad wasn't what people wanted compared to an iPad. Android has similar market-share (and mind-share) problems, only differing in degree.
Google should be throwing money at devs to write Android tablet apps if they want to catch up to Apple, our even just stay in the game. Otherwise they risk being marginalized, and if that happens on the tablet side it may leak over to the phone side.
The silly thing is, if you do it with a shader in WebGL you can do 3D raytraced fractals in real time in a browser. Doing this kind of thing in JavaScript really just shows how incredibly inefficient at number crunching JavaScript is. I mean, yes, you CAN do it... but really why should you? For the detail levels they're showing, a native application is 1000x* faster.
*Not directly measured. But I have some experience in this area.
Actually that's fine, too. If they start blocking people who don't spend enough money pre-emptively then suddenly they've sent potential future customers directly to their competitors. If you stop someone from even being able to be your customer, you can be certain they will never change their mind.
It's the same thing that happens to sites that have a following, then erect a paywall and discover nobody reads the site any more. They take the paywall down, but the users never come back. Any site that tries to block people based on their non-consuming will find themselves abandoned.
Oddly enough, people were suggesting that the price for the iPad would be $800 or $900 or so, and yet it came out at $500 or $600. Samsung hasn't officially announced their price yet. Speculation is that it will be high, but it might not be.
An Atari 2600 is so amazingly simple that there is little in there to fail. The PS3, on the other hand, has a bazillion failure points by comparison...
Numeric grades are just as prone to inflation.
Shareholders don't invest money into MS to get no return on their investment; they want to see growth in the stock price and/or dividends, because that's what matters to them. If the stock price stays flat even while profits soar, investors are right to ask where the hell the return on their investment is.
Yes, games exist that teach kids things besides how to use computers and how to play games. 360Ed makes some. (Disclosure: I work there.)
Murdoch doesn't want a paywall. He wants Google to pay him, not the end user, because Google has deeper pockets and it's a battle that can be fought once and won. Getting users to pay would require winning them over constantly and is more work, especially when they're already used to free.
Stop playing your driving games in third-person view.
If only it were that simple. Users (a) aren't always aware that they're using an outdated browser and (b) will therefore simply blame your site rather than their browser. Unless you tell them explicitly their browser is at fault, they will not know.
The only reason for CHAP to exist is so that you can avoid sending the password in plaintext over an unencrypted channel. Proper encryption fixes that problem without introducing the greater problem of requiring plaintext password storage.
To be fair, many systems involving end users do store passwords in plain text because a frequent tech support issue is forgotten passwords. I have never built such a system because I've always disclosed up front that this is a bad idea, and we create alternative solutions that don't involve giving out passwords (just resetting them).
PHP being dangerous for novices doesn't make it a poor tool, it makes it a poor tool for novices. C is a useful tool too, and in many cases can be the best tool for the job, but in the hands of a novice it can be dangerous.
The problem isn't PHP specifically (because just about any web-oriented programming language can have similar problems) it's that there are lots of people interested in making dynamic web sites who don't understand the risks. Building and deploying dynamic web sites means subjecting them to possible attack from billions of other people. This is a far different (and bigger) challenge than simply deploying a desktop application, but we still have scads of "tutorials" that treat security as an afterthought.
Web programming is not, nor should it be, something anyone can "whip up" without understanding what they're doing. Think of it this way: "Hey Bob, while you're in that level 4 biohazard lab, why don't you check out this nifty tool I made. I'm pretty sure it won't damage your suit. What? No, I don't have any experience making bio lab tools. Or working in one. Does that matter?"
If Apple is developing an anti-consumer backlash, they have only themselves to blame. Poor customer service, poor developer relations. Obviously some of their competitors will be happy for them to get a bad rap, but you reap what you sow. Apple makes a great product, for as long as it works and you like what it does. When it breaks, or you want to get it to do something outside of Apple's plan for the product, that's where the pain starts.
And other than Hussein being a jerk, it was working--there's no evidence Iraq actually HAD any WMDs. The US just fabricated that story so they could go to war and depose Hussein. All while claiming to be "the good guys".
Depositing money in such a way as to avoid the $10K limit is called "structuring" and it's also illegal, IIRC.
The government does investigate large deposits, but primarily this is so that the IRS can make sure they get paid. I've had them send me a nastygram because I made a nice large deposit and they thought I didn't report it on my taxes; I had to respond and tell them exactly how they missed it. Not really very cool, but remember the primary reason is about money. Too many people deposit $10K or more perfectly legitimately for them to get their panties in a wad over every case.
GoDaddy turbo certs are $20 and only require the email address on the domain validates.