|
Top-level
 @saddestrobots Ten years ago, I worked for a company with "Reimbursement" in the name of the company. We had a DB table column where it was spelled: reimbrusment It's in the name of the god damn company, and someone couldn't spell it right. And since it was in a vital (and quite large) table, we couldn't just fix it without massive database downtime. I bet it still hasn't been fixed. 7 comments
 @Azuaron @saddestrobots Iβve analyzed applications with millions of users that had the application name (which is also the company name) misspelled internally. Clearly, this was a load bearing typo.  @WPalant   @iacore @saddestrobots While I was there, we switched from Rackspace to a cloud hosting service*. This is how I learned that the database only worked if the whole thing, all 80 GB of it, was in memory. The new cloud host didn't have a database with that much RAM, so we shipped them our server from Rackspace and they connected it to their cloud. * that cost twice as much as AWS and had half as many features; the engineers suspected the CTO had some kind of personal kickback arrangement. @Azuaron @saddestrobots r.i.p. no corporate structure to stop this? using number of features on AWS as a comparison... no. just no. they literally promote anyone who make a feature in some obscure market space that's barely usable. |
Gregory's Server
@Azuaron
@saddestrobots
Easier to change the name of the company to match, surely.