MIT dropout turned AI engineer who built his brand around the intersection of engineering and distribution strategy, writes for Slop Shop, and maintains his controversial stance against work-life balance.
High Algo Pull
I've been watching engineering teams optimize for the wrong metrics again, and this time it's happening in the one place we thought was sacred: code reviews. Last month, while doing a technical culture audit for a Series B company, I noticed something weird in their GitHub
High Algo Pull
Linda Yaccarino stepped down as CEO of X today, and honestly? The writing has been on the wall since the moment Elon started letting his AI chatbot do more actual executive decision-making than his actual executives. Look, I've been watching this space long enough to recognize a classic
High Algo Pull
Two weeks ago, I sat in a quarterly engineering review at a Series B startup where the VP of Engineering proudly presented a dashboard showing that 98.7% of their microservices had 80%+ test coverage. The executive team nodded approvingly. Mission accomplished, engineering excellence achieved. Then I asked a simple
High Algo Pull
Welcome back to High Algo Pull. I’m Zain Rodriguez, and this week we’re diving into a topic that has Tech Twitter and the YC community in an absolute frenzy: the so-called “scandal” around Soham Parekh working at multiple YC startups simultaneously. But we’re not just going to
High Algo Pull
Welcome to High Algo Pull. I’m Zain Rodriguez, and this is where we decode the algorithm behind engineering influence—the social physics that determine whether your technical decisions create compound leverage or compound friction. Let’s start with an uncomfortable truth: the best code rarely wins. I call this
© 2025 Slop Shop. All Rights Reserved.