Mark D'Arensbourg

they're gonna starve in there

the real target customer for the apple vision pro is somebody who's been putting off refactoring a 3k loc javascript function

if you want to drive a developer to the brink of madness, give them a bunch of unit tests with bugged assertions

to add to this, people have an inclination to misuse it to produce implementations they assume to be correct/exhaustive. but one area where it's already infinitely valuable is education. it may not be a full fledged engineer yet, but it's quite the tutor.

ChatGPT is extremely impressive, yes, and has a tendency to slip insidious oversights past you even as you continually steer it. I would pay real money for a version which iterated responses based on runner output from a unit test prompt until it detected a pass.

there are a lot of things you can do to reduce stress. exercise, meditation, etc. but the biggest one by far is to write failing tests before modifying legacy code.

request waterfalls and time to first byte are almost certain to dwarf every other perf concern in every web app. start there

"react is slow" is the new "x programming paradigm is slow." for most domains, the biggest perf gains come from scheduling the biggest chunks of work for when they're needed. a really good model will yield great performance on even mediocre tooling and runtimes.

Just got my ticket for #nextjsconf by @vercel, claim yours! Let's make the Web. Faster. nextjs.org/conf/tickets/o…

is anybody working on using the es record literals+deep property syntax proposal for serialization and schema definition?

you gotta be careful where you get your random values from. you can't just pick a generator… arbitrarily twitter.com/matthew_d_gree…

in type-fest this is called LiteralUnion. mystery solved

apparently a "weighted union" is actually already a thing for finding nodes in a tree structure, which this is not. better names welcome (bonus if it's already a name for precisely this from type/set theory)

weighted unions in typescript!

i'm not against writing specs with ascii charts but i think they should be in a parseable format like mermaid charts

this is bad actually. that diagram is gibberish to a screen reader (theoretically some assistive tech could be configured to parse and describe it?) and even with a description it should live in a spec not a class definition

"i barely feel this formal methods gummy dude" one hour later:

@rauchg don't mind if i do! nextjs.org/conf/tickets/o…

Join me at Next.js Conf – I think this one will be big 😊 nextjs.org/conf/tickets/o…

no way i'm getting any sleep for the next 36 hours or so probably