nigelsampson

Agreed, that's the first question as soon as I saw the concept.

I've found a lot of companies don't like giving feedback of negative outcomes for fear of opening themselves up to some sort of liability around discrimination.

Realistically it shouldn't be a problem if they handled the interview correctly, but some prefer not to take the risk.

Would love to see RavenDB http://ravendb.net/ supported in the same way as MongoDB.

Based off my wife's experiences here in New Zealand while planning the wedding this practise is very common in the wedding dress industry.

Agreed, constructor injection is pretty much the only type of "dependency injection" that makes sense to me.

The less magic the better.

I enjoyed Load and Reload, gave up after buying St Anger.

Favourite album is S&M.

In New Zealand I do remember a instance where a politician voted against what they personally believe in due to what their electorate wanted. Sadly the details escape me at the moment.

It's interesting how it talks about how employees aren't loyal to companies, I think a lot of this is because most companies don't show much loyalty to their employees. Although it seems more likely in start ups.

When companies show loyalty to their staff and not lay them off at the first sign of trouble, really think about compensation (so that employees don't have to consider changing jobs as the only way to get a pay rise) then they may see more loyalty from their employees.

Agreed, I've owned my first smartphone (an HTC Trophy) for about a year now, the last six months having the data connection on (using prepaid data). It certainly makes the phone a whole different experience.

I think this is a problem that surrounds us in tech, that we approach everything with the notion of "for x to win, y must lose".

I suspect the overall decrease is because the growth of Windows Phone isn't as strong as the decline of Windows Mobile.

Overall I think it would have been a good idea if Microsoft had done better in separating the brands. Right now its to confusing for the average user if reporters can't get it right.

This also doesn't take into account the impact that being stricter on cheating had on the non-cheating members of the class.

Most of the your examples look like they're caused by the base class library not keeping up with language advancements. Which I agree can be a real issue.

I wonder if this was in reaction to the same pricing change from MS Azure http://blogs.msdn.com/b/windowsazure/archive/2011/06/22/anno...

This seems the most likely option in my opinion. A lot of panic and scaremongering based off a few snippets.

I imagine we'll see other ways to build into the tablet UI apart from html5/js.

Series was one thing I added to my blog as a way to group posts into a ordered series and so to let people see related content. I think its become very useful.

Exactly OAuth works well on the web when the requesting application doesn't have control of the browser.

In any situation where the requesting application controls the browser you may as well just hand it your password.

This approach which is very common completely breaks the security OAuth was designed for.

If my app hosts the browser control, then there's nothing stopping me injecting custom javascript into the page to listen for input events.

Not to mention having to store the key / secret in the app (unless you use a proxy).

OAuth fails for mobile.

You can do it on the WP7 marketplace using the clumsy messaging built into Zune. Not ideal at all.

Only thing I can suggest is making your contact information highly visible in the app (just above the "review app" button) helps solicit feedback and head off negative reviews.

Making the contact information "tap-able" also increases the effectiveness of this.

Let's hope this doesn't affect the direction of the .net platform. There's been a lot of great change lately with more open source work, smaller and more frequent revisions in platforms such as MVC. I'd hate to see it fall to the wayside.

We used to give it to candidates who showed up overly early to interviews. Something reasonably simple they could do waiting in reception while we got people together for the actual interview. I think the success rate was around 50% with the most common error being incorrect conditionals.

They have done this with Facebook, after setting up your People hub becomes a merged list of both your contacts and facebook friends. Status updates from both etc.

I believe similar Twitter integration is in the works.

In New Zealand, Fatso competes with physical rental. http://www.fatso.co.nz

It's nice to see more comments around that there will never be a one solution to fit all the problems (as much as geeks seem to want to find one) especially from Microsoft.

Agreed, the lack of enum support drives me nuts. Hell I wrote an ORM in the .Net 1.1 days that had it.

Still I'm glad they've released this, more "out of band" releases from Microsoft are a good thing. When frameworks and features aren't tied to Visual Studio releases mean the individual teams can iterate a lot quicker (the MVC and Silverlight teams are good examples).

With toxins this deadly you're safe until you're dead. Unless you're lucky like the guy in the story and inhale the toxin.

I learnt C programming Quake 2 modifications, picked up C++ at university and haven't used it since.

Agreed, my initial thought was this was a sim-nation style game.

The development tools require either Vista or Windows 7 as per the release notes http://download.microsoft.com/download/1/7/7/177D6AF8-17FA-4...

Some of these I think are valid points, the update process needs to be improved. Currently it feels like the WP7 update process sits somewhere between iOS and Android, all the problems of both and the benefits of none. Smaller updates released more regularly would go a long way to solve these issues.

The marketplace update process I've never had a problem and I've used both Firefox and Chrome never IE. I'd love to hear some of the marketplace rules that he feels are broken. Most to me seem pretty up front.