proomt

Search

Search posts, papers, and topics

All posts

HostingerSimon Lim8 min readintermediate

What four people at Hostinger actually do with AI all day (and what happens when you have an agentic beef)

Summary

Hostinger staff use custom AI agents to automate daily tasks—from code reviews to influencer lead sourcing—shifting their work from doing the work to managing the agents. Building reliable “harnesses” (prompt contexts, constraints) consumes most of the engineering effort, and agents still hallucinate, repeat work, or suggest unsafe fixes, so human oversight remains essential.

  • AI agents can replace hours‑long manual workflows (e.g., invoice generation, lead sourcing, debugging) with a few clicks, turning engineers into “managers of agents.”
  • The bulk of the effort is in building and maintaining the harness around LLMs—prompt engineering, context handling, permission management—to keep agents reliable.
  • Hallucinations, duplicate suggestions, and unsafe code fixes are common; teams mitigate by breaking workflows into smaller steps and keeping human validation loops.
  • Human expertise is still required for high‑level architecture, nuanced partner evaluation, and creative brainstorming—areas where models lack domain intuition.

Shows a realistic, mid‑scale deployment of LLM‑driven agents in a SaaS company, highlighting both productivity gains and the practical limits of current AI—valuable for teams planning to automate internal workflows.

5/10

Related reading

  1. Agentic Skill Decay

    Addy Osmani warns that AI agents can short‑circuit the hands‑on practice (“reps”) that builds deep expertise and judgment. He recommends deliberately inserting hypothesis‑forming, “why” questioning, diff inspection, failure prediction, and occasional manual coding into the workflow, especially for junior engineers. A 2026 Anthropic study showed junior developers using AI scored 17 % lower on a fo…

    Addy Osmaniaddyosmani.com16 min
  2. Build Your Own AI Agent Harness in C#, the MafClaw Live Series

    The post walks .NET developers through using Microsoft Agent Framework's harness to turn a simple IChatClient into a fully‑featured C# AI agent, showing code for tool integration, file sandboxing, approval flows, and memory, then outlines further capabilities like skills and observability.

    .NETmicrosoft.com10 minHN2
  3. Your AI coding agent evaluation is only as good as its sandbox

    Evaluating AI coding agents requires a robust sandbox to prevent agents from retrieving answers from the environment, which can invalidate tests of internal knowledge. A correct answer doesn't guarantee a valid measurement if the agent accessed information it shouldn't have, highlighting the need to define sandboxes by information boundaries rather than just tool restrictions. Always review agent…

    Microsoft for Developersmicrosoft.com5 min