gyozaking

Singularity 6 | Senior Gameplay Engineer | Los Angeles, CA | Full-Time | Onsite | https://www.singularity6.com

We’re a game development team dedicated to the idea that online games can deliver deeper, more meaningful experiences.

With our first project, we’re exploring new styles of game design and tackling difficult technical problems to create a game that’s beautiful and intricate, delivering far more than superficial entertainment or basic wish fulfillment, an experience that becomes a meaningful part of your life. Our vision is to create a compelling virtual universe filled with rich and diverse gameplay experiences and social interactions that will keep you playing for years, evolving along with you and the rest of the community... We want our players to feel valued as well as a true sense of belonging.

Sounds ambitious? We think so, too. If you’re interested in the challenge of building a new genre, in making rewarding interactive & community experiences filled with amazing art and world class technology to support this living world, join us on the journey.

Apply directly at https://singularity6.workable.com/j/6370D8664C

Probably because most projects will use uirouter: https://github.com/angular-ui/ui-router

Slow installations, not slow uptake. Installations started in in mid-Nov. Based on their schedule (http://googlefiberblog.blogspot.com/2013/02/kansas-reminders...), it seems Google can rollout 1-2 "fiberhoods" a week. With 180 fiberhoods, it is going to take a while to get an impressive installation number.

Good example of relentlessly resourceful: http://www.paulgraham.com/relres.html

Not at all - YVR is the airport.

This glorifies the bag tag a little too much. The bag tag is part of a solution that is only as good as the information supporting it. Airlines are still running archaic backend systems (e.g. systems from the 70's in some cases) & error-prone human processes that simply do not reliably collect and deliver proper baggage information to baggage systems. You would be shocked by the percentage of bags that cannot be processed because the baggage messages are simply not recieved (nevermind format errors, missing fields, etc.).

RFID solutions only improve read rate and tracking while the bag is on mechanical equipment, but do not address issues with manual handling at various other steps (e.g. moving bags from delivery piers to carts, and then to planes). And RFID does not address the information quality problem. That's partly why RFID has only been implemented in a handful of airports (e.g. HK & one of Milan's terminals) despite being feasible for a decade.

To truly reduce baggage losses, airlines & airports need to work together and implement multiple solutions that track and improve performance end to end - for all automated and manual processes.

Disclosure: I worked on designing & enhancing baggage systems for a common-use airport that is consistently ranked in the top 10 by awards (e.g. http://www.worldairportawards.com/).

One unmentioned deterrent to using NFC on Android (for cases where security is not important) is requiring the user to unlock the phone first. In ICS or later, NFC is no longer enabled at the lockscreen, presumably to address security concerns with the payments use cases.

In some cases, it can be just as easy to unlock your phone and execute an action manually rather than through NFC.

I also wonder if Square's "magical" Starbucks payments system will be future - using environmental cues in the background instead of requiring manual swipes of a phone to a terminal.

Show the offers to users for free, but obfuscate the hotel names until the users pay a fee.