Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment Re: Amazing (Score 1) 504

Also, have you seen the stats on spousal abuse and violent abuse between men and women? It's not the majority of the population but it's a very large percentage. I absolutely do believe it is normalised behaviour, and I don't see why you would have a problem with Microsoft doing their small part to counter the problem as it develops. Is it so important to you to be able to be rude and obnoxious to your feminine-voiced phone that you'd deny the opportunity in mitigating violent and anti-social behaviour in others? Are you really that selfish? Or do you need your phone as a verbal punching bag against all those women who upset you so much?

Comment Re: Amazing (Score 1) 504

I'd say yours is the bugaboo with sexuality. It's the abuse part of sexual abuse that's the issue, and it starts with verbal abuse. And yeah, sounds like you do have anger problems, and you should find a way to cope with them nonviolently. What if you're, say, on a weeks camping and have no access to an avatar punchbag? You'll be screaming at everyone to "hold me back, I can't be held responsible!"

Comment Amazing (Score 0) 504

I'm shocked to see everyone so far who has posted has completely missed the point. This isn't about infringing your imaginary rights to be rude and abusive to inanimate objects. It's about discouraging abusive behaviour towards a simulacrum female in the hope that it will in turn discourage similar behaviour towards real women. This AI has no fear of being physically harmed, so can put abusive assholes in their place and teach them how to be decent people - unlike the real women in these peoples lives, who out of fear of being hurt or from being psychology "put in their place" by their abusive men may never speak out, reinforcing such appallingly behaviour. This AI has no such fears or ability to be browbeaten. Slashdot community, you greatly disappoint me.

Comment Re: Ovens. Get rid of them. (Score 1) 222

When you've finished tearing your meat to shreds, why not add it to a chemical bath to leech out the nutrients while turning the remainder into shit? Smart people can just suck the juice of life up a straw from around the turds, while the morons out there can pretend they're enjoying their 'meals'.

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

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

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

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.

Slashdot Top Deals

Take care of the luxuries and the necessities will take care of themselves. -- Lazarus Long

Working...