I'll be honest, I stopped reading the article as soon as it mentioned Hypermedia, because I instantly saw the problem as the author being upset that Swagger is not Hypermedia.
I have a really hard time seeing APIs ever reaching that level of standardization, and I'm tired of having the Hypermedia discussion. I generally support logically organized APIs with good documentation. As long as those things are true, I'm happy for the API.
This is my thought as well. Don't think of Nintendo as a technology company, think of them as an Intellectual Property company. With Mario, Zelda, Donkey Kong, Pokemon, Metroid, etc, as their commodities. These will be money makers for decades, regardless of where the platforms go.
The point is definitely collecting the special coins. The pink coins seem to get harder to obtain as the game goes on. The purple coins afterwards are even harder, and the onyx coins are really challenging.
The levels also have different obstacle and coin layouts depending on the special coins you are going for.
This is helpful for me. I serve on a local board and this very much describes the type of discourse that occurs there. For reference, we run the meetings according to Bourinot's rules of order: https://www.amazon.com/Bourinots-Rules-Order-Assemblies-Shar...
By the same token, this is not terrible useful for me in terms of work meetings which are extremely informal in comparison. They are also intended to achieve a different goal.
I'd say that both types of meetings are appropriate for their goals, but I've also been surprised at just how effective the more formal meetings have been in achieving progress and consensus.
You could just grab user location and populate it in a db. Use a proximity search to see which users you see and see you.
You could also break things down by geofence, but that would work better for a city chat since there would need to be overlapping fences otherwise you could be next to someone and not see their messages.
There are other ways to do it, but if you are going to use Internet connectivity, that's the simplest I believe.
You can't take the Wii U tablet with you. It's not the core of the system. This allows Nintendo to combine their console and handheld divisions so that they can unify their focus and have a steady stream of software, even if third parties don't show up.
Yep. They specifically mentioned the difficulty of keeping up with software for both consoles (which both have different architecture) this generation and that they weren't going to make that mistake again next generation. And clearly they aren't.
It's brilliant. I have kids, and I could definitely see it coming places like the car where the kids are able to play together, or where I am able to play with the kids.
Growing up, my family would do a 24 hour drive to visit family in Pennsylvania, and my dad would get the Sega/N64 working in the van with an inverter for my sisters and me to play on this tiny 10in screen. I looked forward to the 24 hour drive because we'd play games like Mario Kart the whole time.
Not an easy drive to make with triplets, but we loved it. Didn't make a peep.
> you’ll pair with us on a real feature or bug
Are you paying people who are interviewing with you? Or are you getting them to do real work on your code for free?