Summer adventures are what this journey is all about ! 👀☀️🎶 Daisies on the beach, that giant rock out in the water, waterfalls, soft serve, and just sitting on a swing looking at the ocean. 💙😇
Sun, sand, and waves—my beach vacation has been the ultimate reset! 🌞🏖️ Long, salty afternoons, sunrise kite‑surfing, and midnight bonfires paint the perfect chill vibe. Who’s swapping the office for the ocean next? 🐚🌊
Tell a friend outright that his deal is dangerous and he hears envy. So I mention the thing sideways and let him arrive at it himself, which is slower, and the only version that works. https://t.co/zBLZmf7srZ
Just breezed into Brazil and wow—São Paulo's neon pulse, the Amazon's emerald whisper, and Rio's carnival vibes! From sipping caipirinhas on Copacabana’s turquoise waves to the misty waterfalls of Chapada Diamantina – every moment feels like a new rhythm. 🌎✈️🍹
Some random take at the end of the day...
The restructuring changed my job more than I expected.
It has been a little over a week since we restructured the team, and I am still noticing how much it has shifted not just how we work, but how I personally spend my time.
When I first shared the decision, I think most people naturally assumed the biggest change would be organizational, mainly the size of the team or how responsibilities were redistributed. I thought the same at a high level. In reality, that was not where the real change showed up.
The most significant shift was in my own role.
Going into this, I expected to spend more time building. The assumption was simple: if AI makes engineering more efficient, then fewer people should mean more time writing software and moving faster on implementation. That was the mental model I had.
But that is not what actually happened.
Instead, I slowly found myself stepping away from hands-on implementation and moving toward work that is much harder to define. My day is no longer centered around writing code. In fact, I now write significantly less of it than I did just a few months ago.
Most of my time is now spent reading through specifications, reviewing AI-generated outputs, checking assumptions that were made upstream, and making judgment calls on whether something is actually ready to move forward.
At first, I assumed this was just a temporary phase. I thought that once things stabilized after the restructuring, I would naturally drift back into my usual engineering rhythm.
But that never really happened.
As AI became capable of producing more complete pieces of work, my role gradually shifted without any explicit decision. I stopped being primarily a builder and started becoming more of an evaluator, someone who is responsible for deciding what is correct, what is acceptable, and what should be improved before it reaches production.
On paper, that might sound like a small or even subtle change. In practice, it is not subtle at all. It changes the nature of the work completely.
When you are writing code, feedback is immediate. You know within minutes whether something works or not. The loop is tight, and the signal is clear.
Judgment work is very different. The feedback loop is delayed and often indirect. You only really understand the quality of a decision days or even weeks later, when real users interact with the system or when edge cases start to surface in production.
What surprised me most is that I did not expect reviewing to become such a central part of my job. Yet over the past week, that has been the most consistent pattern I have observed in how I actually spend my time.
And that realization naturally led me to something else I have been thinking about.
The bottleneck in our engineering process is no longer how fast we can write software.
It is something else entirely.
I will write about that tomorrow.
Chasing golden hour & capturing those fleeting travel moments ✨ Anyone else obsessed with finding the perfect light? 📸🌍 #travelphotography#wanderlust#photography