Jonny

VP of R&D @PrettyDamnTweet | Building checkout & shipping tech that powers 100M+ eCommerce orders/year | Scaling infrastructure, AI, and engineering teams

[Jonny @JonathanGes]

Smart and true

[Timothy Young @timyoung]

https://t.co/8jdNjdauJ6

[Jonny @JonathanGes]

@simonlast Are you running these agents locally? Cloud? Where do you manage this long running agent?

[Jonny @JonathanGes]

@felixrieseberg This is great! Would love to see a Teams View similar to the one you get with terminal and tmux as a next step.

[Jonny @JonathanGes]

https://t.co/JZZp1yEI6J

[Avi Moskowitz @MoskowitzAvi]

Shopper types "SAVE20." Doesn't work.

Tries again. Caps lock. No caps. Opens Google.

Finds a dead Reddit thread. Closes the tab. Gone.

46% of shoppers bail when a code fails.

We just shipped the fix.

[Jonny @JonathanGes]

I read "Relentless" by Tim Grover a while back, and it's stuck with me. Grover trained Michael Jordan and Kobe. His framework breaks performers into three tiers: Coolers, Closers, and Cleaners.

Most good engineers are Closers. They deliver. They're reliable. They want the ball in crunch time. That's not a knock, Closers are valuable.

But Cleaners are wired differently. They don't wait for a ticket to fix something. They're almost personally offended that a problem exists. They'll dig into a system at 11 PM, not because anyone asked, but because something felt off and they couldn't let it go.

In engineering terms: a Closer fixes the bug. A Cleaner fixes it, then asks why it was even possible and quietly rebuilds the foundation so it can't happen again.

A Closer ships the feature. A Cleaner ships it, keeps an eye on how it's actually used, and is quietly planning the next iteration before anyone asks.

Grover's honest that you can't really coach someone into this mindset. It's either there or it isn't. But leaders still have a role to play: learn to spot it, hire for it, and build a culture that lets these people do their thing.

Worth a read.

[Jonny @JonathanGes]

I read "Relentless" by Tim Grover a while back, and it's stuck with me. Grover trained Michael Jordan and Kobe. His framework breaks performers into three tiers: Coolers, Closers, and Cleaners.

Most good engineers are Closers. They deliver. They're reliable. They want the ball in crunch time. That's not a knock, Closers are valuable.

But Cleaners are wired differently. They don't wait for a ticket to fix something. They're almost personally offended that a problem exists. They'll dig into a system at 11 PM, not because anyone asked, but because something felt off and they couldn't let it go.

In engineering terms: a Closer fixes the bug. A Cleaner fixes it, then asks why it was even possible and quietly rebuilds the foundation so it can't happen again.

A Closer ships the feature. A Cleaner ships it, keeps an eye on how it's actually used, and is quietly planning the next iteration before anyone asks.

Grover's honest that you can't really coach someone into this mindset. It's either there or it isn't. But leaders still have a role to play: learn to spot it, hire for it, and build a culture that lets these people do their thing.

Worth a read.

[Jonny @JonathanGes]

Our merchants see one thing: it works.

Checkouts complete. Orders ship. Revenue flows.

6,000 checkouts per minute on Black Friday. That doesn't happen by accident. It happens because of a team that obsesses over outcomes as if their own business depends on it.

Grateful to work alongside people who care this much.

[Jonny @JonathanGes]

Our merchants see one thing: it works.

Checkouts complete. Orders ship. Revenue flows.

6,000 checkouts per minute on Black Friday. That doesn't happen by accident. It happens because of a team that obsesses over outcomes as if their own business depends on it.

Grateful to work alongside people who care this much.

[Jonny @JonathanGes]

@windsurf_ai I love windsurf. The only thing that would make it better would be the capability to reference a PR or diff between current branch to main.

[Jonny @JonathanGes]

Practically every offensive play today ends with a 3 pointer. This sucks. Make the 3 point line farther. Bring back the 90s so NBA can be fun again #NYKvsUTA

[Jonny @JonathanGes]

@AnthropicAI the example in the docs for the beta count_tokens request is missing the route of the endpoint (has /messages instead of /messages/count_tokens): https://t.co/dyL2dnfirK

[Jonny @JonathanGes]

@jasonfried How and who decides on how much appetite there is?

[Jonny @JonathanGes]

@OriKatz3 לקלוד יש חלון קונטקסט גדול בהרבה והוא טוב יותר בכתיבה יצירתית לדעתי. שווה לעשות ניסוי

[Jonny @JonathanGes]

Interesting!

[The Laboratory of Inflammatory CNS Diseases @AVDlaboratory]

Check out our latest review paper about the interplay of inflammation and remyelination. Discover how OPCs' dual roles in immune modulation and remyelination could revolutionize MS therapy. @MolNeuro

@ZveikO @RechtmanAriel @AdiVaknindem

https://t.co/BBbwpg6MP5

[Jonny @JonathanGes]

8/8 While ZKP technology is promising, it does face some technical challenges. As these are addressed, ZKP could revolutionize how we handle sensitive data in the digital age, enhancing privacy across various applications 🚀

[Jonny @JonathanGes]

1/7 It's #crypto Thursday 🔐 Let's dive into Zero-Knowledge Proofs (ZKP), a game-changing concept in cryptography and blockchain. A thread.

[Jonny @JonathanGes]

7/8 In practice, ZKP is already being used in some blockchain projects to enable private, verifiable transactions. This means you can make transactions without anyone seeing their content.