I've had a busy couple of weeks of movies! Three movies in the past two weekends, and planning on seeing Spider-Man: Homecoming in the next couple days. But first, while trying to keep ourselves entertained in Des Moines, my girlfriend and I decided to kill a couple hours at the movies and checked out the newly-released war movie from Christopher Nolan: Dunkirk.

I'll admit that it took me a little while to figure out this movie's chronological structure. Director Christopher Nolan decided to edit the movie into a non-sequential order, in which individual scenes jump back and forth between points in the movie's timeline (sometimes to show the same event again, but this time from a different point of view). There's three main storylines running in parallel: a pair of soldiers trying to catch a boat off the beach, a pair of pilots hunting down German bombers, and a civilian yacht captain setting sail to help rescue the stranded British army. Early in the movie, the scenes with the soldiers take place at night, and the scenes on the planes and in the yacht take place during the day.

At first, I thought maybe this was some kind of time zone difference. Like maybe the scenes on the boat were taking place sufficiently east that the sun had already set; whereas, the planes were flying far enough west that the sun hadn't set yet. This wasn't the case. The movie was, in fact, shifting between an aerial pursuit taking place during one afternoon and the boat escapes that happened the night before (or several nights before). Maybe I missed something at the beginning of the movie that made this all more clear?

I didn't have any trouble following along with the non-linear, compressed time in Inception, but this movie threw me off a tiny bit simply because I wasn't expecting it. Once I realized how the movie actually worked, it was easy to follow along with each of the individual threads, and to start to see where and how they intersected. Not a deal-breaker in any way. By the end, everything comes together quite nicely.

The early movie cycles between the day of the evacuation and conflict from the night before.

Much like War for the Planet of the Apes (which is quite good), Dunkirk is a surprisingly slow and quiet movie...

It occurs to me that there is a sad dearth of pirate and sailing games in the market. The original Sid Meier's Pirates! is almost 30 years old! And the PC remake was released all the way back in 2004. Other than that, the only pirate or sailing-themed video games that I'm aware of are mobile games.

We saw a proliferation of cowboy and western-themed games after Rockstar's Red Dead Redemption (which, in hindsight, probably isn't as good as I gave it credit for). Perhaps Assassin's Creed IV: Black Flag could trigger a similar renaissance for pirate video games. And if those games are as good as Black Flag (or better), then that would be a real treat!

Hrm, this mission seems familiar...
[LEFT] A plantation raid in Assassin's Creed III; [RIGHT] another plantation raid in Black Flag.

The first hour or two after Black Flag's introductory pirate ship battle is a bit dull because it's mostly just the same old stuff that you've played in Assassin's Creed III: exploring the little town and playing a few "go here, do this" missions with an assassination or two.

Being stuck on land is usually pretty dull. In fact, some missions even seem copy-pasted from previous games. When I got to the mission in which I had to raid a sugar plantation, I couldn't help but think "Hey, didn't I already do this in III?" The only notable difference was that that the plantation raid was wrapped in a segment in which I had to pursue the plantation-owner's ship from a trade island to his plantation island.

Over the course of the game, you'll frequently be forced to step back onto land for story missions. some of the environments are a bit original, since there's some trekking through jungles and along beaches and scaling cliffs to break up the monotony of the usual parkour that the series is known for. Most of these jungle paths are closed and linear, so you won't be exploring open jungle with a machete.

The jungle and beach settings provide some visual variety beyond the city parkour, but are functionally similar.

There aren't any dramatic new gameplay functionalities associated with the more rural and wild settings beyond the tree-hopping that was featured in Assassin's Creed III. So while these missions provide some visual variety, they don't add much to the actual gameplay. The biggest change is that it takes a lot of your freedom of movement away, since you have to follow more of the pre-designed trails through the levels, rather than having the freedom to create your own route.

...

Black Flag sails triumphantly into the sunset as a stand-out game in an oversaturated franchise.

I never really hopped onto the Assassin's Creed bandwagon when the first one was released in 2007. The historical setting and gameplay concepts were intriguing and I wanted to play it, but I wasn't sure if I would like it enough to warrant an outright purchase. And since Ubisoft never bothered to release a playable demo on the PlayStation Network, I never played the game.

So I missed the first two games and their various spin-offs. But when I started seeing information about the third game, and its setting during the American Revolution, my curiosity piqued. The trailers made it look as though parts of the game were played during large-scale battles, and I thought that would be really cool to play. So when I found that a friend (Huh?Mr.Box!) was willing to let me borrow his copy, I decided to give it a chance.

And boy was I disappointed!

My core complaint with Assassin's Creed (and many other games like it) is that I don't like how dumbed down the controls are, and how little actual control the user has. The run button is also the "climb" button and sometimes the "jump" button (even though there is a dedicated "jump" button). I've always held that when a single button does everything, then it really does nothing. Assassin's Creed regularly feels like I am not playing the game; a procedural function created by the developers is playing the game.

Instead of the game just doing what the player tells it to do, it has to determine which of several pre-determined context-sensitive actions the developers decided to pre-program. You might want to try to sprint through a narrow alleyway between two close buildings to chase a courrier, but if you're just a few pixels off, you end up jumping up the side of the wall and climbing to the top of the building. And then it's a pain in the ass to get back down, and the courrier is now two blocks away.

Because I wasn't lined up perfectly, the free run forces me to climb up this building,
when all I really wanted to do was chase the courier through this alley way.

Maybe I want to jump off of a building onto a nearby tree branch in order to stay above a group of enemy Redcoats that I'm trying to stealth past. But for some reason, the game decides to make my character leap past the tree branch and right into the middle of the group of bad guys. Now my cover is blown, I'm stuck in combat, and maybe I've even failed a bonus objective or two.

These sorts of problems could be avoided if the "climb" and "jump" commands were their own buttons separate from the "run" button...

The company that I work for is switching over to using a new set of software for our products. Because of this, several members of our development staff were required to travel to our development studio in Manchester, United Kingdom in order to be trained on the new software.

Downtown Manchester, January 30, 2015.

As one of the senior developers in my office, I was asked to be one of the representatives of our studio for this training, and I had the good fortune of being able to go on my very first trip abroad. It wasn't technically my first visit to a foreign country, as I've visited Canada several times. Nor was it my first trip over an ocean, since I've visited Hawai'i. But the trip to Canada was many years ago; before a passport was even needed to cross the border, so it didn't feel like as big of a deal.

The training element was a bit underwhelming. The training schedule coincided with a major release deadline, so the engineer who was supposed to be providing the training and answering our questions had limited availability due to some last minute crises that he had to handle. So instead, we had a room full of people from different development studios in different countries all trying to bumble our way through the new software together.

But we did still learn some things, and even taught the lead engineer a thing or two!

A piece of advice to tech companies: don't schedule training sessions to begin a couple days before a major software release deadline - especially if you are flying developers in from halfway around the world to participate.

A British perspective on the World Wars

It wasn't all work though. I did try to do some touristy things.

I arrived in Manchester early Sunday morning after a red-eye flight from Philadelphia. After checking into the hotel to drop off my luggage, I took the cable car trolley back into the city and visited the Imperial War Museum (North). The main museum is in London (which I did not get to visit, other than a lay-over on the return trip), but there is a small branch of the museum in Manchester as well.

A tank displayed outside the Imperial War Museum North in Manchester, U.K.

One of the interesting things about this museum (compared to most history museums in the States) is the emphasis on the domestic impacts of war. Several exhibits were dedicated exclusively to the effects that the world wars had on the general populace [More]