Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: I used to think yes, but not so much (Score 4, Insightful) 288

by nick_danger (#41437405) Attached to: Ask Slashdot: Should Developers Install Their Software Themselves?
There was a time in my career that I'd have said yes, the developers make the most sense as they are the only ones that really understand the process. But now I know that's exactly the problem with having developers doing the installs. For a production system you need to have a well defined process that produces repeatable results. The only way to ensure that is to have a separation of duties, whether it's an administrator that's being intelligent hands for a human-readable script, or is simply kicking off a developer provided computer readable script.

Comment: Re:Have a great trip! (Score 1) 1095

by nick_danger (#30219714) Attached to: Geek Travel To London From the US — Tips?
I spent a month there a year ago; the trains are the best. Anywhere my wife and I wanted to go, there were two trains an hour. We never worried about transportation on the far end; you can nearly always find a cab even in the sticks. TfL's London Transport Museum is off the beaten path, and has a fair amount of cool stuff.

Comment: You're doomed. (Score 1) 291

by nick_danger (#14793099) Attached to: How Do You Decide Which Framework to Use?
Frameworks are doomed, and here's why:

You're trying to build a strategy to migrate from .NET 1.1 to .NET 2.0. In a couple of years time, MS will have introduced .NET 2.1, or .NET 3.0 or whatever, and you'll be back to square one, migrating your application into a new framework. You have to ask yourself, What business am I in? Are you in the business of delivering solutions to customer problems, or are you in the business of applying another vendor's solution to the problem they created?

All of the popular frameworks are immature. They'll be completely different in a couple of years, and if you're lucky -- I mean really lucky -- they'll incorporate some sort of backward compatibility to let you leverage your existing code base. I wouldn't count on that though.

Of course, all that being said, if your principle work product is billable hours, then by all means go with the latest and greatest framework. The customer gets some great whiz-bang that they can pay another chunk of big money to upgrade in a few years. I mean, have you tried to hire an entry-level ASP programmer lately?

FORTUNE'S FUN FACTS TO KNOW AND TELL: A firefly is not a fly, but a beetle.