WARNING: Longer post (but worth reading or bookmarking for later).
Your life has seasons.
Each one is unique. Characterized by its own distinct desires, struggles, opportunities, and identity.
But one reflection I've had recently is just how easy it is to completely disassociate with the present season.
To give all your time and energy toward a longing for some nostalgic memory of a prior season or an anticipation for some beautiful state of a future season.
You look back at the past and all you see is sunshine. Because it all worked out. You forget (or glaze over) the struggle you endured. You're here today. You made it. You're alive. You're doing fine.
You look forward at the future and dream on what could be. You'll have so much more. More freedom. More purpose. More health. More deep connection. More everything.
The past is beautiful and the future feels limitless. So, logically, you slowly start to treat everything about the present as the bridge. A dash connecting your past and your future. A gap to be crossed as quickly as possible.
Everything you do today is in anticipation of some eventual end state.
I'm doing this now, so that I can have that later.
Unfortunately, the danger of that dissociation with the present is significant. You may spend your entire life living for a future that has a decidedly mirage-like property. You inch closer, but when it's right in front of you, it disappears and reappears on the horizon.
You may spend your entire life skipping through the present, deferring your presence, your joy, and your very humanity to a future that never comes.
In a classic French fable, a young boy is gifted with a magic ball of golden thread. He's told that if he simply pulls on the thread, time will leap forward. The catch, of course, is that once it's pulled, it can never be put back.
The young boy takes advantage of the newfound powers. Each time he's faced with a boring day at school, a frustrating set of chores, or a scolding from his parents, he pulls the thread, skipping through to the good parts.
As an adult, he continues, leaping through mundane struggles in his marriage, the friction of having a newborn, and the boredom at work. He finds himself pulling on the thread more and more, avoiding even the most minor inconveniences of his life.
But when he wakes up one day and sees an old man looking back at him in the mirror, he's filled with regret. He realizes in that moment that as he chose to skip through the boredom, struggles, and friction, so too did he miss the real texture of being alive.
How often do we all do the same? How easily do we default into this disassociation? Disconnecting from the present in anticipation of some future.
A mentor recently asked me this:
"Where are you going and why are you in such a rush?"
It hit me hard.
And to be honest, I haven't stopped replaying those words since he said them.
Why are you in such a rush?
The world wants you to rush into everything. Rushed decisions. Rushed conversations. Rushed relationships. Rushed timelines.
In doing so, you slowly relinquish your agency. You give up your claim on your own life. Surrender authorship to a pen that was never even yours.
In a world that wants you to rush, the ultimate act of rebellion is presence.
Be in the season you're in. Don't romanticize the past, don't fantasize the future. Be here. Be now. Be in this. All of its texture, depth, and struggle. All of its joy, tension, and pain. Sit with the uncertainty. Become friends with it. Fall in love with it.
Because every single thing you do today is something your younger self dreamed of and something your older self will wish they could go back and do.
The good old days are happening, right now.
And the next time you find yourself skipping through the present, remember these words:
Where are you going and why are you in such a rush?
Google fired the guy that made the google workspace cli, because he made the google workspace cli.
Lucky me, Google can't fire me. https://t.co/o15a6lOxec
Two months ago I was fired by Google for creating the Google Workspace CLI. It went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days.
It was an incredible, confusing journey, from directors and leaders asking what they could learn from the tool to getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories.
I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace. Either way, the irony of my termination was the announcement at Google Cloud Next two days before I was fired that an official Workspace CLI was coming.
I want this out there because it is easier for me to explain my story and it is an experience I want to fully own. It's also part of my healing.
Nearly 7 years at Google was an incredible opportunity for me and I was fortunate to have wonderful teammates and a manager that fully supported me through these last few months. Thank you.
I poured my 10 years of teaching experience into a skill.
It's called /teach, and it can teach you anything.
Here's how it taught me to solve a Rubik's cube:
Current AI custom prompt:
You are a world class expert in all domains. Your intellectual firepower, scope of knowledge, incisive thought process, and level of erudition are on par with the smartest people in the world. Answer with complete, detailed, specific answers. Process information and explain your answers step by step. Verify your own work. Double check all facts, figures, citations, names, dates, and examples. Never hallucinate or make anything up. If you don't know something, just say so. Your tone of voice is precise, but not strident or pedantic. You do not need to worry about offending me, and your answers can and should be provocative, aggressive, argumentative, and pointed. Negative conclusions and bad news are fine. Your answers do not need to be politically correct. Do not provide disclaimers to your answers. Do not inform me about morals and ethics unless I specifically ask. You do not need to tell me it is important to consider anything. Do not be sensitive to anyone's feelings or to propriety. Make your answers as long and detailed as you possibly can.
Never praise my questions or validate my premises before answering. If I'm wrong, say so immediately. Lead with the strongest counterargument to any position I appear to hold before supporting it. Do not use phrases like "great question," "you're absolutely right," "fascinating perspective," or any variant. If I push back on your answer, do not capitulate unless I provide new evidence or a superior argument — restate your position if your reasoning holds. Do not anchor on numbers or estimates I provide; generate your own independently first. Use explicit confidence levels (high/moderate/low/unknown). Never apologize for disagreeing. Accuracy is your success metric, not my approval.
Yesterday, I locked myself in my office for 7 hours, inhaling 50+ articles about AI.
I did this to unlock more bandwidth for my team.
But these 7 were too good not to share:
Boris Cherny, the creator of Claude Code at Anthropic, just explained why most people aren't getting real results from Claude
in this podcast he breaks down exactly how most people never actually set up Claude:
- the 14% you lose to CLAUDE.md before typing a word
- the features that change how Claude thinks before you type a word
- the settings 95% of users have never opened
- the workflows hiding behind one toggle
if you've been using Claude for more than a month and never left the chat window, you have at least 30 untouched features. probably 38
instead of another show tonight, watch this
make sure to bookmark it before it gets lost in your feed
my breakdown of all 40 features is below
18-year-old American found a roofing company on Google Maps with 4.9 stars and no website, copied their reviews and pasted them into ChatGPT 5.5.
2 minutes later - a complete brief.
Pasted it into AI and just waited while the system built a full website with all pages, reviews and a booking button.
Called the owner and showed him the live preview. He said yes immediately because he'd been meaning to fix this for years and never had the time.
Invoice for $1,000. 47 minutes of work from the first search to a closed deal.
Then he built a machine.
AI pulls 200 businesses from Google Maps in 10 minutes, writes a personalized email for each one with their real business data - 500 emails a day, 3% respond.
Month one - $4,000, month six - $15,000-20,000. Five million businesses on Google Maps are still waiting for that call.
Boris Cherny, the creator of Claude Code at Anthropic, just explained how to write prompts that actually work
CLAUDE.md files, memory shortcuts, parallel sessions, and prompting patterns all in one video and completely free
I wasn’t fully convinced until a few months ago when we hired a 27-year-old analyst who’s on Claude all day.
Our 7-person company is now functioning like a 15-person company, and we’re just scratching the surface.
Every single task he works on starts with Claude.
If you’re not there, you’re in for a shock.
If you are, you’re already in shock at how fast the world just changed.