I write about technology, humanity, and books.
I sent this to my team yesterday. I’m sharing it here because I think many of us are still trying to figure out how to best adopt AI into our workflows. This is meant to be more of a manifesto than a prescriptive recipe. A lot of this might apply only to my specific situation. Your org might be at a different stage and ready to go fully agentic, in which case some of these points might not apply.
AI reviews are getting very good at surfacing bugs that are not the immediate thing you are fixing, but are close to it, and this is surfacing the Boy Scouts on your company.
I run a Shopify app that I’m trying to grow organically. Every other week I look at App Store traffic and adjust the listing based on the patterns I see in Google Analytics.
I remember when the coding flip happened for me and I stopped writing most code by hand. It was September 2024. I had long uninterrupted stretches to tinker with AI tools.
I’ve always been interested in personal productivity, habits building, and how to foster spaces that allow me to think and work free from distractions.
Yesterday while reading Atomic Habits I came across two new concepts which are called immediate return and delayed return environments.
I often chat with people in the Stellar Slack who want to build something similar to Venmo and they tend to struggle understanding how different concepts apply for what they are trying to do.
My favorite engineering team out there is probably Artsy. If you go through their blog you might understand why. One of their core mantras is “Open Source by Default”.
I left my job at Envoy without any specific plans in mind. I wanted time off to take care of personal stuff and then figure what to do next.
I’ve been reading a book titled “How Adam Smith Can Change Your Life” by Russell Roberts (@econtalker). I thought this book was going to be a mix of philosophy and Smith’s “The Wealth of Nations” but I was wrong.