David Byttow (@davidbyttow) on X

David Byttow

7,774 posts

David Byttow

@davidbyttow

11x engineer, artist 🏴‍☠️ prev: google, square, secret, snap, bridgewater, lyft, oscar, and former game dev.

NYC

Born February 12

Joined January 2009

Replies Articles Media

Pinned
David Byttow
@davidbyttow
Feb 23, 2019
My mom controlled our AOL account when I was about 13 and would come into my room to sign me in. So, I created an entirely fake AOL login flow in Visual Basic and had her sign me in once to capture the password. Old school phishing.
This post is from a protected account.
David Byttow
@davidbyttow
May 16
Humans rapidly re-baseline reality, especially when a change is gradual, abstract, non-immediately-threatening, or socially validated.
Chris
@everestchris6
May 16
Article
the world is about to change and almost nobody is acting like it
the world is going to change more in the next few years than it has in most of our lifetimes, and the strangest part is that almost everyone is acting completely normal about it. that isn't the...
David Byttow
@davidbyttow
May 14
Insane level of craftsmanship. @Jonathan_Blow doesn’t rush anything and it shows. Can’t wait to play this.
Jonathan Blow
@Jonathan_Blow
May 14
Something we've been working on...
00:00
David Byttow
@davidbyttow
May 13
was reflecting on this today and realized this isn’t new or coming out of nowhere. IIRC, shortly after i joined square (back in early 2012), jack stood in front of the company and informed everyone that we would be doing away with (pure) management roles, most notably in
jack
@jack
Mar 31
Article
From Hierarchy to Intelligence
At Sequoia, we see that speed is the best predictor of start-up success. Most companies are focused on AI as a productivity enhancer. Few are focused on the potential of AI to change how we work...
David Byttow
@davidbyttow
May 2
Oddly reductive. In a narrow sense this is true, but in the broad sense, making the best choices is what wins. And that still on balance means saying no much more than yes.
Jonathan Ross
@JonathanRoss321
Apr 30
For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews. This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No,