I want to share my experience in the cloud, AI, and agents development areas.
AI-assisted development is shifting from single-model tools to multi-model and multi-agent engineering. This article explores how IBM Bob, GitHub Copilot, Gemini CLI, Claude Code, and OpenAI Codex orchestrate models—and why the orchestration layer is becoming the real platform.
The AI generated explores the complexities of privacy in the context of AI coding assistants and agentic IDEs. It emphasizes that privacy is now a structural choice within development environments rather than a simple policy acceptance. The effectiveness of six platforms is assessed based on their privacy features, highlighting trade-offs between integration, cost, and data handling.
I built a local-first Python CLI that reviews unpublished blog drafts with Claude and Codex in sequence. The tool keeps orchestration, reports, and publishing manual, while supporting mock mode for no-network testing. This post explains the workflow, privacy boundaries, provider authentication, and why human review remains essential.
In this post, I explore a lightweight handoff pattern for coordinating GitHub Copilot, OpenAI Codex, Claude Code, and IBM Bob in one local-first Python project. The goal: reduce context loss, make agent work traceable, and turn AI-assisted coding into a more structured engineering workflow.
This post shows the importance of clear prompt structure when developing local AI agents with frameworks like LangGraph and Ollama. Smaller models are less tolerant of ambiguities, making it crucial to separate instructions, context, and output formats. This enhances reliability, debugging, and reduces risks from untrusted inputs.
The blog post by Thomas Suedbroecker addresses the evolving governance challenges as AI becomes an active participant in engineering decision-making. It highlights the shift from human-centric to AI-assisted development and the resulting review gap. The author proposes specialized governance structures and emphasizes the importance of traceability for accountability in automated environments.
This article explores why governance becomes more important as software engineering becomes increasingly automated. It describes the evolution from human-centric development to AI-assisted and agentic engineering, where AI systems no longer only generate code but increasingly participate in engineering decisions. The main argument is that faster software creation does not automatically lead to better software. As AI accelerates implementation, accountability, traceability, reviewability, and human approval become more important. Effective governance allows organizations to use AI capabilities without losing human responsibility. It helps make AI-assisted software engineering more transparent, more reviewable, and more trustworthy.
This post compares various AI coding assistants/agents, emphasizing privacy from a developer's perspective. It highlights how modern AI systems function as integral tools in software development, shifting the privacy discourse from mere data training concerns to broader issues like data sovereignty, operational exposure, and pricing implications, particularly for individual developers.
This post reflects on Contextual Retrieval with Milvus in RAG systems. It explains how generated context can improve chunk retrieval, but also changes the retrieval corpus. Once generated context is indexed, validation, traceability, and quality control become architectural responsibilities—not optional implementation details.
The article continues the exploration of the AI Operational Complexity Cube, emphasizing that modern AI systems encompass software, infrastructure, and probabilistic AI components. It highlights the need for comprehensive testing approaches that consider interactions across these dimensions, as proper evaluation requires observing behaviors that emerge from integrated systems rather than isolated code.
Thomas Suedbroecker's Blog 