Influences
Inspired by a tweet. This is an incomplete collection of influences that caused me to become a software engineer.
Influences
Inspired by a tweet. This is an incomplete collection of influences that caused me to become a software engineer.
This talks about value capture by focusing on the most critical point of leverage
This aligns with what I know to be true. You probably won't get it right on the first try. You probably don't know what right looks like. But keep at it and it'll become apparent in the fullness of time
listening to this, and then a podcast about the telephone made me comfortable that i could learn any and everything about how the internet worked.
i felt this one so deeply because it relates to how certain sedimentary rocks form — accretion. most software is an ongoing effort.
this was a major unblock for me after hearing people talk about building for so long. they were talking about building abstractions. iteratively. over time.
“it’ll take [x] years to do it” “[x] years will pass anyways”
this book for sure. it starts so simple. too simple. if-else + loops → … → every conceivable form of software
one of those things that’s hard to unsee or stop speaking about once you see it
this one too
not specifically this post, but the graphics that accompanied it