Please Take My Money Sony

20 July 2014

Man, I can’t believe I’m saying this but SONY, PLEASE TAKE MY MONEY. I was just trying to buy some video games in the PlayStation Store. When I was adding funds to my account, I kept getting an error when inputting my credit card details: “please enter a valid credit card number.” Double-checked the number, the expiration date, the security code, and name on the credit card and tried again. ERROR. Double-checked my billing address. ERROR. What the hell, Sony!?

After digging around online, I find I’m not the only person with credit card input issues on Sony’s website. After a ton of “me too, fuck Sony” posts, I found a helpful netizen who suggested making sure the billing address inputted on Sony’s website EXACTLY matches your credit card’s billing address. Now I can understand having to get a billing address correct when authorizing a transaction, but Sony is handling this somewhat poorly.

Read More

Shame on Yelp, See What I Did There?

14 July 2014

Yelp, we’ve got a problem. A serious problem. I really like what you’re doing, but you should know that commas cannot join two sentences. Yet every time someone sends a friend request, the placeholder sentence is a classic example of a comma splice.

That comma should be a period or a semicolon.

I already shed enough tears on behalf of the English language when I read some people’s reviews. Yelp, please do your part and stop this unnecessary propagation of terrible grammar. Your community will thank you.

P.S. Also, tell your engineers that they really should get around to replacing “[link to your page]” with the actual link to my page. iOS developers can check out the stringByReplacingOccurrencesOfString method and Android developers can use the replace method. Happy coding fellow developers!

Tales of Awesome

10 July 2014

Namco’s Tales series has been one of the most consistent JRPG franchises. My first taste was in 2004 with Tales of Symphonia, and that was a wonderful experience. I haven’t played every game in the series (there are a few duds it seems), but since Symphonia, I’ve thoroughly enjoyed Abyss, Vesperia, Graces, and most recently, Xillia. In a month, Tales of Xillia 2 will be released. I found Xillia to be a solid entry and the sequel is very, very well-regarded. RPG Fan has a great preview on the game; here are my main (and somewhat irreverent) takeaways.

  • “Ludger [the protagonist] can switch between three weapon types (dual blades, a hammer, and a gun) to fight his enemies effectively at any distance.” Finally! Some game designer realized that the best weapon isn’t a sword, or even two swords, but two swords, a sledgehammer, AND dual-wielded pistols. Genius!

Where will cosplayers keep the extra weapons?

  • “He can also transform into a demi-humanoid using the power of ‘Chromatus,’ dramatically augmenting his strength and ability repertoire.” Yes!!! Not only does he wield three different kinds of weapons, he can also GO SUPER SAIYAN!


  • “The Double Raid Linear Motion Battle System (DR-LMBS) returns as well.” The awesome battle system in the Tales series is a cornerstone of the series, but I never realized how ridiculous they name the system.

The Double Raid...ehh, fuck it. This is the battle system in action.

  • “Ludger and Elle are injured during a train hijacking early in the game, and a mysterious man takes advantage of their plight by paying their medical bills and putting Ludger into astronomical debt.” Sounds like Ludger and Elle don’t live on Elympios, but in the United States of America given the ruinous amount of medical debt they were able to incur. Running with that theory, it also sounds like the TSA should start securing our train systems.

20 million gald!? They must've spent a week and a half in the hospital!

Irreverence aside, August 19th can’t come soon enough because I’m super excited to dive in Tales of Xillia 2.

ChucK Meets Travis

06 July 2014

Ge, Spencer, and I sometimes talk about our dreams when we’re playing StarCraft. During the small windows of time when we’re not playing StarCraft, we’re all making some sort of headway towards our dreams. Today, one of those dreams has come to pass. ChucK is now set up for continuous integration on Travis. Every commit to ChucK triggers Travis to check that ChucK compiles and passes a suite of unit tests.

Who’s Travis? Travis is a free (for public repositories) hosted continuous integration service. With zero knowledge of Travis (but plenty of tears shed dabbling in release engineering at Smule), it only took an hour to get everything set up and running. You add one file to your repository (.travis.yml) and set up your scripts in there; it’s straightforward and just works. They say you get what you pay for, so I feel kind of bad because Travis is so good I feel like someone is getting robbed. How good is it? It builds and tests pull requests! Gone are the days where you would have to meticulously review the changes you were about to pull into your project. If Travis THINKS it’s okay, you KNOW it’s okay. But, perhaps double-checking isn’t a bad idea!

travis.yml file that supports both Linux and Mac

Travis has a multi-platform feature that’s in beta, and we’re already taking full advantage of that to run our tests on both Linux (Ubuntu 12.04) and Mac (Mavericks 10.9.2). When Travis adds more platform and OS configurations, we’ll run (not walk) to get those configurations set up. And while the current 150+ tests are a great start for unit testing, we’re looking to expand testing to make it more thorough and exhaustive. ChucK has a pretty awesome user community that is good at pushing ChucK to the limits (and occasionally breaking it), so we see a future filled with more tests, and consequently a greater and more stable (i.e. more stable than incredibly stable) ChucK.

Want more? Check out ChucK on Travis, check out ChucK on GitHub, read all about ChucK on its webpage, or join the ChucK community. Happy ChucKing you motherchuckers!

iOS Keyboard Addendum

02 July 2014

A few weeks ago, I wrote a post pointing out (i.e. complaining about) how iOS 7 broke the keyboard’s shift key. A coworker pointed out that the shift key really didn’t break in iOS 7 (released September 2013), but rather in iOS 7.1 (released March 2014). Android aside, I think iOS 6 still has the best shift key, but iOS 7.0’s shift key at least makes some sense. Here is a more complete picture depicting the shift key’s deterioration.

The descent into madness...

I can’t wait to see how much “better” they make the shift key in iOS 8!