[james_ross]

this seems to be a load bearing claim in the article: "success is determined by how well a person understands the problem they are trying to solve, not whether they’re trained in coding."

I would normally assume that my understanding of the problem I'm trying to solve is a blend of domain knowledge and system knowledge; that is, some of the what and some of the how. And just as important as bringing domain knowledge to the table is bringing the ability to articulate it with conceptual clarity in a way that bridges to the software. I have met many very deep domain experts who don't have that skill.

My personal interest of late is in capturing domain knowledge and managing it like source code, and using it to share with both the humans (in visual form) and the agents (in plain text form) some of that foundational understanding to make them both better at both the what and the how. This seems aligned with the article when it says "the more understanding a worker brings to an agent, the more quality work the agent is able to do" but I would also say that the more understanding we can bring to future humans new to the domain has pretty good ROI as well.