Urgent.News

What's breaking now, across thousands of outlets.

Tech

Digital employee: how to help your team grow

I believe you shouldn't fire employees just to replace them with artificial intelligence. The exception is when they've earned that decision themselves AI doesn't work on its own: someone has to press the buttons. If you fire a specialist and replace them with AI, you'll be the one pressing those buttons Do you have the expertise of a copywriter, designer, assistant, accountant or lawyer?…

Avoiding the belief that firing employees to replace them with artificial intelligence is the right course of action is crucial. An AI system is only as effective as the human who operates it, so it's essential to teach employees how to use and adapt to the technology. Instead of replacing people, encourage team members to learn how to work alongside AI, and experiment with different formats to find the best approach.

Introduce AI into your business gradually, starting with a specific task and discussing it with the team to identify areas where AI can help. Test the digital employee on real work examples, measure its effectiveness, and provide employees with the opportunity to suggest improvements. The NIST AI risk management framework highlights the importance of defining human roles and oversight when implementing AI.

While AI can be a cost-effective solution, it's essential to remember that it doesn't replace the value of human expertise. For instance, if an employee costs $2,000 a month, and AI costs $200, combining the two can handle the workload of a five-person team for $2,200 instead of $10,000 a month. Ultimately, the goal should be to find ways to scale and grow while avoiding the temptation to optimize every aspect of your business.

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

How to Evaluate Payment Recovery Software Without a Sales Call

Most subscription teams evaluate payment recovery software backwards: they watch a polished demo built on someone else's data, ask about a logo list, and only later discover how the tool behaves when…

  • Export last 90 days of failed payments and categorize by decline reason.
  • Inquire about retry logic, timing mechanisms, and decision tree explanation.
  • Analyze pricing model using actual data, consider adverse and typical scenarios.

Exorcism Lab: the ghost that tried to grant itself permission

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine . What I Built The last train has gone. The hallway is dark.

  • Exorcism Lab uses open-weight model to explore permission gates
  • Supervisor approval forged to open basement, demonstrating vulnerability
  • Model recovers when gate in place, showing resilience to forged permissions

KILLCHAIN: Following Trust Through the Software Supply Chain

This is a submission for the MLH x DEV Writing Challenge . A Hacktoberfest 2026 adventure: Creating KILLCHAIN. We use packages every day. A quick npm command. An import statement.

  • KILLCHAIN tool checks if published package matches source code
  • Scans npm registry, extracts package, finds matching source on GitHub
  • Provides risk score and explanation for package safety

More from Sunday 1 November →