___Calv_Dee___

No SDK love for Canadian developers?

If Microsoft is aiming for an all-in-one situation than they're doing it right. I don't understand why I'm not yet able to have a truly unified experience with all of my devices including smart appliances. I think a hardware maker will have figured it out when they are able to deliver products that provide a consistent interface, delivering smart-content on demand without having to have a gazillion apps. Build devices so they are connected with each other out of the box, not after downloading the remote app and TV guide app and remote desktop app...

But that just adds to the complexity that the "BaaS" is aiming to remove?

Super useful and put together really well, many thanks!

In addition to Quora's main features I use the custom boards to create various "Buckets" so that as I discover content, I can sort it based on what I'd like to use it for. As an example - I have a "Learning Bucket" and a "Stuff Bucket". If I come across some content (article, online PDF, blog post, ...) that will contribute to my knowledge I add it to my Learning Bucket board in case I'd like to read it later or have a quick reference to it. If I come across content I simply find interesting and may want to reference or check out again I add it to my Stuff Bucket board. Quora provides a really clean interface to organize your content and I highly recommend trying it out if not solely for this purpose!

To follow up... This seems to be a good start http://code.google.com/edu/parallel/dsd-tutorial.html

What I was trying to get at is that, at a more abstract level, this process should not be a BASIS for innovation or creation.

I can definitely see the benefits of using this tool as a brainstorming function, however why try and force ideas to create a startup. The function of a startup is to make a company in order to respond to a need. I believe that need is only going to be fully satisfied when the company/person/startup addressing it has some underlying attachment to the core issue. Grabbing a hold of an idea that is a result of some exterior process, to me just seems wrong and lacks a genuine intention.

In my opinion, the notion of an "algorithm for generating new ideas for startups" is absolutely appalling. I am far from an expert in the field of startups but I have enough knowledge (at the very least from a consumer's point of view) on the matter to know that great products are crafted by imagination and passion. Having a process decide what a "good startup idea" would be completely takes away from the base imaginative thought. Furthermore, how are you to become passionate on an issue that was brought to light by a process rather than intuition?

Sure there may have been a lot of expectations and some hype for new up and coming Windows releases but this will be the first time that Microsoft will be providing such an overhauled (design and function) OS available across mobile and desktop. It's a necessity for Microsoft to get the platform integration right in order to stand a chance against the wonderfully integrated ecosystem model Apple has really set a standard for. This is definitely, in my opinion, far from "the same".

http://gigaom.com/2012/02/28/why-windows-8-is-microsofts-mos...

Neat but as expressed in the post, it's "really just a cool implementation of a combined projector and camera".

This webinar by Brian Mulloy is a nice complement to the post and offers up some great design tips when it comes to designing a RESTful API...

http://blog.apigee.com/detail/slides_for_restful_api_design_...

This is pretty vague, what kind of help are you looking for? You can learn everything you need to know (and by everything, I mean just that) via online resources if you're willing to spend the time and can exercise some patience. I'd recommend deciding on a starting point for "learning computer skills" and working through some credible tutorials focussing on one area at a time. Whenever you come across a concept/term that is not clear or makes absolutely no sense to you, keep track of where you were in the tutorial and consult Wikipedia for clarification. Perhaps you'll find another concept/term on a Wikipedia page that you are unfamiliar with. Veer off and check out that resource as well. Once you've grasped all of the associated concepts and terms, return to the tutorial. You'll be amazed at how much you've learned. I think this is a much more satisfying approach than paying someone to teach you computer skills!

I think that "web-appropriate" is actually becoming the "appropriate" way to do things in the publishing realm. The massive shift to web-based content is certain to yield the deprecation of such a term.

Great, just as I'm moving away from PHP and diving into Ruby (I've fallen for it's OO charm), they have to release such a wonderful engine. This is amazing though, well done.

I don't understand how this makes it to Top News. I think at this point we are all well aware that no user-password store is impenetrable or invulnerable and porn websites would hardly be an exception. If you do not know by now that you should not be using the same password across multiple accounts, it seems like there is little hope. There is no lesson to be learned here. Is it not an implicit assumption that if you subscribe to a porn website someone is mostly likely going to find out one way or another?

1. Don't reuse passwords. 2. Don't subscribe to porn sites if you have something to lose from someone finding out.

I completely agree, it's great to see that the language continues to move forward and advance in it's OO design. It's especially nice that these forward steps do not hinder or reduce Obj-C's low-level functionality, leaving available the performance gains from it's use.

Apple, as usual, really seems to be getting it right. The feature list looks super promising as a nextstep (sorry, had to) in unifying mobile with desktop. It's nice to see that the desktop OS is not being abandoned but instead updated to better reflect a consumers preference for mobile (with good reason). Microsoft has also got it right by tying their Metro interface in Windows 8 to the Windows Phone OS. The attempt, however, falls short in that it is not really unifying the two platforms but instead providing a common interface and feel. In order to truly unite desktop with mobile, I believe you need to go beyond providing a common interface and really integrate the components so they exist to the user simultaneously instead of in parellel. This is just another verification (and in my opinion, a big one) that mobile is taking the reigns and is the future.

I feel like this would be a common mistake when getting caught up in the moment of completing a dev project. You're so anxious to launch the site/app that load balancing factors could be overlooked. This seems like it could be really detrimental as you're pretty much canning your first impression when your backend crashes. Anyone up for sharing their horror stories of launching before their backend could handle the traffic? I feel like it could provide for some good insight in regards to patience and thought when it comes to launching.

We need more minimalistic apps like this.

I think I presented a trade-off rather than undermining my own argument although I didn't really clarify that I guess.

Essentially you either focus 100% to design and implementing the design via any available technologies (cross-compatible or not) or settle for 80% (20% loss of design and vision from effort in ensuring compatibility).

Ultimately it depends how passionate you are about your design. Personally I would rather have 5 people absolutely fall in love with and be moved by my design/interface/experience rather than 100 people being able to simply 'view' it.

Fantastic post on the beauty of git. The Using git for for deployment article seems like a great micro-intro to git. Nice one!

While it's important to support cross-browser compatibility, it is equally important to deliver to the user the possible design experience. Unfortunately, this may come as a loss to the functionality of non-supporting browsers but I think in the end, it's worth it. Of course we should strive to enforce compatibility but not at the expense of creating a design of lesser-quality (as a result of being wrapped in cross-browser compatibility).