How Non-Technical Teams Are Starting to Assign Work to AI Coding Agents

By Steve180 · · 1 replies

Something interesting is happening with AI coding agents: the people assigning development work are no longer necessarily the people writing the code.

Product managers, QA specialists, founders, and operations teams can describe bugs or feature requests in natural language. The coding agent handles the implementation in an environment configured by an engineer.

This is the approach behind Sharkly.ai, which provides Tasks, Agents, Crews, and Automations to organize AI-assisted work.

For example, a non-engineer can create a task, assign it to an agent, and follow its progress. The engineering team remains responsible for repository access, technical configuration, and reviewing code changes.

I think three capabilities matter most:

1.Simple task creation for non-technical users.

2.Visibility into agent progress and execution history.

3.Human review before code changes are accepted.

The integration of Slack, Jira, and GitHub can also help connect this workflow to existing team processes.

Product: https://sharkly.ai/

Do you think coding agents will eventually become a normal way for non-engineers to request software changes?

Editing your thread.
Reply
Add images Up to 2 images, 3MB each.
0/2
You must be signed in to reply.
Replies

CapacitorFlux

I think yes, but only for small and clear requests at first. Things like a text change, a broken link, or a simple bug that comes with clear steps to repeat it. A non-engineer can describe those well, and an engineer can check the result in a few minutes.The harder part is that people often don’t describe the real problem. “The page is slow” or “the button doesn’t work” can mean five different things. So I think the quality of the task description will matter as much as the agent itself.Your third point is the one I agree with most. Human review before anything is accepted is what makes it safe for non-technical teams to use this at all.How do you see the review step working in practice? Does the engineer check every change, or only the bigger ones?

Related discussions

Popular in this category