A list of annotation tools

[afomi]

http://roamresear.ch
http://hypothes.is
https://genius.com

[theo-armour]

@afomi

Your issue is a nice example of a problem worth solving.

You posit three links.

What should I do with these three links?

Well, I suppose I should click on them. I click the first one. Nothing happens for a very long time. Then a video appears. And a dude explains he has god-like intentions. And then he clicks on text things for a while and I leave. The second link is to the web site with a very cool name that I went to a few days ago when you sent the link. The third link goes to a gonzo music site.

Now imagine that there are a thousand links like this.

Then I would like to be able stand on the shoulders of a giant who can say 'innovation is saying no to a 1,000 things' and who can deliver an authoritative, curated list of what I should be looking at now - while at the same time being able to present evidence (textual/visual) as to why the others are not relevant to my current task.

---

Perhaps pearltrees in the answer

http://www.pearltrees.com/k/en/javascript

---

Then again my ministry is slightly different:

Can I create a demo in 500-800 lines that any script-kiddie can hack for fun and at the same time could inspire a full-stack dev-ops build a useful corporate info-thingy?

---

I do like thinking about these issues in this way. After all, I am a designer not a programmer. then again, every time I spend the half hour or so on an issue like like this (yes, I think and type that slowly) is half an hour not coding the next release.

What is really fun is when I am working on some half-assed really broken thing, and somebody is along for the ride and they say "Well, could you make both of them jump" or "what about adding windows" or some really in-the-moment I-am-with-you who-cares-exactly-where-we-are-going way.

---

The dream: the designer and the wise fool

Or what's going on in Spider gbXML Viewer with me and Michal and Evgeny - which is about somebody who can code while talking to peeps with deep domain-intense needs.

---

Rats, time for bed

[afomi]

What should I do with these three links?

You've clicked on them, perused them and garnered any value you may have found in them. That is sufficient, to me.

Why generate more work based on this? Is it really a painful problem? Or just enjoyable to muse about?

---

I would like... a... curated list of what I should be looking at now - while at the same time being able to present evidence (textual/visual) as to why the others are not relevant to my current task.

This is what I distill as your use case, and while I can nod at this idea, I cannot conceive of a feasible way to make it happen.

Can I create a demo in 500-800 lines that any script-kiddie can hack for fun and at the same time could inspire a full-stack dev-ops build a useful corporate info-thingy?

I understand your intention, but again, don't have any way of delivering on this. Code is code (abstractions on abstractions). 500-800 lines is arbitrary. Thousands of lines of code can be distilled and leveraged with a function.

What is Acceptance Criteria for a notion like this?

What is really fun is when I am working on some half-assed really broken thing

Yes, collaborating in real-time with another person is fun. Solving user needs is a great reward. Solving real needs is something that drives me as well.