edster

The stack ranking system is really known as the "GE Way" and is one of the reasons Jack Welsh is famous and made a ton of money selling management books.

IBM also employed the 20/70/10% concept to employee reviews in the 90s.

For some reason there is always common confusion between legally having a monopoly/monopoly power and abusing a monopoly/monopoly power.

The problem wasn't that MS was bundling a free browser. The problem was when Microsoft forced PC builders to not only include Internet Explorer but explicitly forbid them from including another browser as part of their offering.

Additionally, Microsoft artificially integrated IE into Windows and then tried to claim that the two were designed to work together. It was easily demonstrated that Windows continued to work fine after un-bundling IE.

I'm looking at this as an iOS developer and not a Mac App developer, but I think this is overblown a bit.

In this case, the APIs are the iCloud related features. There are many reasons to allow only approved apps access. First, to some extent Apple are subsidizing the cost of iCloud and they want to ensure that they get their piece of any app using it. Also, it gives Apple the opportunity to make sure that an app that uses iCloud doesn't abuse it. In fact, I've had an iOS app rejected because it was putting to much data in iCloud. (Which wasn't unexpected, the customer for the app was warned it would likely happen)

I'll be worried if it applies to an API not related to a service but rather a core piece of tech.

Just a completely bogus story by someone who must not be a Mac user.

I put my MacBook to sleep and it wakes up instantly. I shut down my MacBook and it takes a min to boot.

I put my iPad to sleep and it wakes up instantly. I shut down my iPad and it takes a min to boot.

It's the exact same interaction. My MacBook will sleep for a day or more with no problem, come back and it's instant on. If it sleeps to the point of killing the battery it hibernates instead where the RAM is written to disk.

I think this guy doesn't understand how well Macs perform with sleep/hibernate/shutdown and he's imagining it works like his generic PC.

Asking how much you should pay to develop a game is pretty much like asking how much does a car cost.

I think the old adage that it takes money to make money is mostly true and applies here as well. Trying to put an app, especially a game, together on the cheap typically results in product that the customer doesn't have an interest in. Getting the right technical and creative resources together is critical.

Sometimes you can strike gold but if you follow this plan you might need to be ready for several failures before experiencing any success.

Here is the direct link to the video:

http://www.1938media.com/windows-mobile-will-be-a-fail/

More time is spent talking about Twitter never being profitable than Windows Phone 7 being a failure. I do actually agree with both of his points of view. I don't think Windows Phone 7 will restore Microsoft to mobile glory and I don't think Twitter will ever make any money.

I've used this before and it's also available in XML format by using the KML format. What's not mentioned and is an extra bonus is that this doesn't require a Google API key. This is just calling a public URL.

NSString startingLoc = [NSString stringWithFormat:@"%f,%f", starting.latitude, starting.longitude];

NSString endingLoc = [NSString stringWithFormat:@"%f,%f", ending.latitude, ending.longitude];

NSString *dirURL = [NSString stringWithFormat:@"maps.google.com/maps?saddr=%@&daddr=%@&output=kml, startingLoc, endingLoc];

(I took off the http: from the string because the text editor insisted on turning it into a url and ended up hiding the interesting output=kml part)

how do you get out from under the bus? Do they have exits that dive under the guard rail? I wish the story had a little more useful info.

Good fix. My MacBook plastic is chipping apart and I just fixed that using a leftover invisible shield I had for my Newton screen that was sitting in my desk drawer.

I never even used a shield on the Newton, I preferred to ride it bare back just like I prefer with my iPhone. This seems like the most pain free option, although it concerns me that I have to fix all my Apple products with screen shields.

Uggg, horrible font for a blog or any type of extended reading. However, interesting moral decision we all face at various points in time.

It's discussed like an economics decision, but I see it more as a gambler's decision. To me it's about the bankroll and the ability to sustain several losses in a row while waiting for the odds to even out.

I waited to jailbreak my original iPhone until I got my new 3GS. I wonder why that is?

Should we automatically believe the author of the post that he didn't try overclocking the CPU while tinkering with it? That the jailbreak didn't exploit a hole in a power management routine which ended up with a nasty side effect?

I'm sorry people, but I have to agree with Apple/Motorola and the corporate types on this. Software can impact the hardware, so yes indeed tinkering with the software can void the warranty of the hardware.

point?

<sorry, inside joke to one of grandalf other comments>

The point is the single data point you are providing. Finding iPhone 4 users with this same data point of not having a problem point to the fact the you entirely missed the point.

This video is out of date and should not be referenced.

Mainly, the cross compile approach he is mentioning is now not permitted under the "Flash Fix" in the developer agreement that Apple came up with, which requires apps to be written using only native tools.

What's funny, at least I think, is that Apple used to support Cocoa Java which looked very much like the java implementation being shown in the example.

I would say it's pretty much accurate minus the sex with Jennifer Aniston.

I'll save you 90 min of your time. Instead send me two dollars and I'll tell you the secret is to put up a web site that convinces people to drop money on some video you probably stole from somewhere else. Oops, just gave it away without collecting the two bucks.

The study was interesting, yet by the author's own words incomplete with only something like 24 participants. Even then, I wasn't clear if each of the 24 read three different stories, one per device, or how the breakdown went.

Also, a sensationalist headline to attract hits, the comparison was among paper, the Kindle and the iPad. Why not "Reading on paper is faster than reading on iPad or Kindle"?

Finally, while the whole study was pretty pointless, reading on the iPad was slightly better than reading on the Kindle but within the margin or error.

I was just going to comment on that very same thing. The guy is only a day into the job, so what does he know, but didn't offer anything that would lead one to conclude they Nokia is changing anything. He didn't address the problems brought up by symbian-guru at all.

Interesting information as always from useit. However, the conclusion of the test, which was that there wasn't a conclusion was chuckle inducing. Too bad they didn't throw the Kindle iPad app into the mix.

Who cares if the product is hyped or not. Who cares if the guy next door already has one.

I don't use google for search because everyone else does, I use it because it works for me. If I start to find that Bing works better, I'll switch to that. Who cares if everyone else is using google or not.

Saying you don't want to use an iPhone because it's too locked up makes sense, even though I don't agree with that position. Saying you don't want to use an iPhone because of hype and fashion, that's cutting off your nose to spite your face.

I can't reply as a funded person since I'm also a bootstrapper, but having done work for some startups they typically have directors which work for the funding group that sit around and make sure their money is working hard. So I imagine they have less flexibility.

You can look at it that way, but not so much true. The great thing about being a self employed is that it doesn't matter where you work.

I take my computer with me everywhere I go, even on vacation. I've had conference calls in the morning and hit Disney World in the afternoon. Usually my customers don't even realize I'm out and about.

So while you could say that your not really on vacation just remote, you could look at it the other way and realize you could spend a month in Florida on vacation and still make a few bucks in the process. I've been on vacations that have paid for themselves simply by putting a little work in for half a day here and there.

If we assume that the person is a real recruiter, then I would say it probably won't be a real problem.

For the most part, the recruiting game can be fragile. The recruiter has to carefully cultivate the hiring managers they work with and mis-representing a resume or drowning the hiring manager in a storm of unqualified junk resumes will lead to a short career in the business.

You resume might be presented without your knowledge and with your name deleted to jump on an opportunity. The old "I've got a guy, let me see if he's still available". Of course they don't want to sell the manager on a guy they don't have because if the manager becomes enamored with that resume it might mean he'll be less interested in seeing the other guys the recruiter does have.

If we assume this guy is something other than a real recruiter, all bets are off.

In some big companies, the first company to get a person into the system "owns" that person. So it's in the recruiting companies interest to get as many people submitted as quickly as possible.

Another thing with big companies, they sometimes have policies that require them to post jobs and gather candidates from outside, but often they really just want to make the move internally and the recruiting companies and guys like yourself are just collateral damage.

In other words, the course of events doesn't necessarily suggest underhanded play by the recruiter.

Kind of a fluff article, but I'll take the bait.

1. Fragmentation: Given Nokia's "Strong" 44% marketshare, even splitting up the share into three different OS equally would mean 15% each, or about the size of iPhone and Android share. Big enough that developers would target it if there was any interest.

2. Startups: The old throw a bucket a money at the problem to make it go away. Give developers a good business proposition and they will create products. Whether it's direct investment or potential upside based on revenue sharing and mass market doesn't matter.

3. Games: I don't know about the statement that big IP games aren't being created for iPhone. I would dispute that. Nokia had a huge lead in mobile games that they squandered.

4. Make a better store: I think a differentiator would be a curated store and a side loading option. This is a good point

5. Create evangelists: Sorry, but Jobs isn't an evangelist for Apple, John Gruber is. Creating fake evangelists is just a way of saying astroturfing. Evangelists are created for free by offering something compelling to evangelize.

6. Rebuild trust: You can't send out a press release saying you are now developer friendly. It needs to be proven through action.

7. Be more humble: Cause Apple is known for being humble! Developers want to know they can make money, customers want their product to be reliable and fun. Nothing else really matters.

Great post.

I agree he was a bit unprofessional. Gates' awareness probably did fall off as his earlier emails were buried under the mountain of new stuff. Rather than shouting "Hey look at me" he should have sent a gentle reminder about improvements that have been made in the last week or whatever. Bring him back to top of mind in a positive way. Who wants to get stuck working with a guy that annoying.

Copying Jobs as if he were an active part of the project is a total dick move, BTW. He should be thankful that Steve routed him to the right person. The only future communication to Jobs should have just been a quick thank you for the introduction.

"Time to stop butting into other peoples business," edster tells the super-rich

used to be that there were 12 or 13 DNS root servers. I don't know if that is still the case.

I don't know if the president could shut down the internet or not, but I'd like to see him try. That would be all kinds of crazy fun.

hmmm, for some reason I can't reply directly to @gaius' comment. I find the I love my BB argument interesting. While he's right, I don't understand the attraction for these people.

I've been doing some BB development lately using a Storm II. Compared to the iPhone 3GS, it's a flying turd. I wonder if these BlackBerry lovers just haven't tried an iPhone or Android device.

Maybe I would think differently if I was testing on a keyboard device like a Bold, but I can't imagine it would change my opinion that much.

The SuperAMOLED display is supposed to mitigate the sun factor, so it will be interesting to see how it works. I'm sure Apple has evaluated that tech, but chooses not to use it for some reason whether it's cost, availability or simply the fact that it's not yet good enough.

Personally, when I use the iPhone in bed with my glasses off and I surf or watch something, I see pixels. I can't wait to see how the new screen performs.

You characterize the fact that they went super high resolution to accommodate existing apps as a bad thing? How many other companies would have chosen the cheap and easy way out? I say most. This is one example of Apple's focus on the consumer that separates it from the competition.