Yow!

Lately I’ve been using an agentic IDE called Kiro for coding tasks, bugs, and small features on our project.

I’m still a noob at prompt engineering, but this feels like the best time to learn. Our company encourages AI use, and we get free access to strong models like Sonnet and Opus — might as well take advantage of it.

A colleague got me into the idea of AI-first workflows. I might try the CLI soon, but for now the Agentic IDE feels like a good starting point. Not everyone’s sold on AI yet (I get it), but for repetitive work, it genuinely helps.

I’m not a vibe coder, though. I don’t blindly accept outputs. My flow is simple: prompt → review → tweak → override. AI assists. I still decide.

I’ve also been maintaining my own AGENTS.md and project guidelines so the AI understands our patterns and structure. Feels like teaching a junior dev how we code.

Recently, I tried Kiro’s Spec-Driven Development (SDD) and it impressed me. From a feature spec, it generated designs, steps, and task breakdowns. Not perfect, but good enough to use as a checklist. It reduces the mental load of “what did I miss?” Maybe someday we’ll one-shot prompt entire features. Not today — but maybe soon.

I was also added to a small AI knowledge-sharing group at work. We explore ideas and build practical use cases for our teams. The goal isn’t replacing devs — just making work lighter and more enjoyable.

For now, I’m just refining prompts, improving guidelines, and learning as I go. Still early. Still experimenting. But coding feels easier — and honestly, more fun.

In software engineering, coding was not really the hardest part 😉😉😉.

On the other hand, kindly support this petition: Make Tuca Donka Hakari's actual jackpot song in the JJK anime

Maybe next, we’ll get one for Lady Gaga’s Judas in Gojo vs. Sukuna 😄