Blake Embrey

Building. Previously @Opendoor, @MuleSoft, TS Node, Typings, Express.js TC.

[Tristan @Tristan0x]

Had a Jane Street interview in 2014

End of round 5. Interviewer says "round 6 will find you."

Three weeks. Nothing.

I'm in line at the Trader Joe's on 14th. Line snakes past the frozen aisle, the way it always does. I'm holding a bag of orange chicken and a four-pack of cold brew concentrate.

Guy in front of me is in a Patagonia vest over a quarter-zip. Not turning around. Inching his cart forward every 30 seconds.

Picks a box of something out of his own cart. Holds it up over his shoulder without turning around.

"Ant on a corner of this box. Walks to the opposite corner along edges. How many shortest paths."

"Six."

"Now in 4 dimensions."

I think. Tesseract. One edge per dimension, any order.

"4!. Twenty-four."

"Confidence."

"0.85."

"Correct on both counts."

Offer Monday. $69k base (which I'm told is a 'cultural fit discount'). No bonus. No equity. No relocation. They will, however, allow me to name one (1) colocated server in their NY4 cage.

I take my time. This is the only thing I'm being given.

I submit "Steve." Already a Steve.
I submit "Steve2." Discouraged naming pattern.
I submit "Steven." Confusing with Steve.
I submit "Big Steve." Big Steve exists in NY5.
I submit "my Steve."
Approved.

Two weeks into onboarding, IT pings the eng channel: "my Steve is down." Three engineers respond at once asking which Steve. The thread spirals. Someone clarifies: "it's named 'my Steve.'" Someone replies "yes but whose." A VP joins the thread: "is this a possessive or a proper noun." Nobody knows. A meeting is called.

The meeting is titled "re: my Steve." Nine engineers attend. The first ten minutes are spent establishing whether the meeting title refers to the server or to a Steve belonging to the meeting organizer. The meeting organizer is named Devesh. Devesh does not know a Steve.

Offer rescinded Friday. Reason listed in the email as: "Introduced ambiguity into production naming taxonomy. Unrecoverable."

I'm no longer allowed in the building. I am also, somehow, no longer allowed in the Trader Joe's on 14th. The doors don't open for me. I have tested this six times. The orange chicken is still in there. Three bags deep on the shelf, frozen, waiting. I think about it every day.

[Silicon Mania @siliconmania]

WAIT!!! ALL THIS WAS JUST LAST WEEK IN TECH???

[Ben Stiller @BenStiller]

I can do a flip. Not a big deal.

#INSTACARTPARTNERS

[DiscussingFilm @DiscussingFilm]

Apple has landed the rights to turn ‘MISTBORN’ into a film franchise & ‘THE STORMLIGHT ARCHIVE’ into a TV series.

Brandon Sanderson will write, produce and consult on all projects.

(Source: https://t.co/Ka6RvxmT3S)

[Blake Embrey @blakeembrey]

@RobinhoodApp All in

[Blake Embrey @blakeembrey]

@frederic_ooo @wiedymi @saltyAom Basically this, it saves people time. Plus performance and security. You're unlikely to spend as much time optimizing this tiny thing and patching CVEs than the maintainer (currently me).

[Blake Embrey @blakeembrey]

@branmcconnell @saltyAom I try my best to maintain backward compatibility and this was an unfortunate oversight, I should have thought about the possibility passing a field in `options` that conflicts. This specifically was caused by code for maintaining backward compatibility 😓

[Blake Embrey @blakeembrey]

@branmcconnell @saltyAom Fixed: https://t.co/k9bZ9dfMY0

Releasing after merge. This was an unfortunate error caused by `value` being passed in options, and I didn't handle it as expected.

[Blake Embrey @blakeembrey]

@dmythro @saltyAom Can you share the breaking change or report an issue?

[Teortaxes▶️ (DeepSeek 推特🐋铁粉 2023 – ∞) @teortaxesTex]

Hangzhou is insane. Just look at what these kids do. They casually made a fleet of trash-catching trash cans for a 3 minute video. 232 likes as of now. And all their stuff is like this.

[Blake Embrey @blakeembrey]

@daylightco It’s halfway between right now but yes, I haven’t quite adjusted to full amber. This light reminds me of the kindle.

[Blake Embrey @blakeembrey]

Got the new @daylightco for comfortable reading

[Blake Embrey @blakeembrey]

@wesleytodd @kettanaito FWIW, agree it’ll be years before we should ship ESM for the express ecosystem. I’d let the node changes play out first and see how it works and is received in stable versions.

[Blake Embrey @blakeembrey]

@wesleytodd @kettanaito Yes and no, adoption is definitely worse than CJS, but better than I expected. I’m optimistic the node changes will help solve it. It’s a bad situation as an author, because no one is happy with you 😭

But it is easier on my psychology once I commit to a path.

[Blake Embrey @blakeembrey]

@wesleytodd @kettanaito For things outside Express, yes. I don’t author any browser libs, although often they can be used there.

[Blake Embrey @blakeembrey]

@kettanaito The issue for me with dual publishing, aside from maintainer overhead, has been that APIs differ in environments, e.g. __filename. Sure, it’s solvable with other packages, but then you have the package dep/size stans, and I don’t totally disagree with them.

[Blake Embrey @blakeembrey]

@kettanaito > Since you cannot include a CJS dependency in the ESM bundle

If you’re bundling, what bundlers don’t support CJS? Seems dramatic to call this a disaster when publishing ESM means more orgs that can’t rewrite are stuck. I’m someone who is shipping ESM only for my own packages.

[Blake Embrey @blakeembrey]

Instant buy. Love seeing new reading tech. https://t.co/TQxzKPgi0e