May 16, 2006
Lightroom Podcast #6: Cool splash screen names, unite!
“Seetharaman Narayanan” isn’t the only great-sounding name to grace the Photoshop splash screen over the years, and now Zalman Stern (who ported PS 2.5 to PowerPC, then left, started a company, and helped create Macromedia Contribute) has found his way back home. Both engineers joined their boss Dave Story plus George Jardine & Jeff Schewe to chat recently. George writes,
Assembling a cast of some of Adobe’s most interesting and talented engineers, this podcast attempts to crack the lid, if only just a little bit, and allow you a peek into some of the issues and thinking around our cross-platform development. We’ve included Zalman Stern, who has worked in the bowels of Photoshop code and just a few other world-class desktop applications… now working on Adobe Camera Raw; Seetharaman Narayanan, who has been crafting some of Adobe’s most ambitious cross-platform code for well over a decade; Dave Story, our VP of Engineering, who is training our focus on the big picture, to keep us firmly planted as leaders in the industry as we move into the 21st Century of application development; and finally, Jeff Schewe…. just to make sure the customer voice is always being heard!
As always the podcast is available via iTunes (search for “Lightroom”) and via this RSS feed. And maybe next time we’ll get Nkono Boyomo to sit in on a talk. :-)
Photoshop & bugs (the exoskeletal kind)
Now that we’ve squashed some bugs in Photoshop CS2*, we can look at an instance of the tools being used in conjunction with actual insects. Microscopy UK talks about photographing slide mounts using a combination of digital SLRs, microscope, and slide scanner. The Photoshop content here is limited, so I’m passing it along as much for the great high-res imagery as anything. [Tangentially related: Berkeley scientists have been inspired by insect vision to create new camera lens designs.]
* Speaking of Photoshop and bugs (the other, bad kind), there’s a Photoshop Top Issues RSS feed as well as a dedicated product support page. If you see something going haywire, please let us know (and send us your feature ideas, too). We probably won’t respond to each report directly, but we do read them all, and we use the info to guide product planning. Thanks.