Skip to main content

View Diary: [New]: Daily Kos is Broken (285 comments)

Comment Preferences

  •  The tech team *does* work for a living (11+ / 0-)

    And they are generally pretty quick to respond to problems. And they do work for a living, so don't act like they're just lazy asses and don't want to fix it.

    IT people are always under-appreciated because everyone wants them to fix their problem NOW, without considering how many other problems need to be fixed and, compared to the others, yours is pretty small.

    There's no reason to be a dick to the tech team. We actually have a really great set-up at this site, and the tech team can't be expected to snap their fingers and fix an issue immediately just because it annoys some of us.

    So chill out.

    P.S. I am not a crackpot.

    by BoiseBlue on Mon Oct 15, 2012 at 06:35:10 PM PDT

    [ Parent ]

    •  As a former IT type, I can see both sides... (8+ / 0-)

      I agree with what you say about 'fix it now', but I also gotta say changes should be beta'd on a test site before going live, and prior code versions should be kept so that if a problem slips through such a beta and arrives on a production site, you can just revert to the old code until you've got a fixed version of the 'new' code that can be moved off the test servers and out to the production site.

      I know how that goes, I had to do just such reversions several times for clients.  When your 'upgrades' break things, you can't just say 'oh well, it'll stay broken until I figure out what's wrong with the 'upgrade''.  You revert to pre-upgrade, and figure it out without inconveniencing end-users.

    •  I don't think that was what the commenter (0+ / 0-)

      intended. It was poorly worded, but I think the reference was to being able to be on one device all the time. Living/working in the same place, etc. I don't think it was meant to imply that the tech crew doesn't work hard.

Subscribe or Donate to support Daily Kos.

Click here for the mobile view of the site