acdlite Profile Banner
Andrew Clark Profile
Andrew Clark

@acdlite

Followers
73K
Following
15K
Statuses
22K

@reactjs core team, @nextjs, @vercel. Hi!

Manhattan, NY
Joined February 2009
Don't wanna be here? Send us removal request.
@acdlite
Andrew Clark
1 year
One cool thing about working on a web framework is that the tools you use to build a feature might eventually adopt the feature itself. 5.5 years later, in this case.
Tweet media one
5
7
314
@acdlite
Andrew Clark
20 days
If you work in a codebase for more than a few months I don’t see how this can be true. I read old commits/PRs constantly.
@growing_daniel
Daniel
21 days
I love always writing my detailed little commit messages and then never once in my entire fucking life reading a commit message
5
0
46
@acdlite
Andrew Clark
22 days
@Big3Tennis @FDSportsbook Seems about right, but I’d buy Djokovic
0
0
1
@acdlite
Andrew Clark
24 days
@dieworkwear Now judge the guy’s fit
2
0
13
@acdlite
Andrew Clark
24 days
@jordwalke Sorry, I’m choosing to be vague so that everyone may interpret in a way they agree with
0
0
5
@acdlite
Andrew Clark
24 days
See also: socks
1
0
0
@acdlite
Andrew Clark
26 days
@jordwalke Agree this one is trickier. And yet, reading the wrong answers reminded me of the bad analysis you’d sometimes hear during experiment review at Facebook 😆
0
0
0
@acdlite
Andrew Clark
26 days
@subluminary @jordwalke Original text says “most of the less competitive students”, not most students overall
0
0
1
@acdlite
Andrew Clark
26 days
@jordwalke Oh I don’t mean to suggest I could take the exam cold and ace it 😆 the replies to the OP though suggest it’s roughly representative of the overall difficulty level, though (ChatGPT agreed)
1
0
1
@acdlite
Andrew Clark
26 days
@Big3Tennis Slicing down the tee as a lefty has gotta feel so good
1
0
1
@acdlite
Andrew Clark
26 days
@jordwalke Yeah if you approach it as a logic puzzle it really doesn’t seem hard. Which would seem to advantage a STEM-oriented person. Makes sense, I just didn’t realize that’s what the LSAT was designed to test.
1
0
1
@acdlite
Andrew Clark
28 days
@paraplas5 23.3%! With the caveat that Nishioka isn’t the best returner. Still!
0
0
0
@acdlite
Andrew Clark
28 days
@Big3Tennis Indeed, brutal for night owls with no self control (me)
0
0
1
@acdlite
Andrew Clark
1 month
@sebsilbermann @mattpocockuk @github Yeah because I turned it off yesterday 😆
0
0
7
@acdlite
Andrew Clark
1 month
I really liked Challengers, including this sequence, but it does require you to turn off the part of your brain that knows how tennis works
@channelserve
vivi 🖍️
1 month
this sequence takes me out so bad because why are they just hitting the ball back and forth to each other, i can’t see any sensible point construction that’s actually aiming at winning a point 🗿
0
0
2
@acdlite
Andrew Clark
1 month
@mattpocockuk @github Oh lol is it the default or does this mean someone on my team turned it on?
3
0
3
@acdlite
Andrew Clark
1 month
@jstarmx @github There are other strategies for addressing that risk besides "rebase/retest every PR whenever there's an upstream change", like running your tests on the upstream branch post-merge (which presumably everyone is already doing), using a merge queue, etc.
2
0
1
@acdlite
Andrew Clark
1 month
How about removing that warning and adding this one instead?
Tweet media one
0
0
46