Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Install count limit? (Score 1) 259

Technically, it's a combination of hardware IDs on your computer. ID of the install HD, ID of the CPU, ID of the motherboard chips, ID of the video card, ID of the NIC... The strictness of the check depends on the type of license, but replacing things one at a time is generally safe. If you have an OEM license, you generally have to replace things with very similar parts; e.g. if your MB dies, you need to replace it with the same style MB.

Comment Re:Why is this news? (Score 1) 259

If someone stole a manuscript from Disney and got away in a blue Ford with a license plate of XXX-123 and then pirated the manuscript, it certainly would be within the court's power to allow Disney to subpoena the owner of that particular Ford to ask who was in control of the car at the moment of the theft. It might have been the owner's son, or neighbor, or it might have been stolen. But it's a legitimate request to ask the question.

Comment Re:yes they should (Score 1) 254

Ding! We have a winner several zillion posts down the page and buried.

If a software/firmware update can disable the key wipe, then the FBI should be able to bypass it through direct hardware access and copying. The new phones do this all within a secured chip, making it much harder, but the 5c doesn't have that extra hardware protection.

Comment Re:Angel is a centerfold. (Score 1) 263

If the photograph was originally taken in a private location, then the person retains more rights to their likeness than they would if it were taken in a public place. In a public place, the person can only restrict sale of an image for commercial (i.e. advertising and advocacy) purposes. In a private place, however, a person must generally give consent to publish regardless of the purpose of publication. Again - in the US.

Comment Re:Jurisprudence (Score 1) 263

In the US, there is essentially no right to personality except in defamation suits. Copyright law would govern, and since there's a person's likeness involved and no formal consent form signed, a lawsuit *could* prevent the photographer from publishing or selling the photos, subject to normal copyright fines. Since some of the images have been found on the Internet, she could also go after him in a private civil lawsuit. But AFAIK there's nothing in US law that says that one person has a right to destroy another person's possessions just because their relationship has ended.

Comment Re:Maybe, maybe not (Score 2) 507

We effectively do without a scrum master. It can be done with an open and communicative team, so long as everyone recognizes the rules of the game and is willing to speak up to guide the process. Product owner buy-in is essential (and a scrum master IMHO an essential backup if the PM is fighting the system); they don't make the system work, but without good backlog management they can make the system break.

Our team succeeds at Agile more than anything else because our developers are respected by management. Our product owners and management have both wanted longer term planning and a more waterfall process because it's easier for them, but we have the ability to push back, and they have the respect to listen.

Comment Re:Yes (Score 2) 507

Management push-back is a tough one and understandable. They want to know where the company is going in a quarter, two quarters, next year. That means big plans, and it means estimating the size of things way in advance. That's something that Agile is specifically designed to avoid - unnecessary advance planning. I think this conflict exists (or should exist) even in the best Agile development shops. The alternative is the ultimate in management short-sightedness - no plan for the future, just get through the quarter. On our team the compromise is doing some one quarter rough-grooming and having our engineering team manager (who was a team member before being promoted) flesh out the more distant epic level grooming with our PM.

Comment Re:Good idea, hard to implement in the real world. (Score 2) 507

Like so many other things, it's very difficult to take an ideal theory and put it into practice in the real world. If your team really understands the ideas behind Agile and you have a good process in place to make it happen, you can have a great deal of success.

Unfortunately, like so many other things in life, most teams don't get it right and they end up failing to some degree or another.

Cannot be restated often enough.

I've worked in a shop that started doing "Agile" development after years of more waterfallish practices. This essentially meant that we started to get customer requests organized in an Agile toolset and then had a sprint planning meeting to negotiate the value of the various requests so that we could start work on them. Standups often took a half an hour for 6 people, including the PM, who unfortunately doubled as the scrum master. It wasn't terribly agile, and it didn't buy us much other than better tracking of issues.

And I work now at a medium sized company that does everything with some variation on Agile methodology (with some Kanban thrown in). We use Agile as the base framework for our development, but we adopt other practices that make sense, and we've agreed as developers (with the PM) on how it works best for us. Standup was 15 minutes this morning for a (largish) team of 9 developers - and that included some non-standup topics that snuck in. Retrospective for a two-week iteration is an hour to 1.5 hours. Planning is also about that long, including tasking - but we have one or more one hour grooming sessions during the iteration to keep our work backlog properly sized and ready to go. We code review each other's work, we communicate openly, and we know what's going on and how our work fits in with the overall product line because of that. It just works, and from a psychological standpoint it's good for morale to see the progress being made.

The difference is in committing to the actual goal of Agile - producing working code in manageable bits while minimizing unnecessary overhead. It's easy to go off the rails by misunderstanding Agile or half-assing it - you just have to get it right.

Slashdot Top Deals

Work continues in this area. -- DEC's SPR-Answering-Automaton