What do you think is the secret for Workflowy's success? Is it the novelty? The geekiness? The design? Stuff like that fascinates me, because I don't really need it. How am I to discover what people like if I wouldn't use it in the first place?
Workflowy is to TODO as git is to svn
61–70 of 81 posts
Re: Workflowy is to TODO as git is to svn
#62Re: Workflowy is to TODO as git is to svn
#63Re: Workflowy is to TODO as git is to svn
#64Are people really okay with both giving lots of details about what they are working on to an untrusted third party and committing to a tool that may uncontrollably change or disappear depending on what the maintainer decides to do with it? I suppose I could use it for hobby projects. For work stuff, untrusted third parties having a free view at my workflow is just straight out, so there goes one big use for the syste…
There's a simple solution to this problem -> realising that it is surprisingly easy for anyone with the interest to track you around town as you do your stuff and to plant bugs in your office. The info they get that way is much more useful and detailed than anything you ever write down on a TODO list. If they're just reading your stuff as a passing curiosity because they accidentally can, then they are not a threat a…
This is completely false. There might be a handful of people with the time and willingness to do this who also find themselves in a suitable location. There are probably hundreds of thousands who could do it on the internet.
Re: Workflowy is to TODO as git is to svn
#65I keep trying new tools when they come out, but find myself always snapping back to Notational Velocity. Workflowy reminds me of OmniOutliner, they share a very similar, hierarchical approach. Sadly they also share similar problems; a GUI that's too slow for my fingers and too complex for my little brain. The GUI-complexity stems from the enforced hierarchy. Indenting stuff seems nice at first, and makes it look tidy…
Re: Workflowy is to TODO as git is to svn
#66I keep trying new tools when they come out, but find myself always snapping back to Notational Velocity. Workflowy reminds me of OmniOutliner, they share a very similar, hierarchical approach. Sadly they also share similar problems; a GUI that's too slow for my fingers and too complex for my little brain. The GUI-complexity stems from the enforced hierarchy. Indenting stuff seems nice at first, and makes it look tidy…
When I switched to Linux, I found that Zim http://zim-wiki.org/ came close enough to Notational Velocity for my purposes. The key feature both share is giving me the ability to very quickly jump to a note by typing its name in. (With Zim you do this by typing cntrl-j.) I'm reluctant to try any note manager that doesn't have that feature.
Re: Workflowy is to TODO as git is to svn
#67Earlier quoted context omitted.
It's a top-down approach. The question is, can your ideas be subdivided into small(er) tasks?
What if my ideas are smaller parts of different things (i.e. a cycle, which can not be in a tree)? Maybe I'm thinking about it the wrong way.
Re: Workflowy is to TODO as git is to svn
#68Re: Workflowy is to TODO as git is to svn
#69Re: Workflowy is to TODO as git is to svn
#70I would love to run something like this on my personal webserver. Is there any free software solution that provides such a web solution? (I've played with various wikis for a while but it never was never 'addictive' enough.)
Very simple (single HTML file, web server not required), local, lightweight, can sync with Dropbox easily.
For teams, we're heavily using the Open Source version of Etherpad. Not a wiki, but a great collaborative text editor.