fokinsean
Joined 12 years ago
Joined 12 years ago
https://www.covid-datascience.com/post/do-pfizer-vaccines-ki...
Could you elaborate more?
> I never figured out how to classify nollie/fakie board and lip slides front or back
Yep this one still trips me up to and is great argument over some beers. Especially when you introduce flip tricks into them as well :p
I have a private discord and github for the project I can add you too. I eventually plan to open up the discord for anyone once we get a little further in the rebuild.
Wish there was a good way to DM on HN, I can send you a discord invite. Or if you happen to be on slap let me know.
Also I'll go ahead and plug the site I'm helping rebuild.
One of my other favorites:
On circle rails there is "no such thing" as fs overcrook, just fs nosegrind, and there is no such thing as bs nosegrind, but there is bs overcrook.
At least that's how magazines seem to classify it.
For example:
- nollie fs 180 and fakie fs 180 (fs half cab) are two different directions: nollie fs 180 is in front of you and fakie fs 180 is behind you going blind
- nollie 5-0 and fakie 5-0 (fakie switch nosegrind) lean differently on the grind: nollie 5-0 you pop off your nose and land on your back truck, fakie 5-0 you pop off your tail and land on your front truck
- nollie noseslide and fakie noseslide are different motions to get into the slide: nollie nose you pop off nose and land on the nose in the ledge, fakie nose you pop off tail and land on the nose but you do a sort of half cab
The key distinction in the argument is that in fakie, your tail is always considered your "tail". Therefore you treat any derived tricks as being "backwards". In the 5-0 and noseslide examples, you're still popping off the front of your board, but you classify it as nose or tail based on if it's nollie or fakie.
There are caveats though such as "fakie crook" where if you kept the rule it should be "fakie suski", which no one says.
There's a million arbitrary and nonsensical rules in skateboarding which is part of the reason to love it, especially for something that "has no rules".
And remember, never carry your board by your truck :)
https://kentcdodds.com/blog/usememo-and-usecallback
TLDR;
> Specifically the cost for useCallback and useMemo are that you make the code more complex for your co-workers, you could make a mistake in the dependencies array, and you're potentially making performance worse by invoking the built-in hooks and preventing dependencies and memoized values from being garbage collected. Those are all fine costs to incur if you get the performance benefits necessary, but it's best to measure first.