I just had an AI agent read through 100+ of my blog posts and tell me exactly where to add internal links. In 30 minutes, it found connections I'd missed for years. Here's how I did it.
Have you ever wondered why some teams seem to effortlessly deliver value while others stay busy but make no real progress?
I recently had a conversation that completely changed how I think about leading teams. While discussing team performance with a VP of Engineering who was frustrated with their team's slow progress, I suggested focusing on better standups and more experiments.
That's when Skylar Payne dropped a truth bomb that made me completely rethink everything:
"Leaders are living and breathing the business strategy through their meetings and context, but the people on the ground don't have any fucking clue what that is. They're kind of trying to read the tea leaves to understand what it is."
That moment was a wake-up call.
I had been so focused on the mechanics of execution that I'd missed something fundamental: The best processes in the world won't help if your team doesn't understand how their work drives real value.
In less than an hour, I learned more about effective leadership than I had in the past year. Let me share what I discovered.
When I talk to engineering leaders struggling with their AI teams, I often hear the same frustration: "Why is everything taking so long? Why can't we just ship features like our other teams?"
This frustration stems from a fundamental misunderstanding: AI development isn't just engineering - it's applied research. And this changes everything about how we need to think about progress, goals, and team management. In a previous article I wrote about communication for AI teams. Today I want to talk about standups specifically.
The ticket is not the feature, the ticket is the experiment, the outcome is learning.
Helping software engineers enhance their AI engineering processes through rigorous and insightful updates.
In the dynamic realm of AI engineering, effective communication is crucial for project success. Consider two scenarios:
Scenario A: "We made some improvements to the model. It seems better now."
Scenario B: "Our hypothesis was that fine-tuning on domain-specific data would improve accuracy. We implemented this change and observed a 15% increase in F1 score, from 0.72 to 0.83, on our test set. However, inference time increased by 20ms on average."
Scenario B clearly provides more value and allows for informed decision-making. After collaborating with numerous startups on their AI initiatives, I've witnessed the transformative power of precise, data-driven communication. It's not just about relaying information; it's about enabling action, fostering alignment, and driving progress.
Look, creating content that matters is hard. Here's how to craft impactful content without the bullshit.
Look, creating content that actually matters is hard. Here's how to do it without the bullshit. These strategies apply whether you're writing tweets, creating consulting content, or building your personal brand:
Titles That Demand Attention: Your title is the gatekeeper. Make it count or no one will read your shit.
Hook with a Powerful Intro: You've got 15 seconds. Don't waste them.
Use Evidence, Not Adjectives: "Our platform is blazing fast" means nothing. "3ms average response time" does.
Foreshadow Value: Tell them exactly what they'll get. No vague promises.
Structure for Scanners: People skim. Deal with it. Use headers, bullet points, and short paragraphs.
Make It About Them, Not You: No one cares about your journey. They care about their problems.
Be an Oracle: Predict future challenges. Be right more often than not.
One Clear Call-to-Action: What do you want them to do? Ask for it. Once.
Iterate Based on Data: If it's not working, change it. Ego has no place here.
I'm gonna write something technical.
It's often less about the nitty-gritty details of the tech stuff and more about learning something new or getting a solution handed to me on a silver platter.
Look, when I read, I want something out of it. So when I write, I gotta remember that my readers want something too. This whole piece? It's about cluing in anyone who writes for me, or wants me to write for them, on how I see this whole writing product thing.
I'm gonna lay out a checklist of stuff I'd like to have. It'll make the whole writing gig a bit smoother, you know?
The goal of this post is basically to share what I have learned about writing a tweet, how to think about writing a hook, and a few comments on how the body and the cta needs to retain and reward the user. Its not much, I've only been on twitter for about 6 month.