{"id":12752,"date":"2008-05-12T07:56:56","date_gmt":"2008-05-12T07:56:56","guid":{"rendered":"http:\/\/blogs.adobe.com\/jnackdev\/2008\/05\/who-builds-photoshop-and-the-frequency-of-updates.html"},"modified":"2008-05-12T07:56:56","modified_gmt":"2008-05-12T07:56:56","slug":"who_builds_photoshop_and_the_frequency_of","status":"publish","type":"post","link":"https:\/\/jnack.com\/blog\/2008\/05\/12\/who_builds_photoshop_and_the_frequency_of\/","title":{"rendered":"Who builds Photoshop, and the frequency of updates"},"content":{"rendered":"

Via Daring Fireball I caught this little blurb<\/a> from Panic<\/a>‘s Cabel Sasser: <\/p>\n

 <\/p>\n

\n

A company like Adobe, which has hundreds of engineers working on
\nPhotoshop, releases ONE version every two or three years, and maybe a
\nsingle bug fix release in the interim. For the most part, we’re all
\ncool with that, myself included! \ud83d\ude42 <\/p>\n<\/blockquote>\n

 <\/p>\n

I’m glad to hear the last bit, especially as I love Panic’s Transmit and Unison software–models of simplicity and refinement.  The rest is kind of funny, though: in reality we have only a couple dozen engineers working on Photoshop.  (If you added in every person who tests Photoshop and Bridge, localizes them, builds the installers, manages the process, etc., you could get to more than a hundred people–but only with some effort.)  Relative to our feature set and code base, the team runs very lean. <\/p>\n

 <\/p>\n

As for the shipping schedule, it’s been 18-24 months between major releases for quite some time.  I don’t mean to take a casual comment in a forum overly seriously.  It’s just that I’ve been thinking about the Photoshop (and Suite) shipping schedule, wondering whether it’s too long, too short, or both.<\/p>\n

 <\/p>\n

On the one hand, the richer Suite apps get and the more of them there are, the more time people would like to settle into using them.  It’s generally easier to absorb upgrading a number of applications at once, then living with them for a while, than it was to handle continual unsynchronized updates (the pre-Suites world).  Through this lens, 18 months looks short. <\/p>\n

 <\/p>\n

On the other hand, we’re increasingly living in a world where "software is a relationship, not an artifact" (as I think Tim O’Reilly put it).  An application like Google Maps or Photoshop Express could be updated seamlessly, simultaneously for all users, every hour<\/em> if desired.  Through that lens, 18 months looks awfully long.<\/p>\n

 <\/p>\n

I’d like to get to a point where we can have it both ways.  I’d like the core team to be able to go off and spend several years retooling essential pieces of plumbing, making changes that won’t become visible for a few versions.  At the same time, I want to wake up in the morning and have Photoshop be smarter & more feature-rich than when I went to bed.  Some things should be updated every 5 years; others, every five minutes.<\/p>\n

 <\/p>\n

Obviously this isn’t the kind of change a team makes overnight, but we’re getting there.  Building on what we’ve got percolating, functionality like peer-to-peer help<\/a> will become possible.  More on that foundation soon. <\/p>\n

 <\/p>\n

PS–Re: people banging on Panic for more frequent updates to their inexpensive tools, I’m reminded of an observation attributed to Edward Tufte<\/a>:\t"The sense of entitlement increases as the price of the service or product decreases." <\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Via Daring Fireball I caught this little blurb from Panic‘s Cabel Sasser:   A company like Adobe, which has hundreds of engineers working on Photoshop, releases ONE version every two or three years, and maybe a single bug fix release in the interim. For the most part, we’re all cool with that, myself included! \ud83d\ude42 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/12752"}],"collection":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/comments?post=12752"}],"version-history":[{"count":0,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/12752\/revisions"}],"wp:attachment":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/media?parent=12752"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/categories?post=12752"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/tags?post=12752"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}