This is 2nd of my #agentanecdotes series where I want to share a story of an insightful session of agentic engineering. This one was particularly fruitful for me, and I'm pretty excited what came out of it, because I feel that it connects directly to a universal feeling
I want to occasionally share stories of full Agentic coding sessions. I feel like it's very hard for me to calibrate my experiences against others, and I bet others are feeling the same way. I don't know if I should be doing more learning or more
Things that still kinda suck. NOTE: This is Part 4 of a series on my education with AI-driven software development. Part 1 is the why. Part 2 is the how. Part 3 is the what. Part 4 is a bit more what, and a lot more what not. I feel
Resource Management For Dummies NOTE: This is Part 3 of a 3 (?) part series on my education with AI-driven software development. Part 1 is the why. Part 2 is the how. Here we finally come to the specific whats. Footnotes are clickable. I feel obligated to add: this was written
Prompt Engineering is dead. Long live Context Engineering NOTE: This is Part 2 of a 3-part series on my education with AI-driven software development. Part 1 is the why. This is the how. Part 3 is the specific whats. Footnotes are clickable. I feel obligated to add: this was written
or: How I Learned to Stop Worrying and Love the Claude NOTE: This is a series on my education with AI-driven software development. I'm starting with why, for those cynical, suspicious, or ambivalent about AI, as I was only 2 months ago. Go straight to Part 2 if
Editor’s note: This was the last internal document I wrote at Amazon. It was written with the mentees, mentors, and friends I left in mind. But the response was really positive, and it seems to have resonated with peers all over the industry, so I decided to re-title it,
