so the thing i really like about this book (Terence Tao’s Analysis) so far is that this man would give you the most grueling exercises first but after those he’ll throw in a few exercises that go like “here’s how all of the shit you learned connects together” and it’s pure bliss
like, after a dozen of boring mechanical ones, i can’t wait to get to this one.
it’s like a satisfying season finale
loooool this is literally a reducer
• • •
Missing some Tweet in this thread? You can try to
force a refresh
a hundred things i learned working on the react team @threadapalooza
1. every few years your audience changes. new users don’t appreciate problems of the past bc never seen them. old users burn out or lose excitement. new users have different reference frame, learned in diff ways, you might be their first programming env. plan accordingly.
2. when you fix a problem you better really really understand the problem you’re fixing. take a few steps back and reintegrate new knowledge into the design. should it change the design? it’s like fighting a hydra: solving a problem in the wrong spot spawns 10 new problems.
recommend me an ANIME. disclaimer: almost know nothing about the genre.
netflix decided to show me jojo adventures and i watched a few eps. liked: camera freezes while character is thinking, weird shit happening. dislike: too teenagery, women are npcs.
what to watch instead
also watched before:
death note — i know it’s kind of a classic entry point but i watched as a teen and i think it’s also rather teen-oriented
mushishi — this is a bit TOO contemplative plus i’d like some character development as the series progresses
ok a few more things. ideally fights/violence wouldn’t be the focal point, it bores me. something like serial experiments lain too depressing, ideally want something more alive. about relationships maybe?? but not infantilizing. actually interesting character drama?
in my personal projects i use eslint-config-react-app and prettier and it’s been great. recommend 100%
i mean... if it works for you, great. i want people to know other options exist because for many people who are newer this is literally the only thing they were exposed to
proof by contrapositive feels like a cheat code. so instead of proving A => B i can prove !B => !A and it’s the same thing??? my mind refuses to believe it
i think it’s unappealing intuitively for the same reason implication is confusing in general: the idea that you can imply anything from a false statement is nonsensical to our intuition
here’s how i explain it to myself.
we have !B => !A. why is it equivalent to A => B?
1) suppose A is true. !B => !A means you could not have reached A from !B. so B must have been true.
2) suppose A is false. then A => B is true vacuously (false premise).
There’s a lot of interest in Server Components, and our alpha demos have been getting some closer attention. There are two demos I’ve seen so far (one is ours), so I wrote about known issues with both. I hope this will be helpful for future comparisons.
it’s hard to disagree with anything here. this doesn’t mean it’ll die soon though: hype cycles aren’t rational, and a worse architecture that pulls people in for one reason or another can definitely take off for a while
i think it’s also true that there’s something irresistible about coding against a “universe of wallets”. payments were always an afterthought, something you “tack on”, and for somebody coding them directly i imagine it’s hard to go back to wanting to use intermediaries.
the architecture comparison does look like a nightmare from the first glance. i can’t deny though that it’s also how people compared react apps to php/rails. but client side (when done well) improved ux (faster updates) and dx (fast feedback loop); this does neither.