Urgent.News

What's breaking now, across thousands of outlets.

Tech

Design Around Humans

An agent can complete a task independently. That does not make the human irrelevant. We are the fragile part of the interaction. Attention runs out. Fatigue weakens judgment. Understanding takes time. Systems should protect those limits, not overwhelm us with more output to review. Design around humans means helping people reach informed, considered decisions. Surface the relevant context,…

When an agent can carry out a task on its own, it doesn't diminish the importance of the human element. We humans are the delicate component of the interaction. Our attention spans are limited, and fatigue can impair our judgment. Understanding a problem takes time. Systems must not exacerbate our limitations by inundating us with unnecessary information to review.

Designing around humans implies assisting people in reaching well-informed, thoughtful decisions. Display the pertinent context, elucidate uncertainty, render trade-offs evident, and provide space for contemplation. The objective isn't to expedite approval. It's to foster a deeper comprehension of the issue and the ramifications of acting.

This remains pertinent even when agents can perform tasks independently. Tasks hold significance not merely because they are completed. Their worth emanates from aiding people. Human involvement doesn't equate to sanctioning every automated step. It entails articulating the purpose, establishing boundaries, grasping consequential decisions, and retaining the ability to intervene.

It also entails maintaining avenues for learning: at times, grappling with a problem proves more valuable than receiving the final answer. For developers constructing agent workflows, the inquiry transcends, "Can the agent complete this?" Rather, it is, "Does this system aid the person in understanding, deciding, and evolving?" Automate the work without dismantling the human's role in its purpose.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

🥇The Real Value of Event-Driven Architecture Isn't Technology. It's Cost Reduction.

👋 Hi dev community! I originally published this on my LinkedIn Newsletter, but wanted to share it with the dev community here to get your thoughts on how your engineering teams handle infrastructure…

  • Traditional Request-Driven Architecture struggles with integration complexity and rising costs.
  • Event-Driven Architecture (EDA) slashes costs, accelerates delivery, and enhances scalability.

A legal FEN is not a game: state identity in a browser chess extension

Same FEN, different game If you key a chess overlay on FEN alone, two different games can look identical. Rematches are where this shows up.

  • A FEN string alone doesn't define a unique chess game in a browser extension
  • Multiple legal FENs can coexist, each with its own game state
  • Factors like controls, hints, and live move list determine the game's identity

More from Saturday 12 September →