Abandoned again. Well, not abandoned, but that's what it felt like. Siv brushed down the front of her long bekae, which was a long piece of sky blue cloth she pulled over her head and cinched at the sides with a wide violet sash. It allowed her a lot of movement as it didn't restrict her legs. Yes, her hips showed easily, but she didn't mind. She preferred the freedom of movement. Not only that, she had trained as a smekihanxa with the Peridot Order of House Aldinav. As a courtesan in training, it meant she was used to being around people of higher ranks than most maids and was much more familiar. Siv had learned the art of the laugh, the witty banter, and how to touch someone's arm or shoulder in just the right way to make them relax. Unfortunately, she wasn't cut out for courtesan work after causing a rather embarrassing situation between two houses. Since then it had taken practice to remember how proper she should be.

Siv shivered at that thought but focused on what she was doing now. She was an Estate Maid of the 1st Order and a Mistress Apprentice. Those were big things to focus on, but the young woman had earned Mistress Maevin Maer's trust. Siv had been left in charge as Mistress in Standing since Maevin had to handle the Council of Servants for the planet. That was not something Siv wanted to be involved with.

Smoothing her dress out once more, checking the red silk scarf around her waist and running her hands through her two-tone hair, Siv gently rapped on the wooden door of her Lord's office.

“Come in!”

Henry Patton always sounded so exuberant. His curiosity and fascination always brought a smile to Siv's face. He was even gentle with her and the servants, which endeared everyone to him even more. The young woman stepped in, placed one hand atop the other at her waist, and bowed.

“eta mleteematae Siv kive, xixihanvashav.” Siv is here to serve, my master.

“Oh! Siv!”

There was that smile. Her lord was quite excited today. He had a bunch of compu-pads all over his desk, their crystal screens catching the sunlight through the window at odd angles. The entire desk had the look of someone who had been digging through information for the better part of the morning. The window behind him was wide open and a nice breeze was blowing through.

“I have something for you to do. Maevin was going to handle it but things got moved up; she's on the other side of the planet you know.”

Yeah, she knew. The world of the Houses was always moving and it was a delicate dance due to how much the houses could mistrust each other.

“What is it that you require me to do?”

“It's about the veehanaeset.”

The Soft War. Yhe meeting that Lord Henry was putting together with the estates on the planet. The woman's heart jumped slightly at the word. Yes, of course there were other estates here. Victory was an important hub, though House Avernell was the dominant one. Unlike smaller planets that may only have one estate, this planet meant the dance was much more subtle and intense.

“And how can I help with that?”

“I have been informed that Iron Forge, Black Fall, Morning Dew, and Crystal Spring estates are going to be here later this afternoon. They're sending representatives to hammer out the details among the orders before their lords and ladies arrive.”

Siv swallowed. Now she wished she was at the Council of Servants. What Henry was telling her was that she was going to be responsible for negotiating with rival houses on how the entire event was going to go. By the gods, she wished Maevin were here. When it came to her training, Siv did not have much.

“Do you have a list of those who are coming as representatives?” Siv asked, trying to sound calm and not as nervous as she was.

“Let's see. Mistress Niva Atama of Iron Forge, Steward Vedarat of Black Fall, Lady Halesia of Morning Dew, and Estate Maid of the 1st Order Minaka of Shova.”

A lady. Siv swallowed. Not only were there two servant leaders coming but a Lady, a lady who, if memory served, was the first wife of the Duke of House Nevakev.

“Are you alright?”

Lord Henry's voice cut through the chattering voices in her head. The maid bowed more deeply to hide the embarrassed flush in her face. “I apologize, my master. I was simply caught off guard by the rankings of those coming. I am only a Mistress Apprentice.”

Henry nodded and then set down the compu-pad he had been holding. “Siv.”

The woman looked up to see her master looking right at her.

“While Maevin is gone, you are my mistress. I don't care that your title has 'apprentice' attached. You are to be respected like a mistress, and if they don't, I expect you to tell me. No one is going to be insulted here just because I'm human.”

Siv's heart trilled a bit in her chest at such a vehement defense of a servant. No wonder so many maids had crushes on him.

“As you wish, my master.”

---

The living room was not really massive, but the way the furniture had been placed gave the area a feeling of grandeur. The sofas had been placed against the walls, with another lush one close to the center. There were a few large, firm cushions for people to lounge on if they preferred to stretch out. Comfort was the spirit of House Avernell.

The hardest thing was waiting. Siv had asked Nish if she would escort the arrivals to the living room. That woman was very steady and level-headed, unlike her lover Abiva. The Mistress Apprentice wanted to be there herself but that would weaken her position. Maevin never went to meet any other servant except when it was a person of high stature. It twisted her gut trying to decide how to treat Lady Halesia, and the Emissary maids were no help. The protocol for the wife of a lord who didn't hold a title except by marriage was a very big gray area. In the end, the young woman had decided to wait here and ask Nish to show far more deference to her than to the others. Hopefully that wouldn't get her into trouble.

When she heard the patter of feet coming, Siv took a deep breath, smoothed down her dress, and turned, trying to smile warmly but in charge. The group of people who came in were jarringly different from each other.

Nish led the way. The woman with the blonde short-cut hair placed one hand on the other in front of her waist and bowed. Siv appreciated the fact that the Arch Maid bowed much further than she needed to, helping cement that Siv was in charge. Behind her came the others.

The first was someone that Siv recognized immediately. They had had enough dealings with Iron Forge Estate that only the newest people did not know Mistress Niva Atama. The woman was the opposite of how the Mistress Apprentice was dressed. A long charcoal black robe trimmed in gold wrapped around her, the rich material catching the natural light as she moved. Her silver hair was in three braids that wound down her head and faded into a dark brown, almost blending with her clothes. A rather ornate gold crown sat on her head, the gems dangling from it bouncing as she walked. A thick dark yellow sash was wrapped around her waist and she wore matching gauntlets of metal that gleamed in the light. For anyone else this would be a weapon and forbidden, but Siv knew she had earned those by fighting off a Drull attack in a different star system. They were her badges of honor, and the Mistress Apprentice had no pressing reason to ask for their removal. The way that Niva watched her, Siv was pretty sure she was waiting for a challenge.

The next to come in was a tall man wearing simple pale blue robes that fit him well and had larger, pointed shoulders, a style common among House Devenek. The silver sash around his waist denoted that he was a Steward, the male equivalent of a Mistress, and this had to be Vedarat. The man gave her a nod of acknowledgement.

The last two came in together, one all gentle smiles and the other quiet.

“xikihanma daexugee!” Lady Halesia said, reaching out with both hands, striding forward, and taking Siv's in her own. “It is so wonderful to meet you. I have heard of you and your training under Mistress Maer. It is sad that she is not here for me to compliment your skills.”

Siv did her best not to blush. A Lady of another house complimenting her?

Halesia carried herself with an effortless grace that drew the eye immediately. Long, wavy hair cascaded past her shoulders, pinned back with a delicate bow that softened the sharp elegance of her features. Her face was warm and open, lips curved into a smile that suggested she knew exactly the effect she had on people and probably enjoyed it.

Her outfit hugged her figure closely, a fitted bodice cinched at the waist, paired with sleek dark leggings that disappeared into tall boots. When Halesia spoke, her voice carried a practiced charm, her words chosen with ease. She had made no visible effort to do anything except greet them, but Siv already felt that she could easily take over the discussion. So many powerful figures here and she was on her own.

Don't screw this up, the Mistress Apprentice scolded herself.

The last person was Estate Maid of the 1st Order Minaka of House Shova, and it took everything in her not to startle. Large, jagged white scars ran down the left side of her face, marring her look. Her dark eye on one side moved while the other was a white electronic eye with electric blue veins. This woman had been through something. The sitting room felt smaller with all of them in it.

Siv gestured to the sofas and cushions, keeping her expression warm and her voice as even as she could pull off. “Please, make yourselves comfortable. Refreshments will be brought shortly.” She had already arranged for Burdak to have a few of his maids bring tea and the eflen cakes that were a specialty of House Avernell's kitchens.

Niva did not so much sit as install herself. She chose the central sofa, spreading the weight of her charcoal robes around her like a declaration of territory and placed her gauntleted hands on her knees. The gems on her crown caught the afternoon light coming through the wide window and threw small bright shapes across the ceiling.

Vedarat settled into the armchair to the left, crossing one leg over the other and folding his hands in his lap. He said nothing yet, but his eyes moved around the room with a slow, measured attention that reminded Siv of someone taking inventory. Hadn't Maevin said the quiet ones should be watched the most?

Lady Halesia settled gracefully onto one of the firm cushions near the center, tucking her legs neatly beneath her and smiling as though this were a pleasant social call rather than a negotiation. Minaka positioned herself slightly behind and to the right of Halesia, spine straight, scarred face unreadable, her mismatched eyes fixed on the middle distance. Siv took her place standing before them, hands folded at her waist.

“I want to thank each of you for coming on behalf of your houses. Lord Henry is honored by the presence of such distinguished representatives and wishes this meeting to be fruitful for all parties.” She paused just a breath. “I also want to acknowledge that Mistress Maer would normally be conducting these discussions. In her absence, Lord Henry has placed his full confidence in me, and I intend to honor that trust.”

She watched Niva's expression during that last part. The Mistress of Iron Forge did not roll her eyes exactly. She simply let her gaze drift to the window and back in a way that communicated everything without committing to anything.

“As your presence is a tentative agreement to participate in the veehaneaset, it is important for us to make sure that everyone is comfortable. This is supposed to be an informal gathering and my master has made it clear he wants comfort and safety to outweigh any ceremony.” Siv said, trying not to let the words all spill out.

“Outweigh ceremony?” Niva's voice was smooth and low and carried the particular weight of someone who had never been told no and had survived it. “That is a very generous sentiment.”

“Blue Blossom Estate extends it sincerely.”

“Then perhaps your master can explain how this can be maintained when tradition is important not only to my house but to others like House Shova?” Niva leaned forward slightly, the dangling gems of her crown swaying. “Tradition has been a part of our culture as long as we can remember and cannot be thrown aside at the whims of a Terran. This is fact.”

“If I may,” Halesia said, her voice slipping into the conversation like warm water finding a gap between stones. She smiled at Niva with what looked like genuine friendliness. “House Patton-Avernell holds a charter from the Empress herself. It stands to reason that this house's preference of minimal ceremony is their specific culture. It would not look good upon any of our estates if we simply dismissed their approach.”

Niva's jaw shifted slightly. She sat back.

Siv exhaled through her nose. The verbal fencing had already begun and it took everything not to tremble from the adrenaline running through the Mistress Apprentice's system.

“My master wants the representatives to feel as safe and welcome as possible,” Siv continued, drawing their attention back. “He wants genuine conversation without the trappings of prestige, for the betterment of all estates here on Victory.”

“I have heard Lord Patton-Avernell's own words offering support to my estate,” Vedarat's voice was calm and matter-of-fact. He had not changed his posture at all.

“Words are worth only the sound they make,” Niva responded with a curl of her lip.

Steward Vedarat slowly turned to look at the other peer, holding her gaze. “Which he has carried out. His lord has submitted official paperwork to authorize House Devenek's participation in the Starbase upgrades.”

Niva's eyes narrowed, something calculating behind them, but she did not say anything more. The room was quiet for a moment.

Siv glanced briefly at Minaka, who had not moved, had not spoken, and appeared to be semi-focused on something outside the window rather than the meeting going on. There was nothing hostile in it, almost as if this conversation was not interesting to her.

Siv straightened slightly and moved to the next point.

“The ancient tradition of veehaneaset carries an expectation of gifts to begin the event, something that our Emissary maids made clear to my master could not be dispensed with.” There were some things that simply could not be dispensed with.

Niva's chin lifted.

Here we go, Siv thought.

“Iron Forge intends to defer such discussions at the moment.”

Everyone shifted uncomfortably. It took everything for the Mistress Apprentice not to say something. Niva was really pushing the boundary of what she would be allowed to get away with.

Siv kept her voice even. “Still, such things must be planned for, as allowing the insult of any estate or house is something my master will not permit.”

“My husband has prepared a donation of currency toward the upgrades of the starbase we were speaking of earlier,” Halesia said lightly, “to help defray the pressure that would put on House Patton-Avernell.”

Niva frowned and Vedarat straightened.

“Such a substantial gift for a project that one is not part of is...interesting,” Vedarat said with narrowed eyes.

“Peace, Steward,” Halesia said with a mischievous smile. “We donate it in the spirit of the veehaneaset with no expectation except as proof of House Nevakev's trust in Lord Patton-Avernell's leadership.”

The Mistress Apprentice wasn't sure if that helped or not. The politics was choking. How did Maevin handle all of this?

For the next two hours they pressed on with discussions of lodging, how many security personnel, what was expected of any honored maids, down to the mundane of how meals would be prepared and so forth. Even so, in the back of Siv's mind, she knew Minaka had not said anything, had not engaged in a single discussion point.

As they were wrapping up, the 1st Order Maid stood, drawing everyone's attention.

“Crystal Spring Estate of House Shova will not be participating in the veehaneaset.”

Her voice was low and even and carried no apology in it whatsoever. Minaka didn't bother to look at anyone but turned on her heel and left through the door she had come in. The silence she left behind lasted exactly two seconds.

“Well,” Niva's voice cut across the room like a blade finding a seam. “That is rather expected of House Shova, isn't it. They refuse to participate in anything that could put their precious knowledge at risk, even if it means insulting the ruling estate.”

Halesia's smile had gone carefully neutral. Vedarat had gone very still in the particular way of someone who was deciding whether this was his problem. Siv's heart was hammering. She could feel it at the base of her throat. Siv did not let herself swallow visibly. She kept her hands folded at her waist and her expression warm and in charge, completely at odds with the cold spiral happening behind her eyes.

“Please forgive the interruption,” she said, and was relieved to hear her own voice come out steady. “I wonder if I might impose on your patience a little longer. I believe Nish was preparing a second round of refreshments.”

As if summoned by the words themselves, Nish appeared in the doorway with a tray of small glazed pastries and a fresh pot of something that smelled of spice. The Arch Maid moved through the room with her particular brand of unhurried competence, setting the tray down and meeting Siv's eyes for only a fraction of a second.

The nod was so small it was barely a movement at all.

She heard Halesia begin to say something gracious to Nish as the door closed behind her.

---

The corridor outside was empty and cool, and Siv allowed herself exactly four fast steps of genuine panic before she locked it back down and broke into a purposeful stride toward the estate's front approach.

Minaka had not been hurrying. Siv caught sight of her just as the woman turned the far corner of the main corridor that led toward the outer courtyard and the shuttle landing pad beyond it. Her pace was measured; she moved like someone who had already finished a task and was simply in the process of leaving it behind.

“Peer Minaka,” Siv said, referencing that she was also a 1st Order Maid when not a Mistress Apprentice.

The woman stopped but did not turn immediately. There was a pause, brief but present, and then she turned on her heel and faced Siv with that still, unreadable expression.

Siv stopped a few paces away and kept her voice level.

“I would ask a few minutes of your time.”

Another pause. Then Minaka inclined her head. Not warmly. But she inclined it.

Siv chose her words with the same care she would choose footing on uncertain ground. “May I understand why you have refused my master's invitation? Did I not convey to you his sincerity, of safety, with no design upon you or the others?”

For a moment she thought Minaka might not answer, but she spoke. “He may speak of no design, but how can a human be trusted? Let alone any of those in that room. My estate and house are of history and of secrets. Every house has tried to vie for our favor or coerce us into obedience, to use what we know for their own gain. Why would this be any different?”

She said it without heat. That was somehow the most unsettling part.

“Lord Henry is not like that,” Siv said.

Minaka's expression shifted into something like amusement. “A Terran? Really? I would not have expected you to be so naive, Peer Siv.”

Siv stood very still for a moment. Then she made a decision. It was probably reckless. Maevin would have thought carefully about it for at least ten minutes before committing. Siv gave herself three seconds and moved.

“Come with me,” she said.

---

The southern garden was not the estate's most impressive space. That distinction belonged to the formal courtyard near the entrance with its sculpted hedges and fountain that caught the light at dawn in a way that made visitors stop walking. The southern garden was where things actually grew, vegetable beds, herb rows, the stubborn sprawling tangle of something that Burdak had been cultivating and refused to explain. It smelled of turned earth and something green and faintly sweet, and the evening light came through the trees at the garden's edge in long, low bars of amber.

Siv slowed as they approached the garden wall and held out a hand, briefly, to stop Minaka beside her. She positioned them at the corner where the wall's shadow was deep and the sightline through the garden gate was clear.

Lord Henry was on his knees in the third vegetable bed.

He had what appeared to be dirt on both forearms up to the elbow and was pulling weeds from the base of a row of something leafy with the focused enthusiasm of a man who had absolutely no intention of returning to his paperwork. Two maids worked nearby, one on each side of him, and the sound of their voices drifted across the garden in the evening air.

He was laughing. Something one of the maids had said had caught him entirely off guard and he had sat back on his heels and laughed with his whole face, with no performance in it whatsoever.

The maid was grinning, far too comfortable for someone working with a lord of an estate, but that was the point Siv was trying to make.

Henry said something back. Siv couldn't catch the words but she watched the maid laugh again. Henry went back to his weeding. He did not look up toward the wall. He had no idea anyone was watching.

Siv looked at Minaka. The woman was very still. Her scarred face was turned toward the garden and her expression had changed in some way that was difficult to name. The electronic eye moved, tracking slowly across the scene. The dark eye beside it had something in it that it hadn't had before. The silence stretched out between them, easy now in a way it had not been in the corridor.

After a long moment, Minaka exhaled through her nose. It was a small sound. Almost nothing.

“He has no idea anyone is watching him,” Minaka said quietly. It was not quite a question.

“No.”

Minaka was quiet for a long time. Down in the garden, Henry said something that made the maid cover her mouth with her dirt-covered hand, though she quickly composed herself, while Henry looked very pleased with himself.

Minaka watched this. She watched all of it.

Then she said, without looking away from the garden, “This one time.”

Siv turned her head.

“House Shova,” Minaka said, “will send a representative.”

She said it the way she had said everything else today, flat and even and without decoration. The weight on Siv's shoulders lifted and she almost took in a ragged breath.

“Thank you,” Siv said. She kept her voice just as quiet.

Minaka turned from the garden and straightened her shoulders. The scarred face was composed again, the moment tucked away somewhere Siv could not follow it.

“I will see myself to the landing pad,” she said.

Siv nodded and watched her go.

---

There was definitely a look of disbelief on everyone's face, especially Niva's, when Siv returned to inform them that House Shova would be participating. She did not go into detail, as it was time for everyone to leave.

The moon was shining bright as Siv looked over the belvedere wall, noting the maids returning in from their shift. She also noticed Abiva swatting the backside of a certain yellow-haired maid who had probably screwed up something yet again.

“I am impressed.”

Siv nearly came out of her skin at the cool voice beside her. Siv turned with a start to see Mistress Maevin standing there, looking out toward the woods in the distance.

“xikihanmaav,” Siv said with a quick bow. “I did not see you there.”

Maevin raised a hand to ward off the politeness and turned to look at the other girl. “House Shova has never accepted invitations. They have always sent a representative but never followed through.”

There was a glitter of curiosity in Maevin's eyes. “I would not have been confident that even I could have gotten them to agree. What did you do?”

Siv thought about it. Yes, she had gambled and it had paid off, but she had also exposed her master's private life in a way that could have been used against him. Siv would either be rewarded or tied to the pillar. So she lowered her head.

“You once told me that we must learn how to navigate things ourselves and to find ways of getting things done,” Siv said.

“Yes?”

“I have found a way.”

“You don't plan on telling me,” Maevin said with a hint of amusement and irritation.

“What sort of mistress would I be if I gave away my secrets?”

That did get a chuckle out of the imperious woman who ruled the estate with an iron fist.

“Go to bed, Siv. You've earned it.”

Yes. She had.

Something strange happened in late 2025. Engineers at Anthropic noticed that their AI agents were choking on their own capabilities. The more tools they connected, the worse their systems performed. A typical setup linking five common enterprise services (GitHub, Slack, Sentry, Grafana, and Splunk) consumed roughly 55,000 tokens just in tool definitions before the agent had even read a single user request. One internal deployment devoured 134,000 tokens on tool descriptions alone, leaving the model precious little room for actual reasoning. It was the software equivalent of filling a filing cabinet with instruction manuals and leaving no space for the files themselves.

The irony was exquisite. The Model Context Protocol, Anthropic's open standard for connecting AI agents to external systems, had succeeded beyond anyone's expectations. Launched in November 2024, MCP had grown from an internal experiment into the dominant integration standard for agentic AI, with over 10,000 active public MCP servers by late 2025 and adoption by ChatGPT, Cursor, Gemini, Microsoft Copilot, and Visual Studio Code. Official SDK downloads exceeded 97 million per month across Python and TypeScript. But this success created a paradox: the more tools agents could access, the less effective they became at using any of them.

The team's response, detailed in Anthropic's engineering blog post on advanced tool use, was not to limit tool access but to fundamentally rethink how agents discover and interact with their capabilities. The result was a trio of features that, working together, reduced context consumption by up to 85 per cent while simultaneously improving accuracy. And the design patterns they established are now reshaping how the entire industry thinks about building production agentic systems.

When Every Tool Costs You Tokens

To understand why the tool scaling problem became acute in 2025, you need to appreciate the economics of context windows. Every tool definition an agent loads carries a token cost. A modestly complex tool with a name, description, and parameter schema might consume 200 tokens. That seems trivial until you connect to a GitHub MCP server with 35 tools (roughly 26,000 tokens), a Slack server with 11 tools (21,000 tokens), and a handful of monitoring services. Suddenly, you have burned through tens of thousands of tokens before the conversation even begins.

Bin Wu, the primary author of Anthropic's advanced tool use engineering blog post and a former Airbnb engineer who joined Anthropic to work on AI safety, described the problem in stark terms. The traditional approach to tool management, loading all definitions upfront and passing them to the model, simply does not scale when developers are connecting agents to dozens or hundreds of MCP servers. Anthropic's internal testing revealed that tool selection accuracy degrades significantly once you exceed 30 to 50 available tools. The model gets overwhelmed by options, like a diner handed a 200-page menu when they just want breakfast.

This degradation is not merely anecdotal. Research on large language model tool calling has consistently demonstrated a negative correlation between tool library size and selection accuracy. The phenomenon has multiple causes. Context window saturation leaves less room for reasoning as tool definitions consume more space. The well-documented “lost in the middle” effect means models recall information at the beginning and end of their context windows more reliably than content buried in the middle, causing optimal tools to be overlooked when they appear amidst dozens of alternatives. And larger context windows alone do not solve the problem, because the core attention and selection accuracy issues persist regardless of how much space is available.

This problem has two distinct dimensions. The first is what engineers call “context bloat”: tool definitions consuming the finite token budget that the model needs for reasoning, user instructions, and conversation history. The second is “context pollution”: intermediate results from tool calls flooding the context window with data the model does not actually need. A two-hour sales meeting transcript routed through a workflow might mean processing an additional 50,000 tokens of audio transcription, even when the agent only needs a three-sentence summary.

As Adam Jones and Conor Kelly detailed in Anthropic's companion post on code execution with MCP, these two inefficiencies compound each other in production environments. An agent connected to thousands of tools must process hundreds of thousands of tokens in definitions before it even reads the user's request, and then each tool invocation potentially dumps thousands more tokens of intermediate results back into the context window. The practical ceiling is not the model's intelligence. It is the model's context budget.

The financial implications are equally pressing. Token usage translates directly into API costs. An enterprise running thousands of agent interactions daily can see its compute bills balloon when every request begins with 100,000 tokens of overhead. Latency suffers too: more input tokens mean longer processing times, which means slower responses, which means frustrated users and abandoned workflows. Before MCP, developers faced what Anthropic described as an “N by M” integration problem: ten AI applications and one hundred tools could require up to a thousand different integrations. MCP solved that problem elegantly, reducing it to a single protocol implementation on each side. But it introduced a new one: the protocol worked so well that developers connected everything, and the resulting token cost became unsustainable.

The Discovery Revolution

Anthropic's first intervention was the Tool Search Tool, a meta-capability that lets agents discover tools on demand rather than loading everything upfront. The concept is deceptively simple. Instead of passing all tool definitions to the model at the start of every conversation, developers mark tools with a defer_loading: true parameter. These deferred tools are not loaded into the model's context initially. The agent sees only the Tool Search Tool itself, plus a small set of frequently used tools that remain always-loaded. When the agent encounters a task requiring a specific capability, it searches for relevant tools, loads only the three to five it actually needs, and proceeds.

The token savings are dramatic. That five-server scenario consuming 55,000 tokens in definitions? With the Tool Search Tool, it drops to roughly 8,700 tokens, preserving 95 per cent of the context window. Across implementations, Anthropic documented an 85 per cent reduction in token usage while maintaining access to the full tool library. The system supports catalogues of up to 10,000 tools, returning three to five of the most relevant per search query.

But the real surprise was accuracy. Conventional wisdom suggested that reducing the number of visible tools would degrade performance, forcing the model to take an extra step to find what it needs. The opposite turned out to be true. By surfacing a focused set of relevant tools on demand, tool search actually improved selection accuracy, particularly with large tool libraries. Internal testing on MCP evaluation benchmarks showed Claude Opus 4 jumping from 49 per cent to 74 per cent accuracy, a 25 percentage-point improvement. Claude Opus 4.5 improved from 79.5 per cent to 88.1 per cent. The mechanism was straightforward: fewer options meant less confusion, and dynamically selected tools were more likely to be relevant to the actual task.

The Tool Search Tool supports multiple search strategies, each suited to different deployment needs. The regex-based variant, designated tool_search_tool_regex_20251119, uses Python's re.search() syntax and works well for keyword matching across tool names and descriptions. It supports exact matches, flexible patterns using wildcards, and case-insensitive searches with a maximum query length of 200 characters. The BM25-based variant, tool_search_tool_bm25_20251119, accepts natural language queries instead, using term-frequency ranking for more nuanced discovery. Both variants search tool names, descriptions, argument names, and argument descriptions. Custom embedding-based search offers a third option, enabling semantic matching that finds tools by meaning rather than exact terminology. Developers can implement whichever strategy suits their deployment, or combine them.

There is also a caching advantage that was not immediately obvious. Because deferred tools are not included in the initial prompt, the rest of the prompt remains stable across requests. This makes prompt caching significantly more effective, since the cacheable portion of the prompt does not change every time the tool set shifts. For high-volume deployments, this secondary optimisation can compound the primary token savings substantially.

Cloudflare arrived at a strikingly similar conclusion through independent research, publishing their findings under the banner of “Code Mode” in September 2025, roughly two months before Anthropic's November announcement. As Cloudflare's engineering team observed, with just two tools, search() and execute(), their server could provide access to the entire Cloudflare API over MCP while consuming only around 1,000 tokens. When new products were added, the same search and execute code paths discovered and called them automatically, with no new tool definitions and no new MCP servers required. The generated JavaScript runs in a secure, isolated V8 Worker sandbox with external network access blocked by default, and each execution receives its own Worker instance.

The convergence was striking. Two major technology companies, working independently, identified the same fundamental problem and arrived at architecturally similar solutions within weeks of each other, as noted in the Cloudflare Code Mode blog post. Cloudflare published on 26 September 2025; Anthropic followed on 4 November 2025. The posts reference each other, but these were clearly parallel discoveries driven by the same pressures: agents were scaling up, tool counts were exploding, and the old approach broke at this scale.

Writing Code Instead of Making Calls

The second major innovation was Programmatic Tool Calling, which addresses the context pollution problem rather than context bloat. Traditional tool calling works through a sequential loop: the agent requests a tool, the API returns the result, the result enters the model's context, and the agent decides what to do next. For simple workflows involving two or three tools, this is fine. For complex orchestration spanning 20 or more tool invocations, it becomes catastrophically expensive.

Consider a practical scenario: checking budget compliance across 20 team members. In the traditional approach, the agent calls a tool to retrieve each team member's spending, waits for the result, processes it in context, and calls the next tool. That is 20 round trips through the model, 20 sets of intermediate results flooding the context window, and 19 additional inference passes that each add latency and cost. Anthropic measured one such workflow consuming 43,588 tokens across all those sequential invocations.

Programmatic Tool Calling flips this model. Instead of requesting tools one at a time, the agent writes a Python script that orchestrates the entire workflow. The script runs in a sandboxed Code Execution environment, pausing when it needs results from external tools. When tool results return via the API, they are processed by the script rather than consumed by the model. The script handles loops, conditionals, error handling, and data filtering, and only the final aggregated output reaches the model's context window. In Anthropic's budget compliance example, the same workflow dropped from 43,588 to 27,297 tokens, a 37 per cent reduction on that single task. But the savings compound dramatically with complexity: one implementation documented by Adam Jones and Conor Kelly reduced token usage from 150,000 tokens to 2,000, a 98.7 per cent reduction.

The insight beneath this approach has a certain elegance. Large language models have been trained on billions of lines of real code. They are fluent in Python, JavaScript, and TypeScript. But JSON tool-calling schemas are synthetic constructs that barely appear in training data. Asking a model to orchestrate complex workflows through individual JSON function calls is like asking a concert pianist to play a symphony by pressing one key at a time and waiting for approval between each note. Programmatic Tool Calling lets the model compose the entire piece. Cloudflare's engineering team articulated the same observation independently: models are fluent in real programming languages but stutter when asked to produce function-call JSON, because they have seen millions of lines of actual code during training but only contrived tool-calling examples.

This idea did not appear in a vacuum. Joel Pobar's LLMVM project had been exploring code-based tool orchestration since before it was fashionable, allowing language models to interleave natural language and code rather than relying on traditional tool calling APIs. The project's design philosophy, that letting models write code generally results in significantly better task deconstruction and execution, prefigured the approach that both Anthropic and Cloudflare would later formalise. LLMVM uses a “continuation passing style” execution model, where queries result in natural language interleaved with code rather than a rigid sequence of code generation followed by natural language interpretation.

Anthropic's implementation requires tools to opt in to programmatic calling through an allowed_callers parameter, specifically allowed_callers: ["code_execution_20250825"]. This ensures that sensitive operations can be restricted to direct model invocation with user approval. The sandboxed execution environment provides resource limits and monitoring. Intermediate results stay within the execution environment by default, which also carries privacy benefits: the MCP client can tokenise personally identifiable information automatically, allowing real data to flow between systems while preventing the model from accessing raw PII.

On 17 February 2026, Anthropic moved Programmatic Tool Calling to general availability with the release of Claude Sonnet 4.6, signalling that the feature had graduated from experimental curiosity to production-ready infrastructure. Alongside this, web search and fetch tools gained automatic code-based filtering, cutting input tokens by 24 per cent while boosting BrowserComp accuracy from 33 per cent to 46 per cent. Joe Binder, VP of Product at GitHub, noted that Claude Sonnet 4.6 was “already excelling at complex code fixes, especially when searching across large codebases is essential.” The broader community followed suit: Block's Goose Agent added “code mode” MCP support, LiteLLM added native support across providers, and multiple open-source projects adopted the pattern.

Teaching By Example

The third feature in Anthropic's advanced tool use suite is Tool Use Examples, which addresses a subtler problem than context bloat or pollution: parameter specification errors. Even when an agent correctly identifies the right tool and calls it efficiently, it can still fail by passing malformed or incorrect parameters. JSON Schema definitions tell the model what parameters are available and their types, but they do not convey the conventions, correlations, and formatting expectations that distinguish a correct invocation from a technically valid but functionally broken one.

Consider a calendar scheduling API that accepts a date parameter. The schema specifies that the parameter is a string, but does it expect “2025-11-15”, “15/11/2025”, “November 15, 2025”, or “15 Nov 2025”? The schema might even specify a pattern, but more complex relationships between parameters, such as an “enddate” that must be after “startdate” or a “timezone” parameter that changes the interpretation of datetime values, remain invisible in the formal specification.

Tool Use Examples solve this by providing concrete usage patterns alongside schema definitions. Developers include an input_examples array with one to five examples demonstrating proper parameter formatting and usage patterns. These examples can show minimal parameter usage (just the required fields), partial parameter combinations (common optional parameter groupings), and full parameter specifications (every available option), giving the model a practical understanding of how the tool should actually be called. Anthropic recommends between one and five examples per tool, with each example addressing a different usage pattern.

The impact on accuracy is substantial. Anthropic's internal testing showed accuracy on complex parameter handling improving from 72 per cent to 90 per cent with the addition of Tool Use Examples. As the Setec Research analysis of these features noted, the improvement is particularly pronounced for APIs with ambiguous parameter relationships, where the schema alone does not capture the implicit rules governing which parameter combinations are valid. The feature addresses format conventions that JSON Schema cannot express, nested structure patterns that require demonstration rather than description, and the implicit correlations between optional parameters that experienced developers understand intuitively but struggle to formalise.

This is not a novel pedagogical insight. It is the same principle that makes code documentation more useful when it includes examples alongside API reference descriptions. Developers have long understood that showing is more effective than telling. Tool Use Examples apply this principle to the model-tool interface, giving the agent worked examples rather than abstract specifications.

The three features are designed to work together as a complementary system. Tool Search Tool reduces upfront context consumption by loading tools on demand. Programmatic Tool Calling reduces runtime context pollution by keeping intermediate results out of the model's context. Tool Use Examples reduce errors by teaching the model how to use tools correctly through demonstration rather than description alone. Together, they address the full lifecycle of what Anthropic calls “context pollution in MCP-connected agents,” as described in their advanced tool use documentation.

Scaling MCP Without Breaking the Bank

The practical challenge for enterprises is not adopting any single optimisation technique. It is managing the operational complexity of hundreds or thousands of MCP-connected tools while maintaining the progressive disclosure principles that keep agents efficient. This requires architectural thinking beyond individual feature adoption.

The recommended pattern follows what might be called layered tool management. At the first layer, a small set of three to five frequently used tools remains always-loaded with defer_loading: false. These are the tools the agent will need in nearly every interaction: perhaps a file search tool, a messaging tool, and a general-purpose retrieval tool. At the second layer, entire MCP servers can be deferred with a default_config that sets defer_loading: true across all their tools, with selective exceptions for high-use capabilities within those servers. The example Anthropic provides is a Google Drive MCP server where all tools are deferred except search_files, which remains loaded because it is the most commonly needed entry point.

This progressive disclosure architecture mirrors a principle well-established in user interface design: show users what they need now, and make everything else discoverable. The difference is that here, the “user” is an AI agent, and the cost of poor disclosure is not confusion but wasted tokens and degraded performance.

For organisations operating at genuine scale, with dozens of MCP servers and hundreds of tools, the filesystem-based discovery pattern described in Anthropic's code execution with MCP post offers an alternative architecture. Rather than registering every tool with the API upfront, tools are presented as code files on a filesystem, organised into directories by server. A TypeScript file tree might include paths like servers/google-drive/getDocument.ts and servers/salesforce/updateRecord.ts. The agent explores the filesystem to find relevant tool definitions, reading them on demand. A search_tools utility allows the agent to query for relevant definitions with configurable detail levels: name only, name plus description, or full schemas with parameters. This approach scales elegantly because adding new tools means adding new files, not modifying configuration or redeploying infrastructure.

The governance dimension is equally important. In December 2025, Anthropic donated MCP to the Agentic AI Foundation, a directed fund under the Linux Foundation co-founded by Anthropic, Block, and OpenAI with support from Google, Microsoft, Amazon Web Services, Cloudflare, and Bloomberg. Mike Krieger, Chief Product Officer at Anthropic, explained that MCP had started as an internal project and had become “the industry standard for connecting AI systems to data and tools.” The donation was designed to ensure the protocol “stays open, neutral, and community-driven as it becomes critical infrastructure for AI.” Jim Zemlin, executive director of the Linux Foundation, framed the goal as avoiding a future of “closed wall” proprietary stacks where tool connections, agent behaviour, and orchestration are locked behind a handful of platforms. Platinum members of the new foundation include Amazon, Anthropic, Block, Bloomberg, Cloudflare, Google, Microsoft, and OpenAI, with Gold members including Cisco, Datadog, Docker, IBM, JetBrains, and Oracle among others. This institutional backing means enterprises can invest in MCP-based architectures with reasonable confidence in the standard's longevity and neutrality.

Measuring What Matters

Building efficient agentic systems is one problem. Knowing whether they actually work is another entirely. The evaluation methodologies for tool-using agents are still maturing, but several frameworks have emerged from both Anthropic's internal testing and broader industry practice.

The first and most obvious metric is token efficiency: how many tokens does the agent consume per task, and how does this change as the tool library grows? Anthropic's benchmarks provide useful baselines. A five-server MCP deployment consuming 55,000 tokens in definitions with traditional loading should drop to roughly 8,700 tokens with Tool Search, a reduction that should hold proportionally as the tool count increases. Programmatic Tool Calling should yield additional reductions of 37 per cent or more on multi-step workflows, with higher savings on more complex orchestrations.

But token efficiency alone is insufficient. The more meaningful measure is task accuracy, specifically the rate at which agents select the correct tool, invoke it with proper parameters, and produce the intended outcome. Anthropic's MCP evaluation benchmarks provide one framework for this, measuring tool selection accuracy across varying library sizes. The jumps from 49 to 74 per cent (Opus 4) and from 79.5 to 88.1 per cent (Opus 4.5) with Tool Search enabled demonstrate that efficiency and accuracy can improve simultaneously, rather than trading off against each other.

For Programmatic Tool Calling, Anthropic measured knowledge retrieval accuracy improving from 25.6 per cent to 28.5 per cent, and GIA (General Instruction Adherence) benchmarks rising from 46.5 per cent to 51.2 per cent. These gains are more modest than the tool selection improvements, reflecting the fact that code-based orchestration primarily addresses efficiency rather than capability. But in production systems, small accuracy improvements compound across thousands of daily interactions.

A rigorous evaluation framework should track at least four dimensions. First, context efficiency: tokens consumed per task, broken down by tool definitions, intermediate results, and model reasoning. Second, tool selection precision: the rate at which the agent identifies the correct tool for a given subtask, measured against a labelled test set of tasks and expected tool selections. Third, parameter accuracy: the rate at which tool invocations include correct, complete, and properly formatted parameters. And fourth, end-to-end task completion: whether the overall workflow produces the correct final output, regardless of intermediate steps.

The bottleneck identification process follows naturally from these metrics. If context efficiency is poor but tool selection is accurate, the problem is in loading strategy, and Tool Search is the appropriate intervention. If tool selection degrades with library size, the search implementation needs refinement, perhaps moving from regex-based to embedding-based retrieval. If parameter errors dominate, Tool Use Examples should be expanded. If end-to-end completion lags despite good individual metrics, the orchestration logic, whether sequential or programmatic, likely needs restructuring.

Latency deserves its own evaluation track. Programmatic Tool Calling eliminates the multiple round trips inherent in sequential tool invocation, which should reduce end-to-end latency for complex workflows. But it introduces the overhead of code execution environments. Measuring wall-clock time per task, alongside token counts, reveals whether the computational overhead of sandboxed execution outweighs the savings from fewer inference passes. In Anthropic's testing, a workflow requiring 19 or more sequential inference passes collapsed into a single programmatic execution, a latency reduction that far exceeded any overhead from the sandbox.

Researchers have also proposed broader reliability frameworks for evaluating agentic systems. A 2025 study outlined twelve concrete metrics decomposing agent reliability along four key dimensions: consistency, robustness, predictability, and safety. The findings were sobering. Evaluating 14 agentic models across two complementary benchmarks, the researchers found that recent capability gains had yielded only small improvements in reliability, suggesting that making agents more capable does not automatically make them more dependable. This gap between capability and reliability underscores the importance of dedicated evaluation infrastructure that measures not just whether agents can do things, but whether they do them consistently and safely.

Design Patterns for the Production Frontier

The engineering patterns emerging from these developments suggest a maturation of agentic system architecture. Several design principles have crystallised from both Anthropic's work and the broader community's experience.

The first is what Anthropic calls the “layered approach”: address the highest bottleneck first. If tool definitions consume most of your token budget, start with Tool Search. If intermediate results dominate, implement Programmatic Tool Calling. If parameter errors cause most failures, add Tool Use Examples. This triage prevents premature optimisation and ensures that engineering effort targets the actual constraint.

The second pattern is parallel execution through code orchestration. When multiple tool calls are independent, they should execute concurrently rather than sequentially. Anthropic's documentation references asyncio.gather() for independent operations within programmatic tool calls. This pattern does not reduce token consumption, but it dramatically reduces latency for workflows involving multiple independent data retrievals.

The third pattern involves explicit return format documentation. When tools are called programmatically, the agent's code needs to parse tool outputs reliably. Anthropic recommends explicitly specifying tool output structures in tool descriptions, so the code the model writes can accurately reference fields and formats in the returned data. Without this, the model may generate code that assumes incorrect output structures, leading to runtime failures in the sandbox.

The fourth pattern addresses security and privacy boundaries. Programmatic Tool Calling introduces a new trust surface: the agent is now writing and executing code, not just making predefined function calls. The allowed_callers parameter provides opt-in control, ensuring that sensitive tools (those that modify data, access credentials, or perform irreversible actions) can be restricted to direct model invocation with explicit user approval. Cloudflare's approach adds another layer: bindings that provide pre-authorised client interfaces, ensuring that AI-generated code cannot possibly leak API keys because the keys never enter the execution environment. The binding provides an already-authorised client interface to the MCP server, and all calls made on it pass through the agent supervisor first, which holds the access tokens and injects them into outbound requests.

The fifth pattern concerns state persistence across operations. As described in Anthropic's MCP code execution documentation, agents can maintain filesystem state across operations, enabling resumption of interrupted workflows and the development of reusable functions as “skills” that persist between sessions. This transforms agents from stateless request processors into stateful systems capable of learning and adaptation within their operational context.

For enterprises evaluating these patterns, the critical implementation question is infrastructure. Code execution demands secure execution environments with appropriate sandboxing, resource limits, and monitoring. These add operational overhead compared to direct tool calls. Anthropic's managed implementation handles container management, code execution, and secure tool invocation communication, but organisations with strict data residency or compliance requirements may need to build or adapt their own execution environments. Cloudflare's approach, using Durable Objects as stateful micro-servers with their own SQL databases and WebSocket connections, offers one model for self-hosted execution, deploying once and scaling across a global network to tens of millions of instances.

The broader trajectory is unmistakable. The agent ecosystem is moving away from the “give the model everything and let it figure it out” approach that characterised early tool-using agents. In its place, a more disciplined architecture is emerging: one that treats context as a scarce resource, applies progressive disclosure to manage complexity, and uses code execution to keep intermediate processing out of the model's reasoning space. This is not merely an efficiency optimisation. It is a fundamental shift in how we think about the boundary between what the model does and what the surrounding system does.

As the MCP ecosystem continues to expand under the governance of the Agentic AI Foundation, and as tool counts scale from hundreds to thousands, the organisations that thrive will be those that master this boundary. They will build agents that know how to find the right tool without seeing every tool, that orchestrate complex workflows through code rather than conversation, and that learn from examples rather than struggling with abstract schemas. The 85 per cent context reduction is not the end state. It is the beginning of an entirely new way of building intelligent systems.

References and Sources

1. Wu, Bin. “Introducing Advanced Tool Use on the Claude Developer Platform.” Anthropic Engineering Blog, November 2025. https://www.anthropic.com/engineering/advanced-tool-use

2. Jones, Adam and Kelly, Conor. “Code Execution with MCP.” Anthropic Engineering Blog, November 2025. https://www.anthropic.com/engineering/code-execution-with-mcp

3. Wolenitz, Alon. “Advanced Tool Use in Claude API: Three New Features That Change A Lot.” Setec Research Claude Blog, November 2025. https://claude-blog.setec.rs/blog/advanced-tool-use-claude-api

4. Cloudflare Engineering. “Code Mode: Give Agents an Entire API in 1,000 Tokens.” Cloudflare Blog, September 2025. https://blog.cloudflare.com/code-mode-mcp/

5. Anthropic. “Introducing the Model Context Protocol.” Anthropic News, November 2024. https://www.anthropic.com/news/model-context-protocol

6. Anthropic. “Donating the Model Context Protocol and Establishing the Agentic AI Foundation.” Anthropic News, December 2025. https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation

7. Linux Foundation. “Linux Foundation Announces the Formation of the Agentic AI Foundation (AAIF).” Linux Foundation Press Release, December 2025. https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-agentic-ai-foundation

8. Anthropic. “Introducing Claude Sonnet 4.6.” Anthropic News, February 2026. https://www.anthropic.com/news/claude-sonnet-4-6

9. Pobar, Joel. “LLMVM: LLM Python Agentic Runtime Prototype.” GitHub Repository. https://github.com/9600dev/llmvm

10. Model Context Protocol Specification, Version 2025-11-25. https://modelcontextprotocol.io/specification/2025-11-25

11. Pento AI. “A Year of MCP: From Internal Experiment to Industry Standard.” Pento Blog, 2025. https://www.pento.ai/blog/a-year-of-mcp-2025-review

12. Claude API Documentation. “Tool Search Tool.” Anthropic Developer Platform. https://platform.claude.com/docs/en/agents-and-tools/tool-use/tool-search-tool

13. Claude API Documentation. “Programmatic Tool Calling.” Anthropic Developer Platform. https://platform.claude.com/docs/en/agents-and-tools/tool-use/programmatic-tool-calling

---

Tim Green UK-based Systems Theorist & Independent Technology Writer

Tim explores the intersections of artificial intelligence, decentralised cognition, and posthuman ethics. His work, published at smarterarticles.co.uk, challenges dominant narratives of technological progress while proposing interdisciplinary frameworks for collective intelligence and digital stewardship.

His writing has been featured on Ground News and shared by independent researchers across both academic and technological communities.

ORCID: 0009-0002-0156-9795 Email: tim@smarterarticles.co.uk

Managers and organizations want to know exactly when features, bug fixes, and other work will be done. Many have not been software engineers themselves, so they ask for exact dates. Sure, you can be off by a day or two—maybe!—but more than that, and it's a problem. After all, their boss needs to know what to promise customers. What's so hard about knowing when you'll be done?

Sadly, software cannot be estimated that way, and we need to stop pretending otherwise. It's a myth—a pervasive one—and perpetuating that myth only perpetuates its harm.

Sure, if a task is almost identical to some previous task, a precise and reliable estimate really can be communicated. Unfortunately, that almost never happens. If the work ahead were so similar, someone would have done it already using copy and paste. If it's similar and the engineering team wanted to set themselves up for success later, they'd refactor the system, but that refactoring itself can be a hazy fog of unknowns. We've all been there many times.

The problem

I once worked with someone who liked to compare software development to parcel delivery: choose a day when the package is expected to arrive. It's okay if there needs to be a delay, as long as that delay is communicated clearly. While the flexibility with delays was genuinely appreciated, the broader analogy soured on me over time. In truth, estimating software is nothing like estimating package delivery. The former involves doing something that has never been done before, while the latter is completed billions of times each year. Does Amazon have an advantage when forming estimates? You'd better believe it.

Software development is one of the only professions where we are asked to accurately state how long it will take us to do something that has never been done before in the history of the universe.

—Unknown, from a screenshot on X

How long will it take for Amazon to deliver a board game to Zara in Cincinnati? Well, probably about as long as it took last time. Yes, every delivery is different, but there must be millions of deliveries of similar items to nearby locations with similar weather forecasts and other pertinent factors being similar or identical. How long will it take? Probably that long.

By contrast, how much time will be required for me to change code I've never seen? I truly have no idea. How about adding, say, karaoke support to a streaming music app, one with millions of lines of code I've never read, where myriad caveats exist for different software clients, different spoken languages, and different copyright laws. How long will that take? Except in extremely broad terms, your guess is as good as mine. It will take more than one week, and it can probably be completed in less than one year. Beyond that, there's not much more that can be promised, at least in the beginning. More on that in the next section.

No, estimating software development is nothing like estimating like parcel delivery. It's more like estimating the pace of scientific progress. We simply don't know what we don't know. We can't know until we do it.

As much as possible, organizations should communicate that software will be ready when it’s ready. If some software must be released by a certain date, the feature list should not be guaranteed. I know this is easier said than done, believe me, but reality is what it is. Software simply cannot be estimated the way organizations imagine. Some higher-ups, especially those who have not been software engineers, may find this outrageous. They may demand exact estimates regardless. To them, I would say, “Fine, but let’s be honest, how’s that working for ya? How often are you given estimates that actually turn out to be correct?”

There's a reason you're reading this blog post. Something isn't working, and it's not about discipline. It's not about communication. It's not about skill. You're on the wrong path. Skeletons and vultures surround you. It's time to turn around.

Thankfully, there is a better way. Your manager may not like it at first, but over time, they may come to see that estimates of this type are actually useful, unlike the estimates they are accustomed to.

The solution

To explain this kind of estimation, I need to define two terms. First, I'm using the term accurate to describe any estimate that is correct within a given range of dates. Defined this way, even a very broad estimate can be accurate. For example, an estimate that a feature will be completed some time between March 1^st and December 31^st would be accurate, as long as it turns out to be true. Precision is another matter. That feature estimate isn't very precise, but it would be more precise if it predicted a completion date between, say, April 1^st and July 1^st. This is how Rapid Development defines the terms, and I think it’s a good approach. In fact, most of this advice is lifted from Rapid Development. I recommend reading it. It's a tome, so focus on the sections that are most pertinent to your needs.

Crucially, estimates can and should become more precise as time goes on and details become more clear. If a team begins with an estimate of some time in Q1 or Q2, but the feature is more difficult than expected and they realize they need to revisit the database schema, perhaps the estimate could be narrowed to some time between May 1^st and June 15^th. If the team is nearing the end and the final code reviews go more smoothly than expected, maybe the estimate could narrow to some time between May 16^th and May 31^st. If a critical issue is found elsewhere in the codebase, taking the team off the feature for a while, maybe May 29^th becomes the most likely date of completion. The point is, there's no way to predict those problems in advance, but they can inform better estimates over time, as long as the estimation method supports that. Did you instead randomly pick a day three months in advance? Too bad. You're screwed.

Reality-driven estimation

So how should we estimate? Strive for accuracy, start with low precision, and seek greater precision over time. As another example, you might consider communicating a project end date some time between Q2 and Q4, then later refine that to some time in the fall, then some time in October. Finally, at the very end of the project, you might be able to promise a specific week or even a specific day. That is an approach to estimation which acknowledges reality. That is an approach to estimation which acknowledges that surprises happen.

Do organizations want to hear this? Unfortunately, no, I don't think so. It's a tough sell. Organizations want certainty, and they want it now. Good luck telling your boss that you don’t know exactly how much time and money you're going to spend. Even the project management apps we use typically require that an estimate be recorded as a specific date. Talk about encouraging bad practices.

Pushing back is hard, and as someone who was raised to never question authority, even when that authority is obviously wrong, I happen to be particularly bad at it. That's too bad. Our bosses pay the bills, but we do the work. It's time we start saying, “The work can't be done that way, and if I were to tell you otherwise, I'd be lying to you.”

Reality is what it is, and the best we can do is provide estimates with gradually improving precision. Organizations can pretend otherwise, and countless surely will, but again, I would ask, “how's that going?” Organizations ignore these facts to their own detriment, at the cost of time, money, and frustration. I wish them luck.

For everyone else, consider embracing reality. It's not perfect, but it's the best we can do.

#Life #Quotes #SoftwareDevelopment #Tech

#002307 – 22 de Setembro de 2025

O argumento dos doomers, sobre o perigo de uma superinteligência artificial que, por um ou outro motivo leva à nossa extinção não é simplesmente uma visão pessimista sobre um tipo específico de tecnologia. Muitos destes hiperpessimistas vêm do movimento e filosofia altruísmo eficaz, quase uma consequência inevitável de se levar (como Peter Singer) a lógica do utilitarismo até às últimas consequências. Para os proponentes do EA (a sigla geralmente usada para referir o Effective altruism), deve-se maximizar o bem que se faz pelos outros e, por isso, a única opção ética é concentrarmo-nos nas acções e causas que beneficiem mais pessoas durante mais tempo. É daqui que emerge a obsessão com o apocalipse trazido por uma inteligência artificial. Sendo o dano máximo (a extinção da espécie humana), prevenir este resultado nefasto é logicamente mais importante que qualquer outra causa. Mesmo sendo a probabilidade de acontecer relativamente pequena, prevenir que suceda traz o máximo de bem (salvar a vida) ao máximo de pessoas possível (a humanidade inteira).

O que é curioso é que os boomers (que defendem a expansão da tecnologia com a máxima rapidez e urgência) usam a mesma lógica. Mesmo não havendo certeza de que seja possível produzir uma super inteligência artificial, os benefícios (curar o cancro e outras doenças, resolver as alterações climáticas, acabar com as guerras e com a fome) são imensos, basicamente resolver todos os problemas humanos. Por isso, segundo os princípios ultra-utilitários do EA, nenhuma outra causa é tão importante como fazer emergir essa mega-entidade digital. Porquê gastar recursos a melhorar os problemas ambientais, ou aliviar a fome, ou investir esforços diplomáticos para acabar com conflitos, se uma superinteligência artificial resolveria todos esses problemas.

O que um e outro campo parecem professar não é, como dizem o uso da razão, mas uma nova forma de religião. E estão em desacordo simplesmente no método: uns querem impedir que o diabo venha ao mundo e os outros querem invocar a vinda de deus. Usam argumentos lógicos para defender que deixemos de cuidar uns dos outros, das nossas sociedades e do planeta, porque partem de um pressuposto que paira sobre mas não se baseia no estado actual da ciência informática. Ora aqui vai um outro argumento: mesmo que fosse verdade que vem aí um deus ou um diabo digital, devemos cuidar uns dos outros, apenas porque isso determina como construímos as sociedades, as relações humanas e a própria tecnologia. Não devemos colocar nas mãos da tecnologia nenhuma decisão de vida ou morte (como agora se faz com as armas autónomas). O altruísmo poderá ter mesmo uma base bio-evolutiva, os comportamentos pró-sociais beneficiam também quem o pratica e são mais do que a soma de todos os benefícios gerados. São a própria coesão das nossas sociedades, das nossas famílias, da humanidade. Devemos resistir a tentação de industrializar até o altruísmo.

“Se estamos destinados a ser, eu te vejo mais tarde.”

俺はラジオが好きで、文章を読むのはあまり得意じゃない。 でも、つまらない話を聞くのは苦手だ。 要するに、自分がインプットを許せるのは「面白い話を耳で聞くこと」だけ。 音楽を聴くのも好き。

製品マニュアルのような文章を読んで理解することはできる。 ただ、最近はAIに聞いて読む量を最低限にしているから、「文章が好きか」と問われると、正直そうとは言いづらい。

仮に資格の勉強をするとする。 eラーニングをただ流しているだけでは、まったく頭に入る気がしない。 自分が一番関心を持てるのは「面白い話を耳で聞くこと」だから、本当は勉強もそういう媒体で学びたい。 けれど、面白い話と学問はなかなか両立しない。 面白い話を聞きたい時には、学問や知識はできるだけ排除したい。 そう考えると、両立はやはり難しい。

では、どうするか。 「面白い話」のグルーヴ感を、自分の勉強内容に置き換えてみるのはどうだろう。 つまり、学ぶ内容を自分で声に出して読み、耳で聞くことで覚える方法だ。

自分で喋れるようになれば、その分野を体得したことになる。 学習のとき、自分が好きなように喋って、その声を自分で聞いて「ちょっと楽しい」と思えれば、自然と身につく。 これが一番効率のいい方法なんじゃないかと思う。

ただ、今は会社にいて、周りには人が多い。 声に出して勉強するのは、まるで演目みたいで迷惑だし、何より恥ずかしい。 ふと、外で演説やプレゼンをしている人は、どこで練習しているんだろうと考えた。

インプット方法をいろいろ考えた末に「これしかない」となるのは、思った以上に厳しい。 パソコンにポートが1つしかなく、しかもマニアックな端子でしか刺さらない、みたいな状況だ。

社会人で表に立つ人たちのことを思うと、普段何をしているのかよく分からない。 それを今になって気にしている自分は、やっぱり鈍いというか、無関心な部分もあるんだろうと思いながら、結局コーヒーを飲む。 その一口で、なぜか問題が解決したような、大きな句点が頭の中にぽんと浮かんだ。

In Summary: * Having a Monday that is both productive and enjoyable sets a tone for the rest of the week, don't you think? I think it does. And this Monday in the Roscoe-verse qualifies on both counts. Doing my weekly laundry today, all of it, and having it all folded and put away, I count that as being acceptably productive. And listening to my Texas Rangers win their game today vs the San Diego Padres ranks right up there on the enjoyability scale. So... I'm ready now for the rest of the week. Heh.

Prayers, etc.: * I have a daily prayer regimen I try to follow throughout the day from early morning, as soon as I roll out of bed, until head hits pillow at night. Details of that regimen are linked to my link tree, which is linked to my profile page here.

Starting Ash Wednesday, 2026, I've added this daily prayer as part of the Prayer Crusade Preceding the 2026 SSPX Episcopal Consecrations.

Health Metrics: * bw= 231.60 lbs. * bp= 146/87 (70)

Exercise: * morning stretches, balance exercises, kegel pelvic floor exercises, half squats, calf raises, wall push-ups

Diet: * 05:40 – 1 banana * 06:30 – 1 ham & cheese sandwich * 10:20 – rice cake * 11:00 – fresh papaya * 12:50 – bowl of cooked meat and saltine crackers * 17:00 – 1 fresh apple

Activities, Chores, etc.: * 04:30 – listen to local news talk radio * 05:15 – bank accounts activity monitored * 05:50 – read, write, pray, follow news reports from various sources, surf the socials, and nap * 09:50 – start my weekly laundry * 12:50 to 13:50 – watch old game shows and eat lunch at home with Sylvia * 14:40 – folding laundry * 15:00 – listening to an MLB Spring Training Game, the San Diego Padres vs my Texas Rangers * 17:45 – and the Rangers win, 4 to 1.

Chess: * 14:35 – moved in all pending CC games

Under a patch of undergrowth, once a fistful of perfect golden chanterelles lay hidden. I didn’t see them until I did, I was the first human who did I think, and I felt their weight and a special type primal hunther/gatherer satisfaction as I put them in this paper bag I brought

Or maybe it was plastic

But the memory of the hidden treasure is strong with the sun sending playful somewhat blinding rays on the surface of the water with was fringed by this greenery.

When I — by accident as I was browsing — found that Katherine Kerr had started writing a new series set in the same Deverry world, and bought the first one of these books, I felt just a similar type of joy.

I made the connexion because these occurrences were only days apart if it wasn’t on the same day in fact? It doesn’t matter

And it was a pleasure to visit this world again

When I started I took great pleasure in having a series of twelve (then later sixteen) books with this world but I read them all eventually and then of course to see it again was like they say like visiting an old friend, you know. It doesn’t take long until it’s just like it was before — just like it was supposed to be

You know?

#002306 – 21 de Setembro de 2025

A música, em muitas situações, é um fio condutor à sanidade.

#002305 – 20 de Setembro de 2025

Kat Abughazaleh no meu ecrã, à procura do melhor remédio.

There is a quiet tragedy that unfolds every day in the lives of people who began with pure intentions. It does not usually happen loudly. It rarely announces itself with flashing warning signs or dramatic collapse. Instead, it creeps in slowly through long workdays, ambitious goals, spreadsheets, marketing strategies, deadlines, and the relentless pressure to make something succeed. A Christian entrepreneur may begin their journey kneeling in prayer, dedicating their dream to God, asking Him to bless the work of their hands, and promising that everything they build will be for His glory. But somewhere along the road between inspiration and expansion, something subtle can shift within the heart. The dream that once felt like a calling can slowly become a machine that demands constant feeding, and the One who inspired the vision can begin to fade quietly into the background. The business still carries Christian language, Christian branding, Christian mission statements, and perhaps even Bible verses on the office wall, but the daily decisions that determine the direction of the enterprise are no longer flowing from the same place of surrender that existed in the beginning.

This is not usually done with malicious intent. In fact, it often happens to the most sincere believers. People who love God deeply and who genuinely want to serve Him can slowly become consumed by the responsibilities of building something that requires endless attention. The demands of leadership have a way of filling every available space in a person's mind, and the urgency of business decisions can begin to drown out the quieter voice of spiritual guidance. Many Christian entrepreneurs wake up one day and realize they are exhausted, spiritually dry, and wondering why something that once felt alive now feels strangely hollow. The numbers might still be moving. The company may still be operating. Customers may still be buying the product or using the service. But inside, the builder feels disconnected from the very reason the structure was started in the first place. This is the moment when many people assume the problem must be marketing, strategy, pricing, or market conditions. They search for a better system or a new tactic, unaware that the deeper issue lies somewhere far more foundational than any business plan could ever address.

Scripture quietly reveals a principle that applies to every endeavor a person builds in this world. The Psalmist wrote that unless the Lord builds the house, the builders labor in vain. That statement is not merely poetic language meant to inspire reflection. It is a spiritual law that operates beneath the surface of every human effort. When a person sets out to construct something meaningful, whether it is a family, a ministry, or a business, the strength of that structure ultimately depends on the foundation beneath it. A house built on sand can appear stable for a long time. The walls may be straight, the roof may be strong, and the interior may even look impressive. Yet the unseen weakness beneath the structure guarantees that when storms arrive, the collapse will be inevitable. Jesus described this principle in one of His most famous teachings when He spoke about two builders who constructed their houses in very different ways. One built on rock and the other built on sand, and the difference between them was not visible on calm days. The difference only became obvious when the winds rose and the rain began to fall.

Christian businesses often begin their journey on the Rock, but over time the builder can slowly drift into constructing additional layers on something far less stable. The pressure to succeed can quietly push a person toward relying more heavily on personal intelligence, networking ability, marketing creativity, and financial resources. None of those things are inherently wrong, but they become dangerous when they begin to replace the deeper reliance on God that once defined the mission. A Christian entrepreneur can unknowingly begin operating as though the success of the company ultimately depends on their own effort, their own planning, and their own ability to outwork every obstacle. This shift in perspective rarely feels rebellious. In fact, it often feels responsible. After all, business owners are taught that success requires discipline, planning, and relentless work. But the spiritual danger lies in the subtle transformation that occurs when a calling slowly becomes a personal burden instead of a shared partnership with God.

Many believers reach a point in their business journey where they begin to sense that something is not right. The joy that once accompanied the work has faded. Prayer becomes shorter and less frequent. Time in Scripture feels rushed or postponed because there is always another urgent task demanding attention. The heart that once burned with purpose now feels tired, and the business that was meant to serve as a vessel for faith now feels like a weight pressing down on the soul. This is often the moment when entrepreneurs begin searching for solutions in the wrong places. They attend conferences, purchase new training programs, hire consultants, redesign their brand, and experiment with new marketing strategies. Some of those efforts may produce temporary improvement, but they rarely address the root issue that is quietly weakening the entire structure. The problem is not usually a lack of intelligence or effort. The deeper issue is that somewhere along the journey, the builder forgot who the business truly belongs to.

There is a profound difference between building something for God and building something with God. When people begin their journey with the desire to honor Him, they often imagine themselves constructing something impressive that they will eventually present back to Him as an offering. The intention is sincere, but the mindset can subtly position the entrepreneur as the primary architect of the enterprise. Over time, the builder begins carrying the emotional weight of every outcome, every failure, every financial challenge, and every unexpected obstacle. The pressure grows heavier because the responsibility feels entirely personal. But when a person remembers that God was never meant to be a distant beneficiary of the work, the entire perspective begins to shift. The business was never meant to be an offering constructed independently by human hands. It was always meant to be a partnership where the Creator Himself remains the true builder.

Jesus once told His followers that apart from Him they could do nothing. That statement challenges the deeply ingrained cultural belief that success is primarily the result of human effort. Modern business culture celebrates independence, self-reliance, and personal ambition. Entrepreneurs are often praised for their ability to take control of their destiny and shape their own future through determination and discipline. While those qualities can certainly contribute to achievement, they can also create the illusion that God’s role is limited to providing inspiration while humans handle the real work. The Kingdom of God operates on an entirely different principle. In God’s design, human effort is never meant to replace divine guidance. Instead, it becomes powerful only when it flows from a life that remains deeply connected to Him.

One of the most dangerous moments in the life of a Christian business owner is the moment when success begins to appear. Growth can be far more spiritually risky than failure because it quietly reinforces the belief that the current approach is working. When revenue increases, when recognition grows, and when customers begin praising the value of the product or service, it becomes easier to believe that the system itself is responsible for the results. The entrepreneur may still pray and still speak openly about faith, but the heart can gradually shift toward trusting the structure that has already been built. The danger is not visible immediately because the business may continue thriving for months or even years. Yet beneath the surface, the foundation is slowly becoming disconnected from the Rock that once supported everything.

Eventually the storm arrives. In business, storms can take many forms. Economic downturns can suddenly shrink markets that once seemed stable. Unexpected competition can appear and begin eroding customer loyalty. Internal leadership challenges can disrupt the harmony of a growing team. Personal exhaustion can drain the clarity that once fueled innovation. Sometimes the storm arrives as a quiet sense of spiritual emptiness that cannot be explained by financial numbers or external circumstances. The entrepreneur looks around at the business they worked so hard to build and realizes that something essential is missing. It is at this moment that many Christian entrepreneurs discover a painful truth. The real crisis is not external at all. The real crisis is that the builder slowly drifted away from the One who was meant to be guiding the entire project.

Yet this moment of realization can also become the beginning of something far more powerful than the original vision. When a person recognizes that their foundation has shifted, they are given the opportunity to return to the Rock with deeper humility and clearer understanding than they possessed at the beginning. The rebuilding process does not necessarily mean abandoning the business or starting from scratch. In many cases it means something far more transformative. It means reorienting every decision, every strategy, every ambition, and every measure of success around the presence of Jesus Christ as the true center of the work. It means remembering that the purpose of the enterprise was never simply to generate profit or recognition. The deeper purpose was always to create a vessel through which God’s presence could touch the lives of people who might never step inside a church.

Christian businesses have the potential to become extraordinary instruments of influence in the world. A company led by someone who walks closely with God can create environments where integrity is honored, where employees are treated with genuine dignity, where customers encounter honesty instead of manipulation, and where generosity flows naturally instead of being calculated for public relations. These businesses can quietly reflect the character of Christ in industries that often operate on entirely different values. But this kind of influence only emerges when the builder remains deeply connected to the Source of the vision. When Jesus remains the foundation, the business becomes something far greater than a commercial operation. It becomes a living testimony that faith is not confined to church buildings but can shape every corner of daily life.

The challenge for every Christian entrepreneur is not simply to begin with the right motivation but to remain rooted in that motivation through every stage of growth. This requires something far deeper than occasional prayer or symbolic references to faith. It requires a daily posture of surrender that acknowledges God as the true leader of the enterprise. Decisions must be filtered through prayer rather than made solely through analysis. Success must be interpreted through the lens of spiritual impact rather than financial metrics alone. The entrepreneur must continually remember that the business belongs to God long before it belongs to any human owner. When that truth remains alive in the heart of the builder, the foundation remains secure regardless of how large the structure eventually becomes.

The world does not desperately need more Christian businesses that merely display religious branding. What the world truly needs are businesses led by people whose lives remain anchored in the presence of Christ so deeply that the influence of that relationship quietly shapes every aspect of how the organization operates. These are the businesses where employees sense something different in the atmosphere. They are the companies where integrity is practiced even when it costs money. They are the workplaces where compassion outweighs competition and where success is measured not only by profit margins but also by the lives that are strengthened along the way.

When a Christian entrepreneur remembers the Rock beneath the structure, the entire journey begins to change. Work no longer feels like a lonely struggle to force outcomes into existence. Instead, it becomes a daily collaboration with the One who created the universe and understands the deeper purpose behind every opportunity that appears along the path. The builder no longer carries the entire burden of success because the true Builder has always been present, patiently waiting to guide every step. This realization can transform even the most exhausted business owner into someone who rediscovers the joy that existed at the very beginning of the vision.

The most important rebuilding work in any Christian business does not happen in conference rooms or strategic planning sessions. It happens in the quiet places where a person stands honestly before God and admits that somewhere along the journey the center of gravity shifted. Rebuilding begins when the entrepreneur recognizes that the issue was never primarily about tactics, systems, or market dynamics. The deeper issue was spiritual alignment. A business can be efficient, profitable, and professionally managed while still drifting away from the presence that once gave it life. That drift rarely happens through rebellion. It happens through distraction, through exhaustion, through the gradual accumulation of responsibilities that slowly crowd out the space where prayer and listening once lived. The builder does not wake up one morning and decide to remove God from the foundation. Instead, the foundation slowly becomes buried under layers of activity until the builder begins operating as though everything depends on personal strength alone.

Many Christian entrepreneurs are deeply committed to honoring God, yet they unknowingly fall into a pattern that quietly undermines their own mission. They begin treating spiritual life as something separate from the mechanics of business. Prayer becomes something that happens before the workday begins rather than something that flows through every decision that follows. Scripture becomes a source of inspiration rather than a living guide that shapes leadership choices, hiring practices, partnerships, and financial priorities. The separation is subtle, and it often feels practical because the business world teaches people to rely on measurable strategies rather than spiritual discernment. Over time the entrepreneur begins trusting experience, instincts, and industry knowledge more than the quiet guidance of the Holy Spirit. The business may continue functioning, but the living connection that once made the work feel sacred begins to fade.

This separation is where many Christian businesses unknowingly begin constructing new layers on sand. The structure can appear strong for a long time because human intelligence and discipline are capable of producing impressive results. But eventually every system encounters a moment that exposes the limitations of human control. Markets shift, customers change, competitors innovate, and unforeseen challenges arise that cannot be solved by repeating yesterday’s strategy. When that moment arrives, the entrepreneur discovers whether the foundation beneath the company is truly anchored in Christ or merely decorated with Christian language. The storm reveals what calm seasons can conceal. Businesses that are deeply rooted in the presence of God often navigate storms with surprising resilience because the leader remains anchored in something stronger than circumstances. Businesses that slowly drifted toward self-reliance often feel shaken in ways that expose how fragile the underlying structure has become.

Yet storms are not always destructive. Sometimes they are the very instruments God uses to awaken the builder to a deeper reality. A season of struggle can become a sacred invitation to rediscover the reason the journey began in the first place. Many Christian entrepreneurs describe a moment when their carefully constructed plans stopped working and their sense of control evaporated. In that moment they returned to prayer with a humility that had slowly faded during years of progress. They began asking not merely for success but for guidance. They stopped treating God as someone who blesses their plans and began seeking the plans that God Himself wanted to unfold through their lives. Something remarkable often happens in that moment of surrender. The entrepreneur begins experiencing clarity that does not originate from human calculation. Ideas emerge that align more closely with the deeper calling that first inspired the business.

Rebuilding a business on the Rock does not necessarily mean abandoning ambition or rejecting excellence. In fact, it often leads to a higher standard of both. When Jesus becomes the center of a company’s identity, the entrepreneur begins pursuing excellence not merely to outperform competitors but to honor the One whose name they carry. Integrity becomes more than a policy. It becomes a reflection of the character of Christ. Decisions about pricing, customer relationships, employee treatment, and community involvement begin flowing from a deeper place of conviction rather than short-term advantage. The business gradually transforms into something that reflects the Kingdom of God in quiet but unmistakable ways. Customers may not always be able to articulate what feels different about the company, yet they sense an atmosphere of trust that is increasingly rare in a world driven primarily by profit.

Employees also notice the difference when a business is truly anchored in Christ. Leadership rooted in humility creates environments where people feel valued rather than used. Instead of viewing employees as interchangeable pieces in a productivity machine, the entrepreneur begins recognizing the sacred dignity present in every person on the team. Conversations about goals and performance remain important, but they are balanced by genuine concern for the well-being of the people involved. This shift does not weaken the business. It strengthens it because people tend to give their best work in environments where they know they are respected and appreciated. A company built on the Rock begins reflecting the relational values that Jesus modeled throughout His ministry.

Customers, too, become part of this transformation. In many industries, businesses rely heavily on persuasion techniques designed to maximize sales regardless of whether the product truly serves the customer’s long-term interest. A Christ-centered business approaches these relationships differently. Instead of focusing solely on closing the transaction, the entrepreneur begins asking a deeper question about whether the service genuinely benefits the person on the other side of the exchange. Honesty replaces exaggeration. Transparency replaces manipulation. Trust becomes the most valuable currency the company possesses. Over time that trust often proves more powerful than any marketing strategy because people recognize authenticity when they encounter it.

None of this transformation happens overnight. Rebuilding on the Rock is not a single decision but an ongoing posture of surrender that shapes the rhythm of daily life. It begins with the simple but profound act of remembering who the true owner of the business really is. The entrepreneur may legally hold the title, but spiritually the enterprise belongs to God long before it belongs to any human leader. When that truth becomes real again, the weight of carrying the entire future of the company begins to lift. The builder no longer feels alone in the responsibility because the true Architect is present in every conversation, every opportunity, and every unexpected challenge.

One of the most beautiful discoveries many entrepreneurs make during this rebuilding process is that God often cares about the details of their work far more than they realized. He is not distant from business decisions or uninterested in the practical realities of commerce. The same God who guided fishermen, tax collectors, and craftsmen during the time of Jesus remains present in the ordinary tasks of modern life. When a person invites Him fully into the daily operation of a company, guidance begins appearing in ways that cannot always be explained through conventional logic. Opportunities align at unexpected moments. Relationships form that open new paths forward. Challenges that once felt overwhelming become manageable because the entrepreneur is no longer relying solely on personal strength.

There is also a deeper transformation that occurs within the heart of the builder. When a business is built primarily on human ambition, the emotional highs and lows of entrepreneurship can feel overwhelming. Success brings temporary excitement, but it is often followed by anxiety about maintaining momentum. Failure can feel devastating because it appears to threaten the identity of the person who built the company. When the foundation shifts back to Christ, the emotional landscape begins to stabilize. The entrepreneur discovers that their identity does not depend on the rise and fall of financial results. They remain secure because their life is rooted in something far more enduring than any quarterly report. This freedom allows them to lead with greater courage because their sense of worth no longer fluctuates with the performance of the business.

Many Christian entrepreneurs who experience this transformation begin realizing that their company was never meant to be merely a vehicle for personal success. It was always intended to become a channel through which God could reach people in places where traditional ministry rarely enters. Employees who might never attend a church service encounter leadership shaped by compassion and integrity. Customers who expect ordinary transactions experience unexpected honesty and care. Business partners observe decisions guided by principles that transcend short-term profit. In quiet and often unseen ways, the company begins reflecting the character of Christ to people who may have never encountered Him in any other context.

This perspective changes the meaning of success entirely. Profit remains important because it allows the business to survive and expand its influence, but it is no longer the ultimate measurement of value. The deeper question becomes whether the company is reflecting the heart of God in the way it operates. A smaller business built on that foundation can have far greater spiritual impact than a massive organization that quietly abandoned the Rock beneath its structure. The true measure of success becomes the faithfulness of the builder rather than the size of the building.

For entrepreneurs who feel spiritually dry or stuck, this realization can become the beginning of a profound awakening. The path forward does not require discovering some secret marketing strategy or reinventing the entire business model. The path forward begins by returning to the place where the vision first came alive. It begins by kneeling again in the quiet presence of God and acknowledging that the company was never meant to exist apart from Him. From that moment of surrender, new life can begin flowing through every aspect of the enterprise. The builder rediscovers the joy of working alongside the One who first planted the dream in their heart.

In the end, the greatest danger facing Christian businesses is not competition, economic uncertainty, or limited resources. The greatest danger is forgetting the One they were building it for. When that memory fades, the structure begins slowly drifting away from the foundation that once made it strong. But when the builder remembers the Rock and rebuilds every part of the enterprise upon Him, something extraordinary begins to unfold. The business becomes more than a commercial endeavor. It becomes a living witness that even in the marketplace, the presence of Christ can transform ordinary work into something eternal.

Your friend, Douglas Vandergraph

Watch Douglas Vandergraph’s inspiring faith-based videos on YouTube https://www.youtube.com/@douglasvandergraph

Support the ministry by buying Douglas a coffee https://www.buymeacoffee.com/douglasvandergraph

Financial support to help keep this Ministry active daily can be mailed to:

Vandergraph Po Box 271154 Fort Collins, Colorado 80527

LIKE A LADY BUG

What I love about Rio is the feeling of untouched alleyways, shaded by generous almond trees, yet the passersby never grab its fruits, perhaps because of the salty winds, or simply out of love for its silence, All the paineiras of Ipanema sit there patiently, protecting all couples in their long, slow kisses, while branches are entertained on their delicate, solitary journey of exploring lightness through the air. Roots know nothing but to seek, to seek; its flowers know nothing but to bloom and give.

There are corners of Rio where the world seems to have stopped in ’95, where the passing of time is measured only by the ice cream cone melting in my hand. Who is born here carries an open heart as destiny, and a gentle indifference toward the rest of the world, poor souls who never tasted this light, the one that rises over the mountains before surrendering itself to the sea.

Here I was born on a sunny spring 1990, my mom couldn't lay down the last two weeks, the umbilical cord is wrapped around the baby's neck, said the doctor: Forget October 11th, she should be born earlier, scheduled September 28th. My mom sat on her bergère in the living room listening to the neighbor playing bossa nova, Tom Jobim that's how I orchestrated my prelude to life. And then just in time for the first flowers to bloom, a week after the beginning of spring, 08:17 of a sunny friday, crescent moon, I had my first breath into the world. My mom dressed me in red and in his first visit, my brother said: “She looks like a lady bug.”

/mar26

Rangers vs Padres

Listening now to the Padres Radio Network for pregame coverage to be followed by the call of my afternoon's MLB Spring Training Game of choice featuring the San Diego Padres vs my Texas Rangers. Go Rangers!

And the adventure continues.