244 karma · joined March 27, 2015
Here's an anecdote. My little brother has after school band practice 30 mins drive away. What does he do after school? He can't walk home, so he has to wait for me to pick him up. He can't go out to a movie with his friends because it would involved several parents taking the time out of work to send his friends there, and pick them up. He can't walk home or ride the subway because it's a freaking sprawl of highways. Bus stations are few and far between, and hugely unreliable. Instead all he knows is the highway that connects the school to home, and relies on my driving instead of his own two legs to get him home. I wonder why Americans are obese, hmm.
I watch animes that depict life in Tokyo. There is never a car involved. Kids just walk home after school, walking to a restaurant with their friends if they feel like it, hitting up a local 7-11. They can explore the local park, go to the movie theater, walk home with their friends if its on the same way.
I've stayed in Paris for 2 weeks and could literally walk everywhere. It's amazing how good it feels to see a cool gelato shop in yelp, proceed to take the subway with a bunch of strangers, walk a bit to the gelato shop, buy my gelato, and sit in a nearby coffee shop eating it. And want to check out some comic books? There's a comic book shop around a mile away, let's walk there.
People were not meant to live in suburbia. We are a social creature, we need to belong in a tribe, not a single home separate from the world.
1. Arrow functions are really handy:
["the", "red", "fox"].map(word => console.log(word))
is much cleaner than ["the", "red", "fox"].map(function(word) {
console.log(word)
})
2. Imports, while more ambiguous than `require`, look quite nice: import React, { Component } from 'react';
import Block from './Block';
vs var React = require('react');
var Block = require('./Block');
3. Exports are cleaner and streamlined export default myFunction()
vs module.exports = myFunction()
So while ES6 is more ambiguous than ES5 and has a higher learning curve, I think it's much cleaner and looks more like a proper programming language. ES5 feels like a homegrown hacky language in comparison.There's a lot of really well run subreddits like /r/AskScience and /r/AskHistorians where the people who get the final say are usually the ones who have the best credentials.
For websites like medium, it's less about the credentials but more about how flashy your title can be. Just look at the top articles - it's usually titled something along the lines of "You're all missing the point of X" or "Elon Musk is Dangerous" or "How the Tech World Trashes Women". And these articles tend to be written by social justice warriors or "motivational speakers" who have never actually done anything but coach.
Rather read a real book about people who have actually done great feats. Elon Musk's biography, and Pixar's Creativity Inc have had much better advice than the fluffy articles I see on medium.
Props to this guy for having the balls to speak honestly about Medium.
Think of the whole neural net as a function:
input * weight = output
At each iteration, we feed in the input to the neural net. Then the neural net compares what output it gets to the correct output.
For example, input1 is 5, and the correct output for input1 should have been 2. But the neural net got 3 as the output. So it then decreases the weights slightly so it would get 2.75 next time it has input of 5. Repeat thousands of times. That's the basic idea for machine learning and neural networks.
The algorithm it uses to figure out how much to decrease the weights is called "backpropagation" which uses gradient descent. To explain gradient descent, as as a roller coaster track. Imagine the roller coaster starts off on a random location on the track. Then gravity takes the roller coaster down the track until it ends up on a low point between two hills and stays there. This is the new location of the roller coaster. This new location is nice because it has the lowest energy the roller coaster could find, so it stays there. (We use derivatives to figure out the slope of a curve, which then gives us the direction where the curve goes downhill).
In neural networks, the roller coaster curve is the "cost function", which basically calculates the amount of difference between the neural net's output and the actual correct output it should have got. The initial weight is the roller coaster's initial position. The new weight is the roller coaster's final position, at the bottom of the cost function curve. This new position thus gives us the lowest cost.
Note that there may be even lower valleys, but when we roll the rollercoaster it stops at its nearest low valley. This is why we randomize the weights at the beginning - to put the roller coaster near possibly even lower valleys.
I'm not sure about 3rd party js text editors, but I'm guessing it could be a pain to work with state and props in that context.
Well this exact thing isn't THAT big of a deal but it's a slippery slope. If Apple agreed to this then what else can the government ask them to do under the banner of "public safety"? And if Apple were to give the government an electronic way to brute force the touch codes, it would break the trust of every iPhone owner.
Would have been better if he took a more objective look at Uber's redesign instead of taking the time to bash the CEO or the designers.
http://rackt.org/redux/docs/recipes/ServerRendering.html
On server request, render the first snapshot of a React app into pure HTML and send it out, and then that HTML snapshot uses a script tag to get the actual JS file of the react app.
I feel like Meteor fulfills two niches in the Node world
* Experimental Javascript full stack framework
* Providing a foundation for full stack apps instead of having the developer do it.
I disagree with this point... I think Node is very versatile and solid. I dont see anything niche about it. It does very few basic jobs well, 1) providing a good package system (NPM) and 2) giving us javascript on the backend. I feel like people think that just because Node is associated with Javascript that its inherently bad.
Windows + Mouse with hotkeys is still the most comfortable set up for most people including me. I don't need an optimized experience.
I've tried Metro, I've tried i3, I've tried bspwm, I use Vim with split screen, and I still prefer the concept of draggable windows at the end of the day. It feels more free to be able to drag windows and take ownership of the layout than having a computer dictate what my layout should be.
At the end of the day, I feel like I'm more and more preferring simple UI's rather than these multitouch optimized experiences
Tried it out on a random equation from the Fourier transform wiki page: