Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This is why at work [plusthree.com] each developer gets a pretty powerful laptop and does all their work on it. At a conference but need to do a little work? Want to travel for a week visiting relatives but not use any vacation time? Need to go home a little early because the baby sitter didn't show up?

    None of these are problems if each dev has their own portable environment. Sure we're at the office 81% of the time working normally, but that extra flexibility for that other 19% is great.
  • I tend to prefer shared over local as long as the shared resources are in the same office and have reasonable rights. Servers located in different continents or where I have not got enough rights to do my job are a pain.
    If your test db servers are down as often as they are up, 20 is a normal load on your server or you often don't have network connectivity in your office then you probably have bigger problems than the relative merits of centralized verses distributed development.

  • I've been at my current $work for a year and a half.

    Luckily for me, I've never seen our SVN repo go down, I've never seen our Oracle dev instance go down, and all our dev and test servers are on a VMWare cluster, which I've never seen go down.

    Frankly, I've had more problems with my desktop machine due to virus checking, remote admin and network drives than I've had problem with server gear.

    Maybe we're just lucky... :/