ovid,
@ovid@fosstodon.org avatar

Still love the struggling client who explained they picked their database because they misread the documentation.

Our company still goes into clients who are considering and it turns out it's because they don't know how to use a . Denormalized, no foreign keys, 20 indexes on a table that needs one, and so on. So they decide to trade a known set of problems for an unknown set of problems. It often ends poorly.

PS: we can fix this for you.

wordshaper,
@wordshaper@weatherishappening.network avatar

@ovid Well, y'know, they really traded one set of known problems for another set of known problems. They might not have know about them but the rest of us probably did.

(Sometimes the problem you're trading for is either NIH-syndrome or "we're more clever than those people who did that", not that I'm thinking of anything in particular in-house or anything...)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • DreamBathrooms
  • mdbf
  • ngwrru68w68
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • osvaldo12
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • InstantRegret
  • tacticalgear
  • provamag3
  • ethstaker
  • cisconetworking
  • modclub
  • tester
  • GTA5RPClips
  • cubers
  • everett
  • normalnudes
  • megavids
  • Leos
  • anitta
  • JUstTest
  • lostlight
  • All magazines