Please create an account to participate in the Slashdot moderation system


Forgot your password?

Comment: incorrect - 40 astronauts required to date. (Score 5, Informative) 160

by ferret4 (#47016577) Attached to: The Shrinking Giant Red Spot of Jupiter
5 crews of 7 astronauts have gone into space on repair missions, including the first mission to repair Hubble's faulty lenses that would have rendered it useless. Add to that the 5 astronauts that took Hubble into space in the first place and you have a total of 40 people in space. Some of those 40 may possibly be the same across 6 missions, I'll let you research that yourself.

Comment: Re:Agile means you always hit final release date (Score 1) 597

by ferret4 (#43916239) Attached to: Why Your Users Hate Agile

I pitched my comment towards differences for the users, as that's what this Slashdot article is querying. The difference to actual development is, as you've quite rightly pointed out, zero - which is at it should be. Your developers have created a launchable product, it's only up to the business to decide if it's an appropriate time to launch the product or not - it's none of the developers concern.

When talking about "the non-agile alternative" I'm afraid I should have specified "the classic waterfall method".

Comment: Agile means you always hit final release date (Score 1) 597

by ferret4 (#43910275) Attached to: Why Your Users Hate Agile

The way I've used agile is not to have multiple iterative launches of a product, but to have multiple iterative points where you *have* a launchable product. The advantage of Agile isn't constantly churning out crumb-like updates to freaked-out users, it's being able to say on any given week "we could launch with X feature set now if we had to, and have Y feature set still to build" rather than the non-agile alternative which is "it doesn't work but we are 30% towards completing it".

This enables you to be able to set a firm launch date and be able to meet it with a working product. You can either chose to launch iterative updates afterwards, or just stick with what you launched and move onto a different project - whatever the business decides.

In reference to the summary: if there is no process, you are doing Agile wrong. If your developers are overwriting each others work, you are using SVN wrong. Neither of these are inherent problems with Agile, you're just being incompetent - and there is no methodology to overcome incompetence.

Comment: Flickr have announced 1 Terabyte of storage, free (Score 1) 162

by ferret4 (#43777829) Attached to: Yahoo Pinkie-Swears It Won't Ruin Tumblr
Giving 1 Terabyte (not gigabyte, terabyte) of storage to users (not paid users, all users) is NOT the action of a dying product. The Yahoo! bashing is getting pretty tiresome around here - according to the Wall Street Journal they've made $5 billion profit annually for the last few years - I fail to see how that is unsuccessful. In regards to Tumblr, Flickr is an excellent example of Yahoo! buying a brand and service and not ruining it in the proces.

"Your attitude determines your attitude." -- Zig Ziglar, self-improvement doofus