vicapow

7 ms·

31.
by vicapow 10y ago
I'm sucker for self descriptive "boring" names like "create-react-app" Also, sweet project!!
32.
by vicapow 11y ago
Find the source code for this and other explanations at: https://github.com/vicapow/explained-visually/tree/master/cl...
33.
1M taxi pickups in NYC(vicapow.github.io)
1 points by vicapow 11y ago|0 comments
34.
by vicapow 11y ago
They've also never built a car before
35.
Allocating 56GB of memory in Chrome(gist.github.com)
2 points by vicapow 11y ago|1 comments
36.
by vicapow 11y ago
I've worked both at a large company (Facebook) that used the mono repo approach as well as a large company that uses the per project repo approach (Uber) and I have to say I'm personally a VERY big fan of the project based repo ap
37.
by vicapow 11y ago
Also, if you're in SF and are interested in learning more about d3.js, one of the primary libraries that we used to build EV, we'll be teaching a 1 day workshop May 2nd geared towards people comfortable with data but haven't
38.
by vicapow 11y ago
I think it's important to remember that, for at least EV, these explanations aren't intended to stand on their own. There's a lot of good resources online already for learning this stuff. The problem, as we see it, is one of
39.
A Visual Explanation of OLS Regression(setosa.io)
22 points by vicapow 11y ago|4 comments
40.
by vicapow 11y ago
Pull request? :)
41.
Where do betas come from? A Visual explanation of OLS Regression(setosa.io)
3 points by vicapow 11y ago|0 comments
42.
Generate your own map of all the streets in America(github.com)
1 points by vicapow 12y ago|0 comments
43.
by vicapow 12y ago
PCA minimizes the error along the PC axis. Here's a nice article that goes into more detail: http://www.r-bloggers.com/principal-component-analysis-pca-v...
44.
Principal component analysis explained visually(setosa.io)
187 points by vicapow 12y ago|22 comments
45.
by vicapow 12y ago
Yes
46.
by vicapow 12y ago
Yep! It was tricky to make it performant but I mostly just used chromes performance profiling tool to pinpoint optimization compiler bailouts. A big one was just casting to ints with |0 inside the kernel function.
47.
Eigenvectors and eigenvalues explained visually(setosa.io)
523 points by vicapow 12y ago|52 comments
48.
A Multi-Layer Perceptron in D3(bl.ocks.org)
3 points by vicapow 12y ago|0 comments
49.
by vicapow 12y ago
That is a great visualization but one something that bothered me about it was that you're constrained to watch it unravel at it's own playback speed.
50.
Show HN: Pi Explained Visually(setosa.io)
16 points by vicapow 12y ago|7 comments
51.
Explained Visually: Sine and cosine(setosa.io)
8 points by vicapow 12y ago|0 comments
52.
by vicapow 12y ago
That's a great idea.
53.
Show HN: Explained Visually(setosa.io)
353 points by vicapow 12y ago|45 comments
54.
Eigenfaces(en.wikipedia.org)
2 points by vicapow 12y ago|0 comments
55.
Gridlock vs. Bottlenecks: A visual explanation(setosa.io)
199 points by vicapow 12y ago|17 comments
56.
A Brief Introduction to WebGL(setosa.io)
1 points by vicapow 12y ago|0 comments
57.
Woodcut Data Visualization(setosa.io)
9 points by vicapow 12y ago|2 comments
58.
Show HN: Visualizing CSV formatting with “fingerprints”(setosa.io)
4 points by vicapow 12y ago|0 comments
59.
by vicapow 12y ago
To answer your first question, yes.
60.
by vicapow 12y ago
There was a bug in the playground earlier that I just fixed that allows you to share your Markov chains via the url hash. For example: http://setosa.io/markov/#%7B%22tm%22%3A%5B%5B0.9%2C0.1%2C0%2...

More ›