791 karma · joined July 15, 2019
A grander vision of gathering feedback as part of a normal process seems desirable, but I don't know that the incentives for stakeholders are present to enable that.
Of the four, scirate.com seems the best option (unless you're focused on machine learning -- then arxiv-sanity is the winner).
I agree that comments on arxiv papers are "unlikely to take off" in either a commercial money-making sense or a "grow as large and popular as HackerNews" sense.
[0] https://graphthinking.blogspot.com/2021/12/comments-on-arxiv...
This author focuses bio-sciences; I've been collecting a list of similar efforts in Physics [0]. Those who can't do teach, and those who can't teach decorate data with semantic features.
Write down every quantitative expression in Mathematical Physics. Assign a unique numerical ID to each expression. Identify the relations between each of the expressions to create a graph. Does that graph feature any patterns? Is there a path from any expression to every other expression?
Pivots away from the current approach are very difficult. Even minor deviations like https://arxiv.org/ take decades to gain "normal" status in the science community.
More frequently everything is a one-off, with failure recurring randomly until a working (though not reproducible) approach is found. I'm not sure how to spin this evolutionary approach positively, as it can result in fragile outcomes.
There is software infrastructure that enables reproducibility (virtual machines, and more recently containerization), but this concept rarely makes it to written documentation.
[0] https://github.com/LappleApple/awesome-leading-and-managing
[1] https://github.com/kdeldycke/awesome-engineering-team-manage...
[2] https://github.com/ankitjaininfo/awesome-managers
[3] https://graphthinking.blogspot.com/2021/04/reading-list-for-...
While there are many spiritual interpretations, there is also practical advice online for recovering. Walking outside (experiencing nature) is commonly suggested.
Accidentally stumbling into this disorienting experience could be (and in the case of this author, was) traumatic.
[0] https://en.wikipedia.org/wiki/History_of_KFC#Heublein_and_st...
[1] https://en.wikipedia.org/wiki/Colonel_Sanders#1930%E2%80%931...
[0] https://graphthinking.blogspot.com/2021/04/reading-list-for-...
[1] https://graphthinking.blogspot.com/2021/07/questions-for-non...
As for what HN could be mined for, a big topic is software languages. There are ways to subdivide that: by language, by optimization aspect (e.g., comparative performance). Geographic topics like cost of living and quality of life. Remote work pros and cons.
Another way of identifying topics worth mining would be identify posts where @dang provides a link to previous posts and those previous posts have a sufficient number of comments.
[0] https://graphthinking.blogspot.com/2021/06/periodic-rotation...
I learned that every conversation is a negotiation. Seeking to understand the position the other party is starting from, and seeing where everyone wants to go, reframed how I view interactions.
[0] https://en.wikipedia.org/wiki/You_Can_Negotiate_Anything
For example, asking the same person the same question may yield different answers based on their mood or other environmental or situational factors. Who's asking the question can also matter, as does the specific phrasing of the question.
Hypernode graphs seem to be very applicable to knowledge graphs, though they have different names depending on the discipline -- nested state machines, statecharts [1], UML hierarchically nested states [2].
I recently participated in a lecture series on Applied Category Theory [3] that touched on the underlying math of composition. The course focused on optimization of design choices in complex decision spaces.
[1] https://statecharts.github.io/
[2] https://en.wikipedia.org/wiki/UML_state_machine#Hierarchical...
[3] https://applied-compositional-thinking.engineering/lectures/
I think that's why Stack Overflow websites focused on shallow conditions flourish -- the deep dives are usually specific to a given situation.
The documentation integration is nice.
Great work!