Skip to content
360SOFTY
HomeInsights

Insights

Ideas for building
better software.

Engineering perspectives on architecture, product development, AI, and the everyday decisions behind useful software.

From the engineering desk

Browse practical articles or follow the latest technology updates.

Subscribe via RSS →

Curated links from external sources — not 360Softy original articles.

ExternalSoftware Architecture
Martin Fowler

The Orchestrator's Tax

Subagents get justified by time saved and parallel execution, but Rahul Garg explains that's not what matters most. Every token in the orchestrator's context is competing for its attention, and the real value of a subagent is what it keeps out of that context. Subagents should be treated as a tool for protecting the orchestrator's working memory, offloading reasoning it doesn't need to hold onto. Doing this well means giving the orchestrator explicit ground ru

Martin FowlerRead original
ExternalCybersecurity
SecurityWeek

OT Security Startup Frenos Raises $1.52 Million

The company will use the fresh investment to grow its customer success and AI R&D teams. The post OT Security Startup Frenos Raises $1.52 Million appeared first on SecurityWeek.

Cybersecurity FundingICS/OTFrenos
SecurityWeekRead original
ExternalObservability
Grafana Blog

Telemetry-driven development: How to gain confidence in your coding agents' behavior with gcx and Grafana MCP

You’re about to click "Merge" on a PR, but you feel more anxious about it than you used to. Why?  You did everything properly, by today’s standards: You used Claude to create a plan, giving it context from a GitHub issue and some Slack threads. You iterated on it a few times; Claude says it has the full picture. It feels ready, so you get Claude Code to implement the plan. You run a review agent against the diff and get some of those comments addressed. You start reading the diff, but it's long.

Grafana BlogRead original
ExternalSoftware Engineering
DZone

How Does an LLM Request and Response Cycle Work? A Full Walkthrough

In this blog post, we will see how an LLM request and response cycle works, from the second you hit send to the moment the last word lands on your screen. I will not throw a wall of transformer math at you. Instead, we will follow one single prompt through every stage of the journey, so nothing feels abstract. I got curious about mapping this out properly while building iamspeed.dev, my browser-based LLM benchmarking tool. Before I could measure things like tokens per second or time to first tok

DZoneRead original

Let’s start with a conversation

Tell us what you’re working on.

An idea, a challenge, or a system that needs to work better. We’ll help you understand the next step.

Discuss your project

Prefer email? [email protected]