Hacker News Reader

Comment by l0stb0y | Hacker News Reader

I wasn't a fan if CC at first but it's turned into an incredibly good deal for me at $30 per month. A little downtime from time to time can't be avoided. People just love to complain.

View on HN

I'm sure your words are comforting to those graphic designers who missed print deadlines due to this outage.

Quite frankly, if a persons workflow doesn't include a potential for downtime then they only have themselves to blame. This whole 'down to the wire' and 'stop the press' mentality is a combination of drama-grade fallacy and unprofessional project management skills.

This hand-wave over designer's inability to build enough slack to deal with Adobe's failure into every project is a combination of unsubtle trolling and egregious sociopathy.

It's called 'planning for the unexpected' and encompasses a wide range of scenarios, only one of which can be blamed on Adobe.

Well, to play devil's advocate, 'planning for the unexpected' should also cover 'a client calls at the last minute with a rush job', shouldn't it? In that case, how is an Adobe outage the consultant's fault?

Yes, a professional should be prepared for unexpected customer requests with tight deadlines. And the response to such a request is to just get the work done. That, of course, involves being prepared for any service outages that might interfere with such work.

How many times did Adobe failed? Total minutes outage per month would be nice to know.

How many times did they have work-stopping outages before CC?

It wasn't a little down time. Also they handled it poorly.

I had four staff without access to key systems for our designs. I had to call customers and explain why deadlines were going to be missed.

Made me look unprofessional, especially since there was NO announcement by Adobe. I had to search Twitter to find out what was going on.

You don't have CS5 or 6 running on backup computers in case of CC or general internet outages? Did you explain that to your customers?

No because we work primary in Flash. Flash is not backwards compatible, and we have custom applications developed for flash.

CC is much larger than just Photoshop.

Also internet outages don't usually affect CC.

Yea, unplugging the Internet is a known workaround in fact.

I'm glad you have your toy for just 30$ per month but some people do real work with CC.

Hi, thanks for your reply. I make my living with a combination of professional photography, videography, a smidgen of web design and some graphic design. So yeah, no real work there.

>>A little downtime from time to time can't be avoided. People just love to complain.

If you feel this way then image-editing isn't your core task in your job.

Imagine if the github.com maintainers had your attitude. "Meh, some downtime here 'n there. Whuchagonnado?" A github outage for _OVER 24 HOURS_ would freakin' wreck me and my coworkers. The image-editing department for a high-fashion magazine in New York or Paris with those already near-impossible deadlines losing 24hrs is going to make some execs somewhere very angry.

No one other than Adobe can provide a Creative Cloud that you can type cc add remote creativebucket.org and keep working. You can, however, type git add remote bitbucket and should be working to several remotes.

And yet another fashion magazine expert. So many! I'd like to point out that your image is solely based on low-grade chick-flicks.

I would think git's distributed nature would make this a lesser issue. You would just have to set up another remote target and push/pull from that (say on AWS or some other provider).

Sure. But not having access to the tickets database might cripple a team pretty badly.

One reason I'm still toying with the idea of trying fossil[1] "for real" and/or find/make a tool that distributes issues within mercurial/git like http://www.bugseverywhere.org/

Note-to-self: looks like hattawiki might be a nice companion on the path to "distributed everything":

http://hatta-wiki.org/Install

[1] https://www.fossil-scm.org/

For a distributed wiki try gollum. It's the wiki engine behind the github wikis and it's basically a wiki where the database is a git repo. I love it for family use. I can put up a nice web interface for everyone else to edit and yet I use git push/pull and my normal text editor. Works great.

Turn it around into a special no-Photoshop issue of the magazine, and disrupt the high-fashion industry!

Reply on news.ycombinator.com