3 ms·
> The concept of viewing activities as DAG is going to be huge and ubiquitous, I think. What do you mean "is going to be"? Activities as a DAG is how it's alre
by Jtsummers 7y ago
> The concept of viewing activities as DAG is going to be huge and ubiquitous, I think.
What do you mean "is going to be"? Activities as a DAG is how it's already done. This is how Work Breakdown Structures are generally constructed. Tools like MS Project can display them as Gantt charts or network diagrams or as an outline (where you can set the dependencies used to create the Gantt and network charts).
- andrey_utkin 7y agoVery few human tools utilizing this concept are common to any degree. Github Issues doesn't have issue dependencies at all. Salesforce "Action Plan" view is a plain list, no deps at all, as far as I have seen. Todoist doesn't do dependencies. Bugzilla does dependency graph, wow: https://bugs.gentoo.org/showdependencytree.cgi?id=706426&hide_resolved=1 https://bugs.gentoo.org/showdependencytree.cgi?id=706426&hid... I guess JIRA supports deps, but I don't think it's the tool which people here would want to use to be able to decompose their big undertakings, especially personal ones. TaskWarrior supports deps, but it's not a mainstream tool and deps were fairly hard to use in it AFAIR.
- Jtsummers 7y agoIt may not be common in the tools people here use, but it's common in the tools used by major engineering organizations. My point isn't that it's a bad idea, it's that it's not a novel idea. PERT is another way of graphically representing activity. If you aren't concerned with the time, it's your DAG. [0] https://en.wikipedia.org/wiki/Program_evaluation_and_review_technique https://en.wikipedia.org/wiki/Program_evaluation_and_review_...