Useful Reading for Game Developers
Established game studios' staff as well as would-be game developers should check out The 7 Commandments All Video Games Should Obey over at Cracked.com. Commandments #5 and #6 sum up everything that is wrong with Assassin's Creed, but it's #7 - be playable with real friends in the same room as you - that I wish more games paid attention to. Even among the few games that do offer split screen, too many manage to get it so horribly wrong it's worth asking why they bothered in the first place. Just look at the various G.R.A.W. and Rainbow 6: Vegas titles - Ubisoft devs should sit down and play Halo 3 and Gears of War end to end with a buddy to see where the bar is at.
Uncle Bob’s upcoming book: Clean Code
Awesome - finally something to bash people on the head with when they write ugly code! 
(Ok, the "code smells" from Refactoring are a good start too but this seems more pedagogic in nature.) There are a lot of technical books out there, but few focus on good general practices. One of my favourites is Effective Java by Joshua Bloch, but it's focus is slightly more architectural and less on day-to-day coding. I love Bob Martin's writing so I didn't have to look long at the table of contents to order my copy as soon as it's available!
Office Open XML Standardised; Does It Matter Anymore?
Many might wish that this was a bad April Fools joke, but Microsoft has at last managed to push OOXML through as an ISO standard. The New York Times reports that an overwhelming majority of voters supported the notion with only 10 countries' standards bodies voting against (Brazil, Canada, China, Cuba, Ecuador, India, Iran, New Zealand, South Africa, and Venezuela).
The main problem with OOXML is that it is a hugely complicated specification (the document is nearly 10 times bigger than ODF and there are doubts as to whether it is complete); aside from the fact that it is riddled with bugs, legacy workarounds and potential patent traps for competitors, not even Microsoft currently ships a working implementation of the standard. So it is hard to imagine anyone writing new OOXML-compatible software just for the fun of it.
As Joel Spolsky explains, the reason why Microsoft's binary Office formats are so complicated to start with is that they are just binary serialized forms of Microsoft's proprietary OLE object model. The OOXML standard describes how to store the same structures but this time serialized in XML instead. Sometimes a fresh start is the best course of action.
The benefit of open interfaces in computer systems is much the same the same as in real life. Take the common electrical plug for instance - it allows for a multitude of devices to be plugged into a multitude of sockets to draw power. You can be fairly certain that any one device will operate correctly plugged into any one of the vast numbers of sockets out there. And this is where the plug analogy becomes relevant - your valuable data becomes locked in, and only available via Microsoft's proprietary and commercial sockets.
From a developer's point of view, I think the standard is largely irrelevant. There are few incentives to support the format besides the creation of conversion tools. Simplicity has always been key in ICT and there is no reason to select OOXML in places where previously a custom format might have been used.
The danger of having OOXML accepted as an ISO standard is that Microsoft can and will use it as an argument in favor of selling Office into governments and companies concerned about the portability of their data. Of course in practice, with Microsoft being the only supplier of OOXML tools, the data is no better off than it was stored in their undocumented binary formats. Undoubtedly, Microsoft will also try to use its new-found standards compliance as a defense against monopoly accusations.
Adobe Photoshop Lightroom 2.0 Beta Now Publically Available
It was only a matter of time - Adobe Systems has countered Apple's release of Aperture 2 by offering a beta version of its upcoming competitor for anyone to download. The original beta testing program leading up to the release of Photoshop Lightroom 1.0 was a huge success by gathering useful user feedback while introducing digital photographers to a new breed of image processing tools.
Although it carries the Photoshop branding, Lightroom is mostly clean-room a implementation borrowing some concepts from Adobe Bridge and reusing the Camera Raw engine. The original beta release of Photoshop Lightroom (called just Lightroom at the time) also trailed the first release of Apple's Aperture. Both have completely redefined the "digital darkroom" by offering a streamlined solution for digital photographers, although arguably Lightroom has had a bigger impact by reaching both Mac and Windows users.
Notably, the Lightroom 2.0 beta adds two much-requested capabilities: multi-monitor support and localized adjustments. The former has always been present in Apple's offering, while the latter was recently introduced in Aperture 2.1. Apple still has an important advantage in that it offers 3rd party plugin SDK which allows independent developers to offer their image processing add-ons. For virtually all photographers, this would mean that the need to occasionally switch to a more powerful program such as Adobe's Photoshop CS3 for a small subset of retouching features is now eliminated.
So have a look at the release notes, and get downloading! More impressions to follow soon.