31 karma · joined May 9, 2013
2. Construction will begin on a structure that will be taller than anything we have now and use an active support system.
3. A child will be born that lives to be 234.
4. Andrew Yang will be elected to some office, but it probably won't be president.
Could any of the physicists here verify whether it is the case that detecting the slit the particle passes through destroys the interference pattern. I had the impression that the path of the photons could be determined without destroying the pattern.
What's new?
> Unrecognized command
When I say "What's new" read the "In the news..." section of Wikipedia's main page.
> Acknowledged.
Idea: Git-story, a website that generates summary narratives from git commit histories and other github data.
Here's a brain-dump with some ideas for the specifics:
Use foreshadowing: "It all started with one person, X, spending months to gradually build what would one day become Y, a project forked by hundreds and starred by thousands."
When someone makes their first contribution to a project give them a brief introduction, like a shorter version of http://osrc.dfm.io/
Use sentiment analysis on commit messages to say things like "Frustrations mount as...", "the developers rejoice after..."
When people work on multiple concurrent branches use use phrases like: Meanwhile, X and Y toil away on the new Z feature.
Use the time between commits to chunk them into single sentences/paragraphs. Also, add comments if the project goes dormant, or if there is a spike in development.
Use keywords in commit messages like merge, revert, resolve to generate events in the story.
When bugs are resolved look for linked issues and use the age of the bug and number of comments to say thinks like "X finally fixed the controversial Y bug"
Here's a brain-dump with some ideas for the specifics:
Use foreshadowing: "It all started with one person, X, spending months to gradually build what would one day become Y, a project forked by hundreds and starred by thousands."
When someone makes their first contribution to a project give them a brief introduction, like a shorter version of http://osrc.dfm.io/
Use sentiment analysis on commit messages to say things like "Frustrations mount as...", "the developers rejoice after..."
When people work on multiple concurrent branches use use phrases like: Meanwhile, X and Y toil away on the new Z feature.
Use the time between commits to chunk them into single sentences/paragraphs. Also, add comments if the project goes dormant, or if there is a spike in development.
Use keywords in commit messages like merge, revert, resolve to generate events in the story.
When bugs are resolved look for linked issues and use the age of the bug and number of comments to say thinks like "A finally fixed the controversial B bug"
Here's a demo you can play around with: http://nathanathan.com/fuzzyTemplateMatcher/