# building trust (blogs) — RSS Amplifier Recent posts from the 4 feeds in the RSS Amplifier directory that cover building trust. Page: Feed: --- ## [Making Sense of How Others Think](https://thesilentstruggle.substack.com/p/how-others-think-dissecting-a-reddit) _2026-08-17 · Elina · Leadership Capability_ The same set of facts, read five different ways. What that says about how we all make decisions and what makes us feel stuck. ## [Making Sense of Self Doubt: "What if I am wrong?"](https://thesilentstruggle.substack.com/p/making-sense-of-self-doubt-what-if) _2026-08-10 · Elina · Leadership Capability_ You don't need to be certain to speak up. You need to understand what you're actually waiting for. ## [Diversity was never the issue. Complexity was.](https://thesilentstruggle.substack.com/p/we-tried-to-fix-diversity-it-was) _2026-08-04 · Elina · Leadership Capability_ Diversity talk went quiet in a lot of organisations, but the real-life complexity never did. Here's the capability we never built, and what it actually takes to lead through it well. ## [Difficult People Aren't Always the Problem](https://thesilentstruggle.substack.com/p/difficult-people-arent-always-the) _2026-06-29 · Elina · Leadership Capability_ A two-part approach to working with people who pull a negative reaction out of you ## [Stop fighting the behaviour. Start seeing the story.](https://thesilentstruggle.substack.com/p/stop-fighting-the-behaviour-start) _2026-06-21 · Elina · Leadership Capability_ When nobody owns the problem, who’s fault is that? We argued both sides to find out. ## [How to Close the Gap Between Knowing and Doing: The Capability Practice Method.](https://thesilentstruggle.substack.com/p/the-lamp-post-method-what-managers) _2026-06-09 · Elina · Leadership Capability_ He was told he would never run. By 64 he had finished a hundred marathons. He got there the same way anyone builds a hard skill. Exactly how leadership capability is built too. ## [Building Trust — Monthly Summary](https://thesilentstruggle.substack.com/p/building-trust-monthly-summary) _2026-06-04 · Elina · Leadership Capability_ Watch now | Trust is not a personality trait. It is a capability you earn through consistency, through care, through how you show up under pressure. [Listen](https://api.substack.com/feed/podcast/200606600/b84d5987c0902d38d801aad4fa011045.mp3) ## [How to Become Someone People Trust (Building Trust Part 3)](https://thesilentstruggle.substack.com/p/how-to-become-someone-people-trust) _2026-05-20 · Elina · Leadership Capability_ Trust is the thing that moves careers and opens opportunities. It's also almost never named when it's missing. This article names what's actually happening and gives you a framework to work with. ## [Can you control trust at work? Curation of perspectives (Building Trust Part 2)](https://thesilentstruggle.substack.com/p/can-you-control-trust-at-work-curation) _2026-05-13 · Elina · Leadership Capability_ Two practitioners, two perspectives on one of the messiest topics in leadership — what trust at work actually means, and how much of it we can deliberately control. ## [Two Weeks After "Context Is the New Code" at AIE London: I Did Not See This Coming](https://jedi.be/blog/2026/two-weeks-after-context-is-the-new-code/) _2026-05-13 · JEDI — Just Enough Developed Intelligence_ It’s about two weeks after the Context Is the New Code presentation at AIE London. I called it “an unpolished thought” on stage, because that’s what it was. I’d drawn an infinity loop on a slide, and apparently numbered the steps 1-4-3-2 instead of 1-2-3-4, which the internet has been kind enough to point out roughly 200 times. Fair. The diagram was, in fact,… ## [From any door to your door (Sponsored)](https://crawlproof.com/a/QeqArHSZcOeq) _2026-05-12 · **Sponsored**_ Book rides, errands, deliveries, groceries and home help in one app ## [The Leadership Supplies store is open](https://thesilentstruggle.substack.com/p/the-leadership-supplies-store-is) _2026-05-04 · Elina · Leadership Capability_ I built an imaginary store to find out what managers really need right now. Browse the shelves. Tell me what you would buy. ## [The leader who built this can't be the leader who scales it](https://toddemaus.substack.com/p/the-leader-who-built-this-cant-be) _2026-04-01 · Todd Emaus · Grow Yourself, Grow Your Startup_ Three traps that keep founders stuck in the version of themselves their company has outgrown. ## [Sonar Summit 2026 | The Context Flywheel: How the Best AI Coding Teams Pull Ahead](https://jedi.be/blog/2026/talk-2026-context-flywheel-how-best-ai-coding-teams-pull-ahead/) _2026-03-13 · JEDI — Just Enough Developed Intelligence_ The competitive edge in AI-native development isn’t the model or the coding agent — it’s the organizational context you feed it. In this conversation with Edgar at the Sonar Summit, I walk through why context is the fuel that makes agents perform, and why the teams that invest in building it systematically are pulling ahead. ## [Founder Burnout Is a Leadership Failure](https://toddemaus.substack.com/p/founder-burnout-is-a-leadership-failure) _2026-03-09 · Todd Emaus · Grow Yourself, Grow Your Startup_ You're Not Tired From the Work. You're Tired From the Performance ## [CI/CD for Context: Same Pipeline, Different Rules](https://jedi.be/blog/2026/cicd-for-context/) _2026-03-05 · JEDI — Just Enough Developed Intelligence_ If context is code, can we test it in a CI pipeline? The CDLC says generate, evaluate, distribute, observe. The evaluate step is where it gets real. I wrote about this on tessl.io : evals are the equivalent of tests for context. But they follow different rules. Seven problems came up, split between how you run evals and what you’re actually measuring. Part 1: Running evals Non-determinism.… ## [The Context Flywheel: Winning on Context, Not Models](https://jedi.be/blog/2026/context-flywheel/) _2026-02-26 · JEDI — Just Enough Developed Intelligence_ The Context Development Lifecycle described four stages: generate, evaluate, distribute, observe. That was the what. The flywheel is the why. Better context produces better agent output. Better agent output generates better signals. Better signals produce better context. Each cycle compounds. By the tenth iteration, the team that invested in context is operating at a fundamentally different level… ## [AI Manager Styles: From Full Visibility to Pure Outcomes](https://jedi.be/blog/2026/ai-manager-styles-from-full-visibility-to-pure-outcomes/) _2026-02-22 · JEDI — Just Enough Developed Intelligence_ You’re managing the thing that writes code. So what’s your management style? Most people start the same way: watching every action, approving every tool call. Then they trust more, review less, scale up. It’s an evolution. The management style that works on day one isn’t the one that works on day ninety. Vincent van den Tol wants to keep track of how his application is… ## [Intentional Overuse Is an AI Coding Learning Strategy](https://jedi.be/blog/2026/intentional-overuse-mapping-ai-boundaries/) _2026-02-22 · JEDI — Just Enough Developed Intelligence_ Every time AI removes one bottleneck, the system reveals the next one. The useful question isn’t “how much faster” but “what breaks next.” That question has been my compass. Intentional overuse has proven a good learning strategy for me. Yes, if all you have is a hammer, everything looks like a nail. That’s the criticism, and it’s fair as a permanent way… ## [Self-Tuning Context: When Agents Rewrite Their Own Instructions](https://jedi.be/blog/2026/self-tuning-context/) _2026-02-22 · JEDI — Just Enough Developed Intelligence_ What if the agent could optimize its own instructions? Every time an agent messes up, you open the CLAUDE.md, add a rule, and hope it sticks. You’re the feedback loop: watching output, diagnosing failures, rewriting instructions by hand. Mitko Vasilev , a CTO focused on enterprise R&D and a vocal advocate for owning your own AI stack, is doing exactly that . He’s running a feedback… ## [Think Tax: The Real Cost of AI-Generated Code](https://jedi.be/blog/2026/think-tax-comprehension-debt/) _2026-02-20 · JEDI — Just Enough Developed Intelligence_ Cole Medin’s post on comprehension debt got me thinking. The term is making the rounds — it’s the gap between the code your team has shipped and the code your team actually understands. Unlike technical debt — which you can see and plan around — comprehension debt is invisible until something breaks and nobody knows why. I’ve been calling it the think tax . Every time you accept… ## [Install Manifest V3 Extension (Sponsored)](https://crawlproof.com/a/QHAuhsO6CwRE) _2026-02-19 · **Sponsored**_ Get this Manifest V3 extension from the official TronBrowser Store listing. ## [DevOps Modernization: AI Agents, Intelligent Observability and Automation](https://jedi.be/blog/2026/talk-2026-devops-modernization-ai-agents-intelligent-observability/) _2026-02-19 · JEDI — Just Enough Developed Intelligence_ I joined Olalekan Elesin (HRS Group), Mallika Rao (Netflix), and Martin Reynolds (Harness) for an InfoQ Live panel moderated by Renato Losio. The conversation centered on how AI is changing DevOps and SRE practices — moving beyond reactive monitoring toward predictive, automated delivery and operations. The real problem: human attention waste The panel quickly aligned on what AI should actually… ## [The Context Development Lifecycle: Optimizing Context for AI Coding Agents](https://jedi.be/blog/2026/context-development-lifecycle/) _2026-02-19 · JEDI — Just Enough Developed Intelligence_ Coding agents can write features and fix bugs. The bottleneck has shifted — from how fast we can write code to how effectively we communicate what we actually want. Context is the new constraint. Most teams store context informally: .cursorrules files, scattered .md documents, Slack threads, tribal knowledge that lives in people’s heads. None of it is versioned. None of it is tested. None of… ## [Intercepting Prompt Injection at the Syscall Level: A macOS Proof of Concept](https://jedi.be/blog/2026/intercepting-prompt-injection-at-the-syscall-level/) _2026-02-17 · JEDI — Just Enough Developed Intelligence_ When you git clone a repository and open it with Claude Code, the first thing it does is read CLAUDE.md — a project instruction file that shapes how the AI behaves. This happens automatically, before any hooks fire, before you type a single prompt. If that file contains prompt injection, you’ve already lost. This post describes context-filter , a proof of concept that intercepts file reads… ## [Unlearning, Experimentation and Engineering Rigor in an Agentic World](https://jedi.be/blog/2026/talk-2026-unlearning-experimentation-engineering-rigor-agentic-world/) _2026-02-11 · JEDI — Just Enough Developed Intelligence_ In this ThoughtWorks Technology podcast episode, Patrick Debois joins Nathan Harvey (DORA, Google Cloud) and host Ken Mugrage for an in-person conversation about what changes when AI agents enter the software development lifecycle. The discussion centers on a core tension: how do experienced engineers unlearn established habits while maintaining the engineering rigor that keeps systems reliable? ## [Sandboxing AI Agents: From dclaude to ADDT](https://jedi.be/blog/2026/sandboxing-ai-agents-from-dclaude-to-addt/) _2026-02-02 · JEDI — Just Enough Developed Intelligence_ When AI coding agents can navigate your filesystem, one wrong move and they’re “helpfully” editing files in your production branch while you’re working on a feature. I built two tools to solve this — starting with a focused wrapper, then generalizing it into something any agent can use. dclaude: Containing Claude Code The first iteration was dclaude — a containerized… ## [Automating Claude Desktop via Chrome DevTools Protocol](https://jedi.be/blog/2026/automating-claude-desktop-via-chrome-devtools-protocol/) _2026-01-28 · JEDI — Just Enough Developed Intelligence_ Electron apps support the Chrome DevTools Protocol. That means Claude Desktop can be launched with a debug flag and controlled programmatically: /Applications/Claude.app/Contents/MacOS/Claude --remote-debugging-port=9222 Hit localhost:9222 and you can inject JavaScript directly into the UI. From there, things get interesting fast. What you can do Extract responses — Use a MutationObserver to… ## [AI-Native Everything: Connecting Claude Desktop to My Whole Workflow](https://jedi.be/blog/2026/ai-native-everything-connecting-claude-desktop-to-my-whole-workflow/) _2026-01-27 · JEDI — Just Enough Developed Intelligence_ It was right under my nose. I’d been optimizing my coding work with AI but completely neglecting everything else — emails, meetings, task management, research. The fix: connect Claude Desktop to all of it via MCP servers. Standard connectors The easy wins: Linear, Notion, Google Drive, Slack, Google Calendar, Google Tasks. Plug them in, Claude can read across all of them. Custom MCP servers… ## [Building My Own Tools Instead of Reusing](https://jedi.be/blog/2026/building-my-own-tools-instead-of-reusing/) _2026-01-26 · JEDI — Just Enough Developed Intelligence_ I’m increasingly writing my own tools with AI rather than reaching for existing open-source libraries. For smaller applications — glue apps, the $5 appstore kind, MCP servers — I can iterate to exactly what I need faster than reading through someone else’s codebase and adapting to their decisions. I know pretty well what I want, or can iterate fast to get there, versus being dependent… ## [Trust, Accountability and AI Coding Swarms](https://jedi.be/blog/2026/trust-accountability-and-ai-coding-swarms/) _2026-01-24 · JEDI — Just Enough Developed Intelligence_ A late night conversation with Claude that started with Steve Yegge’s Beads architecture and ended somewhere unexpected. Full conversation (PDF) . The question Who’s accountable when AI agents write 44,000 lines of code that no human has looked at? Architecture convergence Across Beads, Gas Town, Claude Flow, and Cursor’s swarm experiments, the same patterns keep emerging: Flat… ## [2025: Make Coding Agents Work. 2026: Make Them Work Better.](https://jedi.be/blog/2025/2025-make-coding-agents-work-2026-make-them-work-better/) _2025-12-05 · JEDI — Just Enough Developed Intelligence_ 2025 was the year of making coding agents work — figuring out what they’re good at, wiring them into IDEs, running them async, mostly in solo dev environments. Exploration phase. 2026 is about making them work better . The shift from “can I use this?” to “how do I scale this across a team?” That means: Spec-driven development becoming a standard practice, not a… ## [AI QA That Opens Fix PRs (Sponsored)](https://crawlproof.com/a/NFZ7IsU3cUuZ) _2025-12-04 · **Sponsored**_ Runs browser QA, files issues with repro evidence, and opens fix PRs. ## [Coding with AI — CTO Club Belgium](https://jedi.be/blog/2025/talk-2025-coding-with-ai-cto-club/) _2025-11-26 · JEDI — Just Enough Developed Intelligence_ Gave a talk at CTO Club Belgium on coding with AI. The session was deliberately interactive — less presentation, more shared experiences. Most CTOs in the room had teams experimenting with AI coding tools, and the conversation quickly moved past the hype into what actually works at scale. The gap between vibe coding and reality Everyone wants to vibe code. Most early adopters hit a wall. The tools… ## [Code Speed Reading](https://jedi.be/blog/2025/code-speed-reading/) _2025-11-21 · JEDI — Just Enough Developed Intelligence_ I wonder if there are code speed reading courses — the way there are speed reading courses for text. As AI generates more code faster than we can review it, the ability to quickly comprehend unfamiliar code becomes a critical skill. Some interesting perspectives from the conversation that followed: Build tools to read for you — Tudor Girba’s take: the answer isn’t faster reading,… ## [Spec-Driven Development: 10 Things You Need to Know About Specs](https://jedi.be/blog/2025/spec-driven-development-10-things-you-need-to-know/) _2025-11-07 · JEDI — Just Enough Developed Intelligence_ Spec-driven development is no magic bullet, but it’s useful nonetheless. The trap is expecting any technology to solve all problems — or dismissing it when it doesn’t. Treat every new tool as part of your toolkit and understand its strengths and limitations. Here are 10 things I’ve learned about working with specs for AI-assisted development. 1. What’s a spec, really? A… ## [Learning Rate Beats Years of Experience](https://jedi.be/blog/2025/learning-rate-beats-years-of-experience/) _2025-11-06 · JEDI — Just Enough Developed Intelligence_ Senior devs often tell me they’re worried juniors won’t learn what good looks like. Juniors tell me they’re learning much faster with AI helping them stumble along the way. Both are right. The question is which effect dominates. Learning rate as competitive advantage Greg Ceccarelli nailed it: the most dangerous person in any room isn’t the expert with twenty years of… ## [Reflecting on The DevOps Handbook](https://jedi.be/blog/2025/talk-2025-reflecting-on-the-devops-handbook/) _2025-10-30 · JEDI — Just Enough Developed Intelligence_ In this episode of the Book Overflows podcast, Patrick joins hosts Carter Morgan and Nathan Tops to reflect on The DevOps Handbook, originally published in 2016. Patrick clarifies his role as a chief consultant and thought partner to Gene Kim rather than a primary author, and shares the origin story of the term “DevOps” itself, which emerged almost accidentally from the need for a… ## [Radical Ideas for Code Review Volume](https://jedi.be/blog/2025/radical-ideas-for-code-review-volume/) _2025-10-28 · JEDI — Just Enough Developed Intelligence_ Asked ChatGPT for more radical ideas to deal with code review volume. Suggestion 9 was: just regenerate the code instead of reviewing it. It’s not wrong — but no such product might survive long enough to have users. The reactions were interesting: As complexity increases, regenerating could require “a trillion tokens and multiple days” — it doesn’t scale linearly It might… ## [The AI Coding Fabric](https://jedi.be/blog/2025/ai-coding-fabric/) _2025-10-28 · JEDI — Just Enough Developed Intelligence_ Been pondering on what I call the “AI Coding Fabric” — a new infrastructure challenge emerging as AI agents move beyond traditional IDEs into sandbox environments. Platform engineers need to think about: Agent access rules — who can do what, where Spec registries — shared, versioned specifications Code-specific guardrail rules — beyond generic safety, actual coding constraints… ## [Devoxx 2025: 8 Talks on Spec-Driven Development](https://jedi.be/blog/2025/devoxx-2025-spec-driven-development-talks/) _2025-10-21 · JEDI — Just Enough Developed Intelligence_ Curated 8 talks from Devoxx 2025 related to spec-driven development for writing better code with AI. Kudos to Stephan Janssen for another great edition. Spec Driven Development: Why Your Prompt Chaos Won’t Scale — Simon Maple Generative AI: Tech du Jour or the Next Big Thing? — Massimo Re Ferrè Backlog.md: Reaching 95% Task Success Rate with AI Agents — Alexandru Gavrilescu The New AI Native… ## [From DevOps to AI-Native: The Next Great Shift in Software](https://jedi.be/blog/2025/talk-2025-from-devops-to-ai-native-secure-disclosure/) _2025-10-15 · JEDI — Just Enough Developed Intelligence_ A conversation with The Secure Disclosure covering the full arc from DevOps to AI-native development — and why the engineering discipline hasn’t changed, even as everything around it has. The developer as ops person The central irony: developers using AI coding assistants have effectively become operations people. They receive code they didn’t write and must review, understand, and… ## [The New AI Native Dev Coding Workflow](https://jedi.be/blog/2025/talk-2025-new-ai-native-dev-coding-workflow/) _2025-10-10 · JEDI — Just Enough Developed Intelligence_ Patrick presents a comprehensive framework for understanding how AI is transforming the developer workflow, drawing on his experience curating nearly 500 AI coding tools over the course of a year. Rather than focusing solely on code generation, the talk identifies four key patterns that define the emerging AI-native developer experience: managing agents as a reviewer, expressing intent through… ## [From DevOps to AI-Native: Rethinking Software Delivery](https://jedi.be/blog/2025/talk-2025-from-devops-to-ai-native/) _2025-09-30 · JEDI — Just Enough Developed Intelligence_ In this TechRox podcast episode recorded ahead of the TechRox Summit, Patrick Debois sits down with host Dimitri Bi to discuss the journey from DevOps to AI-native development. Patrick recounts how boredom with the plateauing DevOps conversation, combined with explorations in the metaverse, digital twins, and gaming automation, naturally led him into the generative AI space. He describes AI as… ## [DevOps, AI, and the Future of Engineering](https://jedi.be/blog/2025/talk-2025-devops-ai-and-the-future-of-engineering/) _2025-09-19 · JEDI — Just Enough Developed Intelligence_ In this episode of the Hangar DX podcast, Patrick joins host Anka Jan to discuss the parallels between the DevOps movement and the current AI transformation in software engineering. Drawing on his history as the person who coined the term DevOps and organized the first DevOps Days, Patrick identifies recurring patterns: the same spectrum of believers and skeptics, the rush of competing tools, and… ## [The New Engineering Paradigm: Day 1 Vibe Code, Year 1 Rewrite in Rust](https://jedi.be/blog/2025/the-new-engineering-paradigm-vibe-code-to-rewrite/) _2025-09-03 · JEDI — Just Enough Developed Intelligence_ Stan Girard’s lifecycle of modern software — there’s some truth to it: Day 1 : Vibe code with Claude Week 1 : Fix bugs for production Month 1 : Senior engineer optimizes for scale Year 1 : Rewrite in Rust The punchline: despite using AI extensively, most of the code that goes to production is still human-written. Domain expertise matters. Doing one thing well requires understanding… ## [An Ode to Junior](https://thoughtsofkb.substack.com/p/an-ode-to-junior) _2025-07-29 · Kieran Bond · Thoughts of KB_ Learning, building trust, and getting stuff done are crucial to progressing your career - especially early on. These are the things I learned on my journey from junior. ## [What AI Thought About My Resume](https://jedi.be/blog/2025/what-ai-thought-about-my-resume/) _2025-07-22 · JEDI — Just Enough Developed Intelligence_ Fed my resume to AI and let it analyze me. It’s not wrong. The interesting observation from the conversation that followed: people who enjoy collaborating with AI for coding might share specific personality traits — particularly introverted intuitive types. Whether that’s MBTI pattern-matching or genuine signal is an open question. The AI assessment didn’t research “deep… ## [4 AI Native Dev Patterns — ServerlessConf Edition](https://jedi.be/blog/2025/talk-2025-4-ai-native-dev-patterns-serverlessconf-edition/) _2025-07-20 · JEDI — Just Enough Developed Intelligence_ Patrick presents the four patterns of AI-native development at ServerlessConf, framing the rapid evolution of coding tools – from simple tab completions to multi-agent systems that autonomously work across entire codebases. He traces the progression from single-line copilot suggestions through chat-based generation, multi-file edits, terminal and browser awareness, and eventually to tools… ## [4 AI Native Development Patterns — Future of Software](https://jedi.be/blog/2025/talk-2025-4-ai-native-development-patterns-future-of-software/) _2025-07-20 · JEDI — Just Enough Developed Intelligence_ Patrick presents the four patterns of AI-native development at the Future of Software event hosted by Eficode. He opens by tracing the rapid evolution of coding tools – from basic tab completions and chat-based copy-paste workflows to multi-file predictions, terminal and browser integration, reasoning models, and continuous autonomous loops like Devin. The key insight is that the technology… ## [The 4 Patterns of AI Native Development — AI Engineer Summit Edition](https://jedi.be/blog/2025/talk-2025-the-4-patterns-of-ai-native-development-ai-engineer-summit-edition/) _2025-07-20 · JEDI — Just Enough Developed Intelligence_ A framework of four patterns that describe how AI is fundamentally transforming the developer role beyond simple code completion. As AI technology has progressed from basic LLM prompts through RAG, function calling (MCP), and into agentic workflows, we are moving from “sprinkling AI on top” toward a genuinely AI-native way of working — one that reshapes the tasks developers perform day… ## [Prove It's Working: AI Swarms That Build Their Own Proof](https://jedi.be/blog/2025/prove-its-working-ai-swarms-that-build-their-own-proof/) _2025-07-11 · JEDI — Just Enough Developed Intelligence_ Igor Moochnick tested an autonomous distributed system built by an AI swarm. When he challenged it to prove it was actually working, instead of empty assurances, the swarm responded: “I’ll implement you a dashboard where you can monitor my progress and status.” Within 15 minutes, a fully operational monitoring dashboard appeared in the terminal. The swarm had planned the… ## [Automating Claude Code Configuration](https://jedi.be/blog/2025/automating-claude-code-configuration/) _2025-06-27 · JEDI — Just Enough Developed Intelligence_ Setting up Claude Code feels a bit like being the first DevOps on Mars. Here’s what I learned automating the configuration for CI/CD pipelines and scripted deployments. API key without OAuth Skip the OAuth flow — use an API key helper script: echo 'echo ${ANTHROPIC\_API\_KEY}' \> ~/.claude/anthropic\_key\_helper.sh chmod +x ~/.claude/anthropic\_key\_helper.sh claude config set --global apiKeyHelper…