twittering on 2011-04-05

  • UpdatePDX tonight! At P.I.E. http://www.meetup.com/updatepdx/events/16416694/?a=md1.2p_evn&rv=md1.2p #
  • I'm experiencing an eventsplosion. Not sure how I'm going to sleep for the next two weeks. #
  • "You can't tune away the horror of 300-line SQL." -@lusciouspear #updatepdx #
  • learned that we needed to hire CS people #updatepdx #nosql #
  • "Once you stop answering email in 24-hours, they start sending more email." -@sarahnovotny #fail #updatepdx #
  • "you need to check that you have backups BEFORE you do your maintenance." -@sarahnovotny #backups #updatepdx #
  • "You don't have valid backups. You have valid *restores*." -@sarahnovotny #updatepdx #
  • "Twitter is really a series of caches." -@al3x #updatepdx #
  • "We had no idea how much we had to learn." -@al3x #updatepdx #
  • many <3s for computer science education today #updatepdx #
  • shout out for Pivotal Labs /cc @sarahmei 🙂 #updatepdx #
  • "both readthrough and writethrough caching was happening at the same time." #fail #updatepdx #
  • "But the issue was not technology, but responsibility in the organization." #fail #updatepdx #
  • "Only use NOSQL if you reach a certain point of despair." -@timanglade #updatepdx #
  • "If you ask for NOSQL by name, you probably don't need it. " -@timanglade #updatepdx #nosql #fail #
  • "Usually they should just hire a MySQL consultant." -@timanglade #updatepdx #
  • "Trust no one. that goes double if they talk about CAP." -@timanglade #updatepdx #
  • I see a niche market for database and devops-specific comedy. #
  • "Get a fresh set of eyes on the problem." (story of replacing data stored in Riak w/Postgres) #updatepdx re/collab while scaling @al3x #
  • talking about learning culture, passion for tech and how to hire when jobs are no longer silo'd between dev, ops, dba #updatepdx #