Dungeons as Software Development

Your tank is the product team. They decide what the group is going to do, the pace of work, and generally what needs to be done.

Your DPS are the design team. They follow product's lead in terms of what should be done, but are pretty much on their own to decide the specifics of implementation.

Your healer is the development team. All they want to do is help things progress, but they're too busy trying to make up for the issues caused by product and design's decisions.

(And yes, I am both a healer and a software developer, I may be a bit biased :p)

The pace of a dungeon is not up to the tank, it's up to the healer.

Quote:

---

Originally Posted by Intaki

The pace of a dungeon is not up to the tank, it's up to the healer.

---

That's a new one lol! I suppose the healer has the power to stall production but they're not so much a pace-setter as a pace-breaker.

Same could be said about DPS... slower DPS, slows production.

But tanks should be the pace-setters & should do so reasonably, in view of their teammates' capabilities.

Quote:

---

Originally Posted by Intaki

The pace of a dungeon is not up to the tank, it's up to the healer.

---

It should be up to everyone.

Well, completion of a fight is generally when the boss dies, which is the damage dealers' job. DPS complete the core objective while tank and healer make it possible for them to do so. I think that would make DPS the development end of such an analogy. Maybe healer=product, tank=design, DPS=development.