If you have an underwater camera, and you take it with you to your dive off Vancouver Island, please post a picture of the Saskatchewan reef. That's where I'm from. Just curious. Sounds like you've got quite a list of interesting hobbies, and a great job.

It's not on your list, but I'd love a good topic on how large games handle communication and interaction between multiple distinct game entities, without each game entity knowing about each others' internals. This is one of the most important areas in my own programming where my code suffers.

If the Player entity throws a Grenade entity, how does Player tell the World to spawn a Grenade without knowing about the World or the Grenade, and when the Grenade explodes, how does the Explosion or the Grenade tell the BadGuy to get hurt, without knowing about BadGuy's internals?

This is a rather simple example, and I can think of multiple ways to make it work (without hardcoding, and without knowledge of internals), but when you add more and more different types of events and different types of effects to different types of entities that are supposed to react in different ways, it gets harder to maintain. So what do the big boys do that a hobbyist/indie like me can learn from?

Another example, is how do you cleanly make Button X on the editor GUI spawn Entity Y in the engine, or modify level settings? Is there some kind of messaging system you'd use, or does each different editor widget have access to a pointer of the engine's public interface with which to directly call functions? Or is the engine globally accessible? Is the engine a monolith, or is the 'engine' a composition of different classes like "Level" and "Sound" and etc...? If the latter, do the editor widgets have access to each sub-system class?

How would falling x feet with the physics engine tell the entity that fell that it took damage, and how would that entity know what material it hit (metal, wood, etc...) and then tell the sound engine to play the proper sound effect for hitting that material, without having access to a dozen different pointers for each subsystem involved?

A good tutorial explaining this in-depth would benefit me greatly. There are plenty tutorials on "Here's how a GameState looks", but few on, "Here's how all your sub-systems interact with each other".

From your topic list, I'd personally be most interested in anything related to DirectX 11 - for the past couple years I've been using XNA, which is great, but I feel I've fallen behind a bit not having used the more modern API features. Also, new tech is fun to play with . I'd prefer C#, which I'm guessing would mean either using SlimDX or a custom wrapper, perhaps there are other wrappers I'm not aware of.

Not on your topic list, but I've also been meaning to delve into multithreading one of these days, and from I hear the newest .NET has added MT features. I've done very little with mutlithreading (never had to), so I'm not even really sure what topics would make for a good tutorial, but I'd at least be interested in where MT is most effective in games, and where the complexity outweighs the benefits.

Edit: SotL's suggestion also sounds interesting