Erik Hanchett

@erikch.bsky.social

Senior Developer Advocate at AWS, content creator. Views are my own.

It's really easy to get into a situation where you generate duplicate code, dead code, and lengthy functions. Here are a few tools that I've been using to help eliminate that 👇

I upgraded my personal website using Kiro this weekend. I added dark mode, a better mobile nav, and some fun easter eggs. Hover over the hero image to see for yourself! 👀 +1 if you get the reference.

Building with AI coding agents? 👀 You'll want to catch this one. @erikch.bsky.social (Developer Advocate, AWS) is keynoting CascadiaJS on spec-driven development. Breaking complex features into requirements, design, and implementation with real code and a live demo. June 1–2, Seattle

CascadiaJS Web + AI Conference. Keynote speaker. Erik Hanchett. AWS. June 1 - 2, 2026. Seattle, WA.

I built my own AI butler. 🌝 It wakes up every hour, pulls from Hacker News and Reddit, and sends me a trending stories digest on Telegram. 🚀 Full tutorial + video 👇

AI Butler

One thing I like about Kiro is that it lets you go requirements first or design first. I like this because it fits how I work. Sometimes I’m already deep into the design before I fully know the requirements. Other times it’s the opposite. 👇

Thumbnail that says better than vibe coding

My favorite Roman. “The impediment to action advances action. What stands in the way becomes the way.” Feels just as true in software as it probably did 2,000 years ago.

Picture of emperor

Played around with vinext earlier this week and came away thinking, yeah, frontend tooling is moving ridiculously fast right now. It’s still early, but seeing a Next-like API rebuilt on top of Vite was pretty neat, and the build speed was the first thing that jumped out at me 👇

Erik pointing at 2 logos next and vite with a heart in the middle

🔥 By default autocomplete is turned off in Kiro, however you can easily turn it on by clicking the Autocomplete in the status bar at the bottom. Or bringing up the command pallete (Cmd + Shift + P / Ctrl + Shift + P) and searching for the Kiro autocomplete (Cmd K, Cmd A). 🔥

Autocomplete text

🔥Kiro Tip: When creating a new spec, you'll be presented with a task list after the requirements and design is created. Instead of clicking "Start task" use the chat to tell Kiro how to complete the tasks. For example you could type:👇 Please complete tasks 1-4, stop at 4. 🔥

Screenshot of Kiro tasks.md file with Start task showing

🔥Kiro Tip: Use file matching patterns when creating your steering files! Files are automatically included only when working with ones that match the specified pattern. In this example steering files will only be included in the context for components with the *.tsx extension🔥

Image shows inclusion and fileMatchPattern

Wow! Glad to hear so much support for Kiro! Thanks so much for everyone for sharing and supporting! We are listening, and taking all your feedback. Join the wait list if you haven’t already, we’ll be in touch!.👻

🛫I have a busy few months! If you're at these events come say hi! 🛬 ⛰️AWS Summit New York City July 16th 🍛GOTO Serverless Conference Bengaluru August 8 🌲CascadiaJS in Seattle September 18th-19th See you there!