Leadership writing is hard, even with AI. Executive summaries, promo documents, writing that actually sounds human.
Check out this skill: github.com/ivikash/Leadershi…
#LeadershipWriting #AI #ExecutiveCommunication #CareerGrowth
If you were to take one thing from this, I'd highly recommend the house rules for writing: github.com/ivikash/Leadershi…
Vikash Agrawal retweeted
I tested 5 approaches to guiding AI agent behavior across 3,000 eval runs to see what actually makes agents reliable. Strands steering hooks was the only one that hit 100% accuracy
Here's how it works:
The key is just-in-time guidance for the model before tool calls and at the end of a turn. Steering handlers observe what the agent is doing and intervene only when the model is about to go off track.
Full results and code in the post
strandsagents.com/blog/steer…
Vikash Agrawal retweeted
You don't need to spend a bunch of money to try openclaw. Amazon Lightsail just released a blueprint for it that you can run for as little as $12/month + whatever tokens you consume. It's also easy to setup. See tutorial here: docs.aws.amazon.com/lightsai…
Prof. Donald Knuth opened his new paper with "Shock! Shock!"
Claude Opus 4.6 had just solved an open problem he'd been working on for weeks — a graph decomposition conjecture from The Art of Computer Programming.
He named the paper "Claude's Cycles."
31 explorations. ~1 hour. Knuth read the output, wrote the formal proof, and closed with: "It seems I'll have to revise my opinions about generative AI one of these days."
The man who wrote the bible of computer science just said that. In a paper named after an AI.
Paper: cs.stanford.edu/~knuth/paper…
Vikash Agrawal retweeted
Today @AWScloud is pushing the frontier of agent development with the launch of Strands Labs—a new GitHub org for experimental agentic AI projects. Push the frontier of agentic development and get started with one of three agent development projects in our new Git organization ➡️ aws.amazon.com/blogs/opensou…
Excited to see what you'll build with Strands Labs.
> Open source is a form of cognitive surplus.
If you visit Europe, cultural surplus is everywhere: small towns that built towering churches, merchants who funded fanciful art they just installed in the market square.
It is a form of what I call ‘cognitive surplus’. Surplus takes the following meaning: you produce more than you need today, so you attempt to store it.
We are all familiar with ‘financial surplus’: you store part of what you earn so that you can consume it later when you are sick or can’t work.
Open source is a form of cognitive surplus. To twist @esrtweet ’s words around, open source is akin to a cathedral. Instead of acquiring financial or military capital, we build this tremendously expensive collection of software. And it is expensive: according to Santiago Calderón et al. (2022), U.S. investment in open source in 2019 was about $37–38 billion.
On the short term, it makes little sense on paper. Why would anyone work hard to build fancy software that everyone can just enjoy without paying?
Yet, if you look around, you see plenty of engineers working in corporations who are in silly jobs. Or you have successful entrepreneurs who have plenty of time for side projects. You have young people who are underemployed, incapable of finding work matching their skills.
Open source offers a way to channel this productivity and make something useful out of it.
Ryan Fleury says that it makes software financially unsustainable. He is right but only in the sense that building cathedrals in small towns was unsustainable.
Chromium is unsustainable. It makes no sense for a company like Google to spend a billion dollars a year (reportedly) to fund a web engine you can just fork and use for free. And yet, it is being sustained (for now).
Fleury is likely correct that open source drastically limits the price of software: Hoffmann et al. (2024) estimate that it cuts the price of software by a factor of about 3.5. But we should be careful: it does not follow that software programmers would earn 3.5 more money without open source. Software has been eating the world in part thanks to open source software... without it, it might be a much smaller industry.
I cannot predict the future but I have proposed that AI coding changes the equation somewhat and might redirect the software cognitive surplus. It is possible that we might stop investing so much in the open source cathedrals. It is becoming increasingly visible that the code crafted with love by some poor engineer in Nebraska is getting milked by large corporations without credit, through AI. Furthermore, it is becoming easier to just automate the boilerplate code, arguably easier to do so than to download an open source dependency.
80% of AI adoption fails because leaders don't use the tools they're pushing.
How my team increased GenAI adoption from 40% → 100% in 4 months using 5 simple strategies.
Here's what worked 🧵 (1/7)
#GenerativeAI #Leadership #TechLeadership #EngineeringLeadership
7/7
5. If you can SOP it, you can automate it
Best predictor of AI success? Clear instructions. Break problems into step-by-step processes first.
AI is great at following structured instructions.
Full post: linkedin.com/feed/update/urn…
#GenerativeAI
This is incredible. Thank you having me @swyx. The event was very well thought out! Kudos 👏🏻👏🏻👏🏻
Replying to @swyx @aiDotEngineer
just when you thought we were done with AIE...
here's Wave 2 of the AIE Online talks! (basically people who submitted late but still submitted haha)
youtube.com/playlist?list=PL…
from @ProgramWithAi , @vmelnikova_en, @aparnadhinak, @kozerafilip, @know_vikash, @lambdapocalypse and more!
🤔📧 What would you do if you meant to send a high-priority email to leadership but accidentally sent a calendar invite instead? 📅😬
And what if that person is 8️⃣ hours ahead in their timezone? 🌍💼
#HappyDiwali
Vikash Agrawal retweeted
Things you can* do with a text UI (TUI):
github.com/NvChad/minty
* and should














