Hacker News Reader

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.

View on HN

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?

Reply on news.ycombinator.com