Engineering culture is experiencing a practical shift—one that's changing how we communicate about software and product ideas. Coding agents aren't just about autocompletion anymore; they're capturing conversations that used to happen outside the coding editor.
Ever think to yourself, "Why even have long meetings about requirements without an agentic coding editor these days?" Thoughts and decisions can be captured instantly, right as you discuss them, directly inside your coding editor.
Conversations Move Into Code
Software requirements and design decisions are usually discussed in meetings or calls. These conversations are often translated later by engineers writing the code. We all know how this goes. The PM wasn't clear, the customer was misunderstood, the engineer slightly misinterpreted the requirements. Then there's endless back and forth to get it right-checking the requirements, checking the code, checking the requirements again, talking to the PM, talking to the customer, etc.
Coding agents let you put those conversations directly into the coding editor as they happen. At Agentuity, a lot of us start out in the coding editor whether it's brainstorming features, marketing ideas, or even planning sales. This way, context never gets lost, and the conversation's nuances become embedded directly into the code or documents we're creating.
Prompting: Clear Context and Immediate Clarity
Prompting isn't just about asking for code. It's about clearly communicating your intentions. Instead of writing lengthy docs, you have short, clear conversations with your agent. As Simon Willison puts it, "You get exactly what you prompt," highlighting the new skill developers must master: prompt crafting.
When we use Devin at Agentuity, even Slack conversations can instantly become actionable tasks in code. The coding agent remembers and references this context, providing clarity and consistency without extra layers of management or documentation.
Persistent Context: Keeping the "Why"
Pull requests often miss the context behind code changes. A valuable improvement we're seeing is capturing the prompting context—the conversation about "why"—and embedding it into the PR itself.
However, there's still room for improvement. Right now, once a PR is made, the rich context of conversations, prompts, and reasons behind changes disappears. Like requirements documents, these prompting contexts should persist permanently, ensuring humans and agents always understand the reasons behind changes.
Imagine reviewing code changes and instantly understanding the reason behind each decision because the prompting conversation with the coding agent is included. This keeps decisions clear, makes onboarding faster, and helps everyone maintain clarity about project direction.
We'd like to see more context and prompt saving in the future. They really should become artifacts that can be attached to the code.
Real-World Example: Our Workflow at Agentuity
At Agentuity, coding agents handle tasks across our business:
- Developing new software features
- Writing blogs and marketing content
- Preparing sales strategies
- Documenting processes and changelogs
Devin, for instance, takes Slack and Linear discussions and directly translates them into clear, actionable coding tasks. We don’t need extra meetings because the entire context is already right there—captured by the coding agent as we talk through it.
Simplifying Collaboration
Coding agents streamline teamwork. Instead of handing off ideas through multiple layers of communication, the agent captures it directly. Code reviews become simpler, more context-rich, and less prone to confusion or misunderstanding.
We at Agentuity definitely see quicker iterations and fewer trivial review comments, allowing us to focus on important decisions.
Conclusion
The cultural change driven by coding agents is practical, immediate, and powerful. Capturing conversations directly in the coding editor saves time, preserves clarity, and simplifies collaboration. It's a wild new world and way to work-and we're here for all of it.