Catching up

Whew. Survived the month-o-daily-rehearsals. (Work, nap, rehearsal, nap, work, repeat — didn't I used to have a blog?)

So I'll be playing catch-up for a bit (on both the sleeping and the blogging), probably with a bunch of sloppy multi-topic posts.

Question:

If, say, you were a Very Large national chain of newspapers and you had made the initial mistake, when switching all of your newspapers to a single database and a single server bank for their online editions, of forgetting that newspapers include photographs, which are Very Large files, and after crashing constantly due to the tens of thousands of Very Large photo files each night you had resorted to enforcing a Small-Low-Resolution-Compressed-Jpeg-Only rule, and then, somewhat more desperately, to an All-Articles-Will-Disappear-From-Your-Site-After-60-Days-Except-for-the-12-Percent-We'll-Allow-You-to-Designate-as-"Evergreen" rule (thus making the online editions of the newspapers in your chain just about useless for following ongoing news stories, like, for example, criminal trials), and yet your centralized database continued to crash and to suffer what you euphemistically refer to as "latency" on a regular basis because you had also failed to take into account the fact that every newspaper in a given time zone has very similar deadlines and so all of the papers in your chain will be processing their pages at the same time each night — if this were you — wouldn't you think about investing in more server space and more bandwidth?

Just wondering, hypothetically.

(Graphic courtesy of the pointlessly fun Official Seal Generator, via.)