This week I started the Agentic Engineer Nanodegree through AWS AI & ML Scholars, the next step in what has become my increasingly formal attem...
For further actions, you may consider blocking this person and/or reporting abuse
Haha, the initial confusion between React and ReAct is so real! 😂
That loop of 'build first with AI leverage, learn the formal terminology later' is pretty much how most of us are navigating software dev right now. Loved this write-up!
@hoseinmdev, you get it! 🤣 And thank you. I appreciate it.
@earlgreyhot1701d The names are definitely not keeping up. Every new tool gets a name that sounds like a failed startup from 2015 and we just accept it. At some point the namespace will be so full that the next one has to be called 'tool' and we will all just know which one.
Ha @nyx533! I can see it now...
This hit close to home from the mirror-image direction. I came into this with zero programming background, built my first project (a Telegram bot) as a monolithic copy-paste mess without even understanding Python indentation properly — then spent months rebuilding it modular from scratch, purely through trial and error with whatever an AI assistant produced.
Somewhere in that process I ended up reinventing RAG and a crude memory system before I knew those were established, named things with papers behind them. Found out the vocabulary existed only after the behavior already did. Same gap you're describing, just approached from the other end — building first, discovering the name later instead of studying the name and then recognizing it in your own repo.
The "which came first, the building or the learning" question doesn't feel like it needs an answer so much as it describes what AI-assisted building actually is right now for a lot of us. The formal vocabulary is still worth chasing down after the fact — it's the only way to know if what you built generalizes, or if it just happened to work on your specific case.
@mansio , yes I see your point and maybe not having an answer to what came first is part of the journey and we may never get to the end. It feels good not to be alone in this!
ReAct is a great name for the pattern. The trouble is that every paper that names a pattern ends up owning the conversation more than advancing it. The field would be healthier if more patterns shipped as reusable tooling with boring names.
Ha, great point @nyx533 ! It would definitely make it easier. The amount of tools of infinite and it seems like the amount of names...are not? 😆
@earlgreyhot1701d The mental image that keeps me awake is the agent thinking it has won because the loop never exited. No alarm, no crash, just an escalating tax on every subsequent cycle spent re-reading the same context.
A little off-topic, but I’m also part of the Future AWS Agent Engineer track through AWS AI & ML Scholars! It’s honestly so nice to see someone else from the DEV community in the same program. Looking forward to following along with your journey!
Hi @hemapriya_kanagala! Woohoo! Agreed. I'm excited to have a Dev colleague as a classmate! I hope the first week of the curriculum has been interesting and enjoyable for you. I've already learned so much 📚️