<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Monderings: Beyond the Prompt</title>
    <link>https://elijah.mondero.nz/</link>
    <description>Practical engineering insights on AI agents, .NET, AWS, and modern software architecture by Elijah Mondero.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 12 Nov 2026 03:40:00 +0000</lastBuildDate>
    <atom:link href="https://elijah.mondero.nz/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Eval-Driven Development in the AI Lifecycle: Beyond Vibe Checks to Production Rigor</title>
      <link>https://elijah.mondero.nz/post/eval-driven-development-adlc-industry-practices/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/eval-driven-development-adlc-industry-practices/</guid>
      <pubDate>Thu, 12 Nov 2026 03:40:00 +0000</pubDate>
      <description>In non-deterministic AI agents and LLM applications, standard unit tests break down. Eval-Driven Development (EDD) establishes objective, reproducible evaluation suites that replace 'vibe checks' with multi-tiered assertions, agentic trajectory metrics, and a continuous telemetry flywheel across the AI Development Life Cycle (ADLC).</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/6a554f4f-e158-4b4b-b8da-e90620f26e31.png" alt="Eval-Driven Development in the AI Lifecycle: Beyond Vibe Checks to Production Rigor" /></p>
<p>Every engineering team building with Large Language Models (LLMs) and autonomous agents encounters the same sobering inflection point.</p>
<p>In the prototype phase, everything feels magical. You write a system prompt, paste three sample inputs into an interactive playground, tweak a few instructions, and watch the model succeed. The demo dazzles stakeholders.</p>
<p>Then comes day one of production.</p>
<p>A user enters an unexpected prompt phrasing. The agent misinterprets a schema, hallucinates a database column, spirals into a three-minute multi-turn tool-calling loop, and crashes with an unhandled exception. An engineer rushes in to &quot;fix&quot; the system prompt by appending <em>&quot;Always make sure to...&quot;</em>. That patch fixes the immediate bug—but silently breaks four other query types that were working the day before. Nobody notices until customer support tickets flood in.</p>
<p>This chaotic anti-pattern has an industry name: <strong>&quot;Vibe-Based Development&quot;</strong>.</p>
<p>In deterministic software engineering, no team would deploy major code changes without automated unit and integration tests. Yet in AI development, teams routinely deploy non-deterministic, probabilistic agents based on nothing more than anecdotal observations and optimism.</p>
<p>To graduate from brittle demos to production-grade resilience, the industry has crystallized a disciplined methodology: <strong>Eval-Driven Development (EDD)</strong>. Rooted in the emerging <strong>AI Development Life Cycle (ADLC)</strong>, EDD transforms the way we design, iterate, test, and release autonomous systems.</p>
<hr />
<h3>The Anatomy of the Problem: Why Traditional TDD Fails for Agents</h3>
<p>In classical Test-Driven Development (TDD), tests are binary, deterministic, and isolated:</p>
<pre>assert calculate_tax(100.0, 0.15) == 115.0
</pre>
<p>Given input <em>A</em> and state <em>S</em>, the function executes along predictable control-flow branches and produces exact output <em>B</em>. If it returns <code>114.99</code>, the test fails with 100% certainty.</p>
<p>Autonomous agents and LLM applications demolish these fundamental assumptions:</p>
<ol>
<li><strong>Probabilistic Outputs:</strong> Foundation models sample from probability distributions over token vocabularies. Even with temperature set to <code>0.0</code>, subtle differences in GPU kernels, quantization, or floating-point rounding can yield semantically equivalent but syntactically divergent responses.</li>
<li><strong>Multi-Turn Trajectory Dynamics:</strong> An agent does not merely produce text; it observes its environment, reasons, selects a tool, parses the tool&#x27;s execution result, and iteratively plans its next step. The final outcome might be correct even if the trajectory took an unconventional path, or vice versa.</li>
<li><strong>Open-Ended Solution Spaces:</strong> There are often dozens of valid ways to answer an ambiguous query or write a piece of code. Exact string matching (<code>assert output == expected</code>) is completely unviable.</li>
<li><strong>Cascading Failure Modes:</strong> A slight prompt edit intended to improve reasoning in one domain can trigger sudden regressions in tool-calling precision elsewhere—a phenomenon known as the <em>alignment tax</em> or <em>prompt regression</em>.</li>
</ol>
<p>Because traditional unit tests cannot capture semantic correctness or agentic behavior, teams that do not establish automated evaluations inevitably resort to manual sampling. As AI practitioners <strong>Hamel Husain</strong> and <strong>Shreya Shankar</strong> point out in their foundational work on AI evaluations, developer velocity in AI is strictly bounded by the speed and reliability of your feedback loop. Without automated evals, every iteration requires human inspection, grinding development to an excruciating crawl.</p>
<hr />
<h3>What is Eval-Driven Development (EDD)?</h3>
<p><strong>Eval-Driven Development (EDD)</strong> is the systematic discipline of defining quantifiable success criteria, failure modes, and benchmark test suites (<em>evals</em>) <strong>before or concurrently with</strong> engineering agent prompts, tool interfaces, retrieval pipelines, or fine-tuning runs.</p>
<p>In EDD, evals serve as executable Product Requirements Documents (PRDs). Rather than guessing whether a new model checkpoint (e.g., migrating from Claude 3.5 Sonnet to Gemini 2.5 Flash) or an updated RAG chunking strategy improves your system, you run your eval harness and receive an objective scorecard across critical operational dimensions.</p>
<p><img src="https://elijah.mondero.nz/posts/images/eval-driven-development-adlc-industry-practices-architecture.png" alt="Eval-Driven Development Closed-Loop Lifecycle Architecture" /></p>
<hr />
<h3>The Three-Tier Evaluation Harness</h3>
<p>Frontier engineering teams at Anthropic, OpenAI, and leading AI platforms do not rely on a single catch-all metric. Instead, they structure their evaluation harness across three distinct tiers, moving from fast, deterministic checks to nuanced qualitative assessments:</p>
<blockquote><p><strong>Tier 1: Deterministic Code Assertions</strong> &amp;rarr; <strong>Tier 2: Agentic Trajectory Evaluation</strong> &amp;rarr; <strong>Tier 3: Model-Graded Judges</strong></p></blockquote>
<h4>Tier 1: Deterministic Code-Based Assertions</h4>
<p>The foundation of your eval suite must be code-based, fast, and free of LLM non-determinism:</p>
<ul>
<li><strong>Structural &amp; Schema Validation:</strong> Does the agent return valid JSON adhering to the specified Pydantic schema?</li>
<li><strong>Syntax &amp; Compilability:</strong> Does the generated Python, TypeScript, or SQL parse and execute without syntax errors?</li>
<li><strong>Negative Assertions:</strong> Did the model refrain from emitting forbidden tokens, leaked system prompts, or hallucinated internal URLs?</li>
<li><strong>Resource Budgets:</strong> Did the invocation complete within a strict latency threshold (e.g., <code>&lt; 2.5s</code>) and token ceiling (e.g., <code>&lt; 1,500</code> tokens)?</li>
</ul>
<p>Tier 1 assertions run in milliseconds and filter out obvious execution failures before expensive model-graded judges are invoked.</p>
<h4>Tier 2: Agentic Trajectory &amp; State Evaluation</h4>
<p>Evaluating an autonomous agent requires inspecting the <strong>journey</strong>, not just the destination. In its technical guide, <em>Demystifying evals for AI agents</em>, Anthropic highlights the necessity of evaluating multi-turn agent execution graphs:</p>
<ul>
<li><strong>Tool Call Precision &amp; Recall:</strong> Did the agent call the correct tool for the given task? Did it avoid calling irrelevant tools?</li>
<li><strong>Argument Validity:</strong> Were the function arguments structurally valid and grounded in the user&#x27;s request, rather than hallucinated?</li>
<li><strong>State Machine Invariants:</strong> Did the agent respect lifecycle transitions (e.g., never calling <code>execute_payment</code> prior to <code>verify_kyc</code>)?</li>
<li><strong>Loop Detection &amp; Recovery:</strong> Did the agent detect when an environment tool returned an error code, or did it repeat the exact failing invocation until hitting max recursion limits?</li>
<li><strong>Statistical Reliability (<code>pass@k</code> vs. <code>pass^k</code>):</strong> Because agents exhibit variance across repeated runs, single-pass evaluations give a false sense of security. Evaluating with <code>pass@k</code> measures whether the agent can find a solution in <em>k</em> attempts, while <code>pass^k</code> measures whether the agent succeeds reliably across all <em>k</em> consecutive runs. Production agents require high <code>pass^k</code> consistency.</li>
</ul>
<h4>Tier 3: Model-Graded Judges (LLM-as-a-Judge)</h4>
<p>For subjective qualities like answer tone, helpfulness, coherence, and RAG faithfulness, human annotation is too slow to run on every commit. Here, a stronger foundation model acts as a calibrated judge:</p>
<ul>
<li><strong>Single-Dimension Rubrics:</strong> Never ask a judge LLM to score &quot;quality from 1 to 10&quot;. General Likert scales suffer from severe calibration drift and position bias. Instead, evaluate one isolated dimension at a time (e.g., <em>Groundedness</em>, <em>Conciseness</em>, <em>Relevance</em>) using binary pass/fail or clear categorical rubrics.</li>
<li><strong>Reference-Guided Evaluation:</strong> Supply the judge model with a curated &quot;golden reference&quot; and clear scoring guidelines, asking it to produce step-by-step reasoning (<em>chain-of-thought</em>) before outputting its final verdict.</li>
<li><strong>Pairwise A/B Scoring:</strong> When comparing two prompt variations or model versions, pass both responses to the judge in randomized order to eliminate ordering bias.</li>
</ul>
<blockquote><p><strong>Important — Calibrating Your Judges:</strong> An automated judge is only as reliable as its alignment with human engineering consensus. Before trusting an LLM judge in your CI/CD pipeline, calibrate its decisions against a human-annotated baseline. Measure its Precision, Recall, and Cohen&#x27;s Kappa score on held-out test splits. Prioritize high recall on the &quot;fail&quot; class—it is far better for a judge to falsely flag an edge case for human review than to let regressions slip into production.</p></blockquote>
<hr />
<h3>EDD Across the AI Development Life Cycle (ADLC)</h3>
<p>The traditional Software Development Life Cycle (SDLC) assumes requirements are fixed and code behaves deterministically. The <strong>AI Development Life Cycle (ADLC)</strong> accommodates the experimental, empirical nature of intelligent systems. Integrating EDD into the ADLC establishes a continuous, self-reinforcing flywheel:</p>
<blockquote><p><strong>1. Behavioral Specification</strong> &amp;rarr; <strong>2. Golden Dataset Curation</strong> &amp;rarr; <strong>3. Implementation &amp; Experimentation</strong> &amp;rarr; <strong>4. CI/CD Eval Gates</strong> &amp;rarr; <strong>5. Production Telemetry</strong> &amp;rarr; <strong>6. Closed-Loop Auto-Ingestion</strong></p></blockquote>
<ul>
<li><strong>1. Requirements (Behavioral Specification):</strong> Transform vague product ideas into verifiable contracts through edge-case brainstorming and ambiguity detection. <em>Gate:</em> Behavioral rubric passes and edge cases are enumerated.</li>
<li><strong>2. Curation (Golden Dataset Assembly):</strong> Establish baseline ground truth with 50–200 representative prompts and expected trajectories. <em>Gate:</em> Ground truth is calibrated against human consensus.</li>
<li><strong>3. Iteration (Implementation &amp; Experimentation):</strong> Rapidly prototype prompts, tool schemas, routing, and model choices using local eval runners and trajectory debuggers. <em>Gate:</em> Eval pass rate improves without regressing existing baselines.</li>
<li><strong>4. Build &amp; Merge (CI/CD Eval Gates):</strong> Prevent regressions in shared branches via automated CI/CD regression suites. <em>Gate:</em> &gt;= 85% aggregate score, 0 safety failures, and &lt;= +5% token budget delta.</li>
<li><strong>5. Deployment (Production Telemetry &amp; Shadow Evals):</strong> Monitor live behavior with OpenTelemetry distributed tracing and shadow evals. <em>Gate:</em> Real-time drift detection and user sentiment monitoring remain healthy.</li>
<li><strong>6. Continuous Ops (Closed-Loop Auto-Ingestion):</strong> Turn production friction into permanent resilience via failure clustering and automated regression case generation. <em>Gate:</em> New failure trace ingested into the golden suite within 24 hours.</li>
</ul>
<hr />
<h3>Industry Practices: How Leading Engineering Teams Run Evals</h3>
<p>As shared by practitioners across Anthropic, Eugene Yan&#x27;s system patterns, and platforms like Arize, DeepEval, and LangSmith, world-class AI engineering teams adhere to four foundational practices:</p>
<h4>1. Start with Error Analysis, Not Complex Tools</h4>
<p>A common antipattern is spending three months building an elaborate evaluation framework before understanding where the model actually fails.</p>
<p>Instead, start by manually reading <strong>50 to 100 actual user interaction traces</strong>. As Hamel Husain emphasizes, you cannot write effective evaluation rubrics in a vacuum. Group real failures into concrete taxonomy buckets:</p>
<ul>
<li><em>Failure Category A:</em> Misunderstood domain-specific jargon (35%).</li>
<li><em>Failure Category B:</em> Called tool with missing required query parameters (25%).</li>
<li><em>Failure Category C:</em> Hallucinated answer when document had no relevant context (20%).</li>
<li><em>Failure Category D:</em> Overly verbose conversational preamble (20%).</li>
</ul>
<p>Once your error taxonomy is quantified, write targeted eval assertions specifically aimed at your top two failure modes. This guarantees immediate, high-leverage ROI.</p>
<h4>2. Decouple Prompting from Model Vendor APIs</h4>
<p>Tying your core agent logic directly to a single provider SDK creates architectural lock-in and blinds you to cost-performance optimizations.</p>
<p>By wrapping your agent around a standardized evaluation suite, swapping the underlying model—e.g., testing whether an open-weights model or a smaller reasoning model can handle the task at a 70% cost reduction—becomes a routine, low-risk experiment:</p>
<pre># Evaluate baseline Claude 3.5 Sonnet
python run_evals.py --model claude-3-5-sonnet --suite enterprise-goldens

# Evaluate challenger Gemini 2.5 Flash
python run_evals.py --model gemini-2-5-flash --suite enterprise-goldens
</pre>
<p>If the challenger maintains equivalent trajectory accuracy and pass rates across the eval suite, the migration can be merged with complete confidence.</p>
<h4>3. Enforce Evals as Pull Request Build Gates</h4>
<p>In production agent repositories, eval suites should run automatically in GitHub Actions on every Pull Request.</p>
<p>Just like code coverage gates in standard software engineering, the CI pipeline enforces strict thresholds:</p>
<ul>
<li><strong>No Regression Rule:</strong> Zero regressions permitted on core golden test cases.</li>
<li><strong>Safety &amp; Guardrails Floor:</strong> 100% pass rate on prompt-injection and sensitive data protection evals.</li>
<li><strong>Economic Governance:</strong> Proposed changes that increase average token consumption by more than 5% require explicit architectural sign-off.</li>
</ul>
<h4>4. The Telemetry Flywheel: Transforming Traces into Goldens</h4>
<p>The ultimate competitive moat in AI engineering is not the base foundation model—it is the <strong>proprietary evaluation flywheel</strong>.</p>
<p>Every time a production user gives a thumbs-down, regenerates an answer, or edits an agent-generated pull request, an event trace is captured. High-performing engineering teams cluster these failure traces, sanitize them for sensitive data, attach the corrected human ground truth, and automatically append them to the golden regression dataset.</p>
<p>As a result, the agent suite grows progressively more resilient every single day. A bug encountered in production can never silently re-emerge unnoticed.</p>
<hr />
<h3>The Cultural Shift: From Prompt Hackers to AI Systems Engineers</h3>
<p>Adopting Eval-Driven Development requires an engineering culture shift:</p>
<ul>
<li><strong>From &quot;Look at this cool demo&quot; &amp;rarr; &quot;What is our pass rate on the held-out regression suite?&quot;</strong></li>
<li><strong>From &quot;Let&#x27;s add 500 words of instructions to the system prompt&quot; &amp;rarr; &quot;Let&#x27;s inspect the error traces and write an assertion.&quot;</strong></li>
<li><strong>From &quot;The model feels smarter today&quot; &amp;rarr; &quot;Our Cohen&#x27;s Kappa score with expert annotators reached 0.88.&quot;</strong></li>
</ul>
<p>Writing software with probabilistic models is inherently uncertain. But developing that software should never be a gamble. By establishing Eval-Driven Development at the center of the AI Development Life Cycle, teams tame non-deterministic chaos, protect against silent regressions, and build autonomous agents worthy of production trust.</p>
<hr />
<h3>References &amp; Sources</h3>
<ul>
<li><a href="https://hamel.dev/blog/posts/evals/">Hamel Husain - Your AI Product Needs Evals</a>: The seminal essay on transitioning from vibe checks to systematic evaluation systems in production AI products.</li>
<li><a href="https://www.anthropic.com/engineering/demystifying-evals-for-ai-agents">Anthropic Engineering - Demystifying Evals for AI Agents</a>: Foundational architecture guide on grading multi-turn trajectories, state transitions, and measuring agent reliability via pass@k metrics.</li>
<li><a href="https://eugeneyan.com/writing/evals/">Eugene Yan - Patterns for Building LLM-based Systems &amp; Products</a>: Practical three-step frameworks for curating evaluation datasets, single-dimension judges, and experiment harnesses.</li>
<li><a href="https://www.anthropic.com/engineering/writing-effective-tools-for-ai-agents">Anthropic Engineering - Writing Effective Tools for AI Agents</a>: Best practices for designing tool interfaces, context management, and evaluation-driven iteration for autonomous workflows.</li>
<li><a href="https://sh-reya.com">Shreya Shankar &amp; Hamel Husain - AI Evals for Engineers</a>: Leading curriculum and methodology on error analysis, trace inspection, and production CI/CD evaluation pipelines.</li>
</ul>]]></content:encoded>
      <category>Eval-Driven Development</category>
      <category>AI Development Life Cycle</category>
      <category>Agentic SDLC</category>
      <category>LLM Evals</category>
      <category>Software Architecture</category>
      <category>Machine Learning</category>
    </item>
    <item>
      <title>The Agentic Development Life Cycle: Beyond TDD to Evaluation-Driven Development (EDD)</title>
      <link>https://elijah.mondero.nz/post/agentic-development-life-cycle/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/agentic-development-life-cycle/</guid>
      <pubDate>Wed, 11 Nov 2026 07:20:00 +0000</pubDate>
      <description>Writing code is only 20% of software engineering. As autonomous multi-agent pipelines take over the journey from PRD to production, traditional TDD and BDD are no longer sufficient to govern the macro lifecycle. Enter Evaluation-Driven Development (EDD)—where rubric scoring, automated evals, and strategic human gates tame the chaos of probabilistic software systems.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/ac0b47a9-3180-421c-a396-de25a4395b47.png" alt="The Agentic Development Life Cycle: Beyond TDD to Evaluation-Driven Development (EDD)" /></p>
<p>For decades, software development has been framed around a central activity: human engineers sitting in front of code editors, crafting syntax line by line. Even the first wave of generative AI—GitHub Copilot, cursor autocompletes, and inline chat sidebars—retained this exact mental model. The AI acted as a slightly smarter autocomplete, but the human remained the primary typist and runner of every micro-command.</p>
<p>However, writing syntax represents at most <strong>20% of the software engineering lifecycle</strong>. The remaining 80% is the hard part: clarifying ambiguous requirements, modeling architectural trade-offs, writing regression suites, conducting code reviews, managing CI/CD pipelines, enforcing security compliance, and triaging production incidents.</p>
<p>As explored in Port&#x27;s breakdown of the <strong>Agentic SDLC</strong> (<em>&quot;Agentic SDLC Explained for Developers!&quot;</em>), software engineering is undergoing an irreversible shift. Instead of treating AI as an interactive text editor plugin, modern engineering teams are structuring delivery around autonomous, multi-agent software pipelines.</p>
<p>Yet as autonomous agents begin generating code across whole repositories, a critical architectural question emerges: <strong>Where do Test-Driven Development (TDD) and Behavior-Driven Development (BDD) fit—and why are they no longer sufficient to govern this new reality?</strong></p>
<hr />
<h3>The Macro Pipeline: From PRD to Production</h3>
<p>In real-world software delivery, code does not materialize out of thin air. It traverses a structured, multi-stage funnel:</p>
<blockquote><p><strong>PRD</strong> &amp;rarr; <strong>System Design</strong> &amp;rarr; <strong>Architecture</strong> &amp;rarr; <strong>Low-Level Design (LLD)</strong> &amp;rarr; <strong>Implementation</strong> &amp;rarr; <strong>Tests</strong> &amp;rarr; <strong>Security</strong> &amp;rarr; <strong>Release</strong></p></blockquote>
<p>In an <strong>Agentic SDLC</strong>, the handoffs between these phases are executed by autonomous, specialized agents and guarded by deterministic evaluation checkpoints:</p>
<p><img src="https://elijah.mondero.nz/posts/images/agentic-sdlc-architecture.png" alt="The Agentic Software Development Lifecycle (Agentic SDLC) Architecture" /></p>
<h4>1. Specification &amp; Design Gate</h4>
<ul>
<li><strong>Input Artifact:</strong> Product Requirements Document (PRD) or User Stories.</li>
<li><strong>Autonomous Agent Action:</strong> Spec agents analyze user requirements, detect ambiguities, decompose epics into modular tasks, and flag edge cases.</li>
<li><strong>Evaluation Gate:</strong> Automated requirements completeness rubric (scoring clarity, testability, and scope).</li>
<li><strong>Human Checkpoint:</strong> Scope sign-off and architectural intent alignment.</li>
</ul>
<h4>2. Architecture &amp; Contract Gate</h4>
<ul>
<li><strong>Input Artifact:</strong> Approved PRD and Context Lake from Internal Developer Portals (IDPs).</li>
<li><strong>Autonomous Agent Action:</strong> Architecture agents evaluate existing service boundaries, database schemas, and architectural decision records (ADRs) to draft interface contracts.</li>
<li><strong>Evaluation Gate:</strong> ADR conformance rubric and interface contract linters.</li>
</ul>
<h4>3. Build &amp; Micro-Verification (The Factory Floor)</h4>
<ul>
<li><strong>Input Artifact:</strong> Low-Level Design (LLD) and task breakdown.</li>
<li><strong>Autonomous Agent Action:</strong> Subagent swarm implements code within isolated worktrees.</li>
<li><strong>Micro-Verification Loop (Where TDD/BDD Lives):</strong> Inner red-green-refactor loop generating unit tests and confirming execution evidence before committing.</li>
</ul>
<h4>4. Security &amp; Compliance Gate</h4>
<ul>
<li><strong>Input Artifact:</strong> Implemented code and passing test suites.</li>
<li><strong>Autonomous Agent Action:</strong> Security agents execute static analysis (SAST), dependency vulnerability scans (CVEs), and secret leak detection.</li>
<li><strong>Evaluation Gate:</strong> Deterministic security pass/fail gates and automated linting.</li>
</ul>
<h4>5. Release &amp; Continuous Operations Gate</h4>
<ul>
<li><strong>Input Artifact:</strong> Verified codebase, test evidence, and passing CI builds.</li>
<li><strong>Autonomous Agent Action:</strong> Automated Pull Request generation, diff impact analysis, canary deployment monitoring, and runtime telemetry triage.</li>
<li><strong>Evaluation Gate:</strong> Automated E2E verification suites, regression benchmarks, and policy compliance.</li>
<li><strong>Human Checkpoint:</strong> Strategic Pull Request review, architectural validation, and production release authorization.</li>
</ul>
<hr />
<h3>Why TDD and BDD Alone Don&#x27;t Fit the Macro Lifecycle</h3>
<p>When engineers first transition to AI coding agents, their instinctive reaction is to double down on <strong>Test-Driven Development (TDD)</strong> or <strong>Behavior-Driven Development (BDD)</strong>. After all, if an agent writes tests first, shouldn&#x27;t that guarantee correctness?</p>
<p>TDD and BDD remain vital, but they are <strong>micro-loop mechanisms</strong>, not macro lifecycle governance frameworks:</p>
<ul>
<li><strong>TDD/BDD Assumes Deterministic Code Written by Humans:</strong> TDD was designed for deterministic systems where a human reasons about an edge case, writes a failing assertion (<code>assert add(2, 2) == 4</code>), and writes the minimal code to satisfy it.</li>
<li><strong>The &quot;Passing Test&quot; Hallucination:</strong> In an agentic environment, an agent can effortlessly satisfy a local unit test while introducing catastrophic macro regressions. It might hardcode edge cases, violate global interface contracts, use deprecated APIs, or introduce quadratic performance loops that a unit test never catches.</li>
<li><strong>Micro vs. Macro Scope:</strong> BDD verifies whether a specific feature satisfies a given behavioral scenario (<em>&quot;Given a user is logged in, when they click...&quot;</em>). But BDD cannot answer: <em>Is this PRD aligned with our platform architecture? Does this Low-Level Design introduce state fragmentation? Is this PR architecturally sound?</em></li>
</ul>
<p>In short: <strong>TDD and BDD prevent syntax bugs at the micro level, but they cannot prevent architectural drift across the macro pipeline.</strong></p>
<hr />
<h3>The Paradigm Shift: Evaluation-Driven Development (EDD)</h3>
<p>To govern autonomous agents navigating the entire path from PRD to Release, the industry is adopting <strong>Evaluation-Driven Development (EDD)</strong>.</p>
<p>While TDD focuses on binary unit assertions (<code>pass</code> or <code>fail</code>), <strong>EDD treats evaluation, rubric measurement, and golden benchmarks as the primary steering system</strong> across every phase of the development lifecycle:</p>
<ul>
<li><strong>Operating Level:</strong></li>
<li><strong>TDD:</strong> Micro-level focus (individual functions, classes, and isolated modules).</li>
<li><strong>EDD:</strong> Macro-level governance (PRD clarity, architectural boundaries, LLD state management, and full-system release gates).</li>
</ul>
<ul>
<li><strong>Verification Logic:</strong></li>
<li><strong>TDD:</strong> Binary assertions (<code>assert x == y</code>).</li>
<li><strong>EDD:</strong> Multi-tiered evaluation combining deterministic assertions, static analysis, LLM judges, and objective rubric scoring.</li>
</ul>
<ul>
<li><strong>Execution Timing:</strong></li>
<li><strong>TDD:</strong> Executed locally right before writing implementation code.</li>
<li><strong>EDD:</strong> Codified upfront as acceptance rubrics before every phase transition (from spec to release).</li>
</ul>
<ul>
<li><strong>Handling of Drift:</strong></li>
<li><strong>TDD:</strong> Catches syntax regressions and broken logic in existing code.</li>
<li><strong>EDD:</strong> Catches behavioral drift, cognitive degradation, and architectural entropy across the multi-agent pipeline.</li>
</ul>
<h4>How EDD Operates Across the Enterprise Pipeline</h4>
<ol>
<li><strong>PRD Evaluation Gate:</strong> Before architecture work begins, an evaluator agent scores the PRD against a requirements rubric (measuring ambiguity, completeness, and non-functional requirements). A human signs off on the evaluated scope.</li>
<li><strong>Architecture &amp; LLD Evaluation Gate:</strong> Contract linters and ADR evaluators verify that proposed designs conform to system boundaries and security standards.</li>
<li><strong>Implementation &amp; Test Gate (Where TDD Lives):</strong> During implementation, the agent runs localized TDD loops inside isolated worktrees, generating unit tests and confirming execution evidence before claiming completion.</li>
<li><strong>Security &amp; Integration Gate:</strong> Automated security agents scan dependencies, run static analysis, and verify E2E integration against golden test suites.</li>
<li><strong>Human PR Gate:</strong> The Pull Request becomes the ultimate strategic human checkpoint. Instead of reading thousands of lines of raw diffs, human reviewers review the <strong>Evaluation Scorecard</strong>, the automated test proofs, and the architectural delta.</li>
</ol>
<hr />
<h3>Human-in-the-Loop vs. Human-on-the-Loop</h3>
<p>The Agentic SDLC does not eliminate developers; it reclaims their cognitive bandwidth.</p>
<p>When humans try to micromanage agents line-by-line in a chat window, they suffer severe fatigue and fall into &quot;vibes-based&quot; approvals—skimming code and clicking approve.</p>
<p>By replacing constant interruptions with <strong>strategic human gates powered by rubric evaluations</strong>, engineers transition from code typists to <strong>system architects</strong>:</p>
<ul>
<li><strong>Humans Set Intent &amp; Constraints:</strong> Framing the problem in the PRD and approving high-level architecture.</li>
<li><strong>Agents Execute the Factory Floor:</strong> Decomposing tasks, running TDD cycles, running static analysis, and updating documentation.</li>
<li><strong>Evals Filter the Noise:</strong> Automated rubrics ensure that work reaching human review has already passed rigorous multi-point verification.</li>
<li><strong>Humans Gate the Release:</strong> Giving final architectural sign-off on the Pull Request.</li>
</ul>
<hr />
<h3>The New Engineering Reality</h3>
<ol>
<li><strong>TDD is a Subsystem, Not the Strategy:</strong> Use TDD as an inner execution loop for agents writing code, but rely on EDD to govern the macro journey from PRD to production.</li>
<li><strong>Codify Success Criteria Upfront:</strong> If an agent cannot measure what &quot;good&quot; looks like through an objective rubric, it will drift into generic or brittle implementations.</li>
<li><strong>Leverage Context Lakes:</strong> Give agents live access to architecture decision records (ADRs), service catalogs, and API contracts via internal developer portals (like Port) to prevent hallucinated architecture.</li>
<li><strong>Make Pull Requests the True Governance Checkpoint:</strong> Build pipelines where PRs arrive with complete evaluation audit trails, leaving humans free to focus on architecture, business value, and safety.</li>
</ol>
<hr />
<h3>References &amp; Sources</h3>
<ul>
<li><strong>Port&#x27;s Video Breakdown:</strong> <a href="https://www.youtube.com/watch?v=21tuT-e4NVo">Agentic SDLC Explained for Developers! (YouTube 21tuT-e4NVo)</a></li>
<li><strong>Port Engineering:</strong> <a href="https://www.port.io/blog/agentic-sdlc">The Agentic Software Development Lifecycle</a></li>
<li><strong>CodeRabbit:</strong> <a href="https://www.coderabbit.ai/blog/agentic-sdlc-framework">Agentic SDLC Framework &amp; Verification</a></li>
<li><strong>Arize AI:</strong> <a href="https://arize.com/blog-course/eval-driven-development/">Evaluation-Driven Development (EDD) for AI Agents</a></li>
<li><strong>Martin Fowler / Thoughtworks:</strong> <a href="https://martinfowler.com/articles/exploring-gen-ai.html">Exploring Generative AI &amp; Software Delivery</a></li>
</ul>]]></content:encoded>
      <category>Agentic SDLC</category>
      <category>Evaluation-Driven Development</category>
      <category>Software Architecture</category>
      <category>TDD and BDD</category>
      <category>Multi-Agent Systems</category>
      <category>DevOps</category>
    </item>
    <item>
      <title>From Code to Cash: Mastering AI Development's Economic Equation</title>
      <link>https://elijah.mondero.nz/post/from-code-to-cash-mastering-ai-developments-econom/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/from-code-to-cash-mastering-ai-developments-econom/</guid>
      <pubDate>Mon, 01 Jun 2026 12:39:21 +0000</pubDate>
      <description>AI coding tools offer unparalleled speed in app development, but true success hinges not just on productivity, but on understanding token-based costs and selecting the right business model to ensure profitability. This post explores how individual builders to large enterprises are navigating the new economics of AI-powered software.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/6c9b8d1f-be4f-4da9-b9d1-24226d6e6a9b.png" alt="From Code to Cash: Mastering AI Development&#x27;s Economic Equation" /></p>
<h1>From Code to Cash: Mastering AI Development&#x27;s Economic Equation</h1>
<p>The landscape of software development is undergoing a seismic shift, driven by the rapid evolution of AI coding tools. From advanced AI agents like Claude to individual copilot solutions, these technologies promise unprecedented productivity, enabling even non-coders to build applications at speeds previously unimaginable. However, this revolution comes with a crucial caveat: skyrocketing development speed doesn&#x27;t automatically translate to profit. For anyone leveraging AI to build apps, understanding the complex interplay of token-based usage costs and strategic business models is paramount for turning innovation into sustainable success.</p>
<h2>The New Frontier of Builders: A Spectrum of AI Adoption</h2>
<p>AI has democratized app development, creating a diverse spectrum of builders:</p>
<ul>
<li><strong>Individual Developers &amp; Hobbyists:</strong> At one end, we find enthusiasts, often without formal coding backgrounds, who can now rapidly prototype and create custom applications for personal use or niche markets. Tools like OpenAI&#x27;s Codex allow a non-coder to build a functional Mac utility app in minutes, perfectly tailored to their needs, bypassing the limitations and ads of existing freemium options. For this group, AI offers speed and customization, often chosen over traditional outsourcing for bespoke solutions.</li>
</ul>
<ul>
<li><strong>Solo Founders &amp; Small Teams:</strong> Moving along, we see solo entrepreneurs and small teams building marketable applications without the hefty overhead of a large engineering department. They leverage AI to achieve the output of a &quot;mid-sized engineering team&quot; with just a few human overseers, increasingly opting out of traditional outsourcing routes in favor of a more direct, controllable, and faster AI-powered development pipeline.</li>
</ul>
<ul>
<li><strong>Companies &amp; Research Labs:</strong> At the forefront are companies and research labs deploying fully autonomous AI agents at immense scale. While these entities achieve groundbreaking feats in automated development, they also expose the significant and often hidden costs of running AI at full throttle.</li>
</ul>
<h2>The Cost Conundrum: Tokens and Your Bottom Line</h2>
<p>One of the most critical aspects for any AI-empowered builder is the financial model of these tools, particularly <strong>token-based usage</strong>. What begins as an exciting boost in productivity can quickly escalate into an overwhelming expense. The stark reality is illustrated by projects like OpenClaw, which racked up a staggering $1.3 million OpenAI API bill in a single month for operating 100 autonomous agents. Even after optimizing for &quot;standard&quot; pricing, the cost remained around $300,000 per month. This vividly demonstrates that for continuous, large-scale AI operations, token costs can easily surpass traditional labor expenses.</p>
<p>For individual developers and small businesses, this presents a significant challenge. While subscription-based copilots (like GitHub Copilot with 4.7 million paying users or Anthropic&#x27;s Claude Code achieving $1 billion in annualized revenue) offer more predictable costs for human-speed interaction, fully autonomous agents consume API calls at an exponentially higher rate. This can render flat-rate subscriptions economically unsustainable for both providers and users, as Anthropic discovered when blocking agent frameworks for some Claude Pro subscribers due to unmanageable compute demands.</p>
<h2>Blueprint for Profit: Business Models in the AI Age</h2>
<p>Understanding and adopting the right business model is crucial for transforming AI-driven productivity into profit. The current landscape of AI agent projects offers several paradigms:</p>
<ol>
<li><strong>Open-Source as Infrastructure (e.g., OpenClaw, Hermes Agent):</strong> These projects prioritize community adoption and ecosystem growth, often driving usage of underlying models or hardware. They typically lack a direct consumer revenue model, relying on sponsorship (like OpenAI covering OpenClaw&#x27;s costs) or serving as showcases for research labs&#x27; proprietary models. For independent developers, this means the tool itself might be free, but the underlying API calls will still incur costs.</li>
</ol>
<ol>
<li><strong>Subscription-First Agent-Workspace (e.g., Genspark):</strong> This model closely aligns with traditional Software-as-a-Service (SaaS). Companies like Genspark monetize through user seats and usage, proving that a well-defined subscription model can generate substantial annualized revenue (over $200 million for Genspark). Success here depends on the AI agent&#x27;s value justifying a recurring fee and effective management of internal AI usage costs.</li>
</ol>
<ol>
<li><strong>Traditional AI Coding Assistants (e.g., GitHub Copilot, Claude Code, Cursor):</strong> These widely adopted tools, while not always fully autonomous, represent highly successful commercial ventures focused on augmenting individual developer productivity. Their subscription models offer predictable pricing, balancing cost and value for millions of human coders.</li>
</ol>
<ol>
<li><strong>Specialized Solutions/Services:</strong> For individual developers and small teams, rather than aiming to build the next broad utility app (a market AI may increasingly commoditize), a highly effective model involves using AI tools to create specialized, custom solutions for clients. This shifts the focus from product sales to high-value service delivery, where AI tools boost efficiency, allowing for competitive pricing while maintaining healthy profit margins.</li>
</ol>
<h2>Navigating the Productivity-Profit Paradox</h2>
<p>The core challenge for many lies in bridging the gap between unprecedented development speed and sustainable profitability. While AI tools enable rapid development, they also introduce new complexities:</p>
<ul>
<li><strong>Increased Market Saturation:</strong> If everyone can build apps quickly, the market for simple, single-purpose applications becomes more crowded and harder to monetize, potentially eroding the traditional freemium model.</li>
<li><strong>&quot;AI Slop&quot; and Quality Concerns:</strong> Rapidly generated code can sometimes introduce bugs, security vulnerabilities, or simply inefficient &quot;slop&quot; that requires human review and correction, adding hidden costs and risks.</li>
<li><strong>Demand for Strategic Cost Management:</strong> Optimizing API calls, leveraging different pricing tiers (e.g., avoiding &quot;Fast Mode&quot; if not critical), and choosing the right models for specific tasks are essential skills for keeping token costs in check.</li>
</ul>
<h2>Conclusion</h2>
<p>AI is undeniably revolutionizing app development, empowering a diverse array of users to build applications with unparalleled speed. However, this revolution is not merely about increasing output; it&#x27;s profoundly about the business model itself. For individuals and small businesses looking to harness AI to build apps and bypass traditional outsourcing, understanding the true cost of token-based usage, carefully selecting a viable business model (whether SaaS, specialized services, or a hybrid approach), and strategically managing AI consumption are not optional – they are critical for transforming fast productivity into lasting profit. The future of app development is AI-powered, but only those who master the economic interplay of AI will truly succeed.</p>]]></content:encoded>
      <category>AI</category>
      <category>Artificial Intelligence</category>
      <category>AI Coding Tools</category>
      <category>Software Development</category>
      <category>App Development</category>
      <category>Productivity</category>
      <category>Profitability</category>
      <category>Business Models</category>
      <category>Token Costs</category>
      <category>OpenAI</category>
      <category>Claude</category>
      <category>GitHub Copilot</category>
      <category>SaaS</category>
      <category>Autonomous Agents</category>
      <category>Outsourcing</category>
      <category>Solo Founders</category>
      <category>Small Teams</category>
      <category>Tech Economy</category>
    </item>
    <item>
      <title>Unleashing Agility: How Micro Teams, AI, and Autonomy are Revolutionizing Software Engineering</title>
      <link>https://elijah.mondero.nz/post/unleashing-agility-how-micro-teams-ai-and-autonomy/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/unleashing-agility-how-micro-teams-ai-and-autonomy/</guid>
      <pubDate>Mon, 18 May 2026 17:56:31 +0000</pubDate>
      <description>Discover the transformative power of micro teams in software engineering, where small, self-sufficient pods, augmented by AI, are driving unprecedented agility, efficiency, and team morale by focusing on outcomes and embracing self-leadership.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/1e832a5b-a5fb-4bef-8d8e-606500491669.png" alt="Unleashing Agility: How Micro Teams, AI, and Autonomy are Revolutionizing Software Engineering" /></p>
<p>The landscape of software engineering is undergoing a profound evolution. We&#x27;re witnessing a clear trend towards smaller, more agile, and highly self-sufficient teams, often dubbed &quot;micro teams&quot; or &quot;pods.&quot; This shift isn&#x27;t just a fad; it&#x27;s a strategic move to boost efficiency, accelerate product delivery, and enhance team morale, challenging traditional, larger team structures and rigid hierarchies.</p>
<p>The core philosophy is simple: less is more. By embracing this approach, organizations are finding they can achieve greater operational efficiencies and make faster decisions, largely by stripping away unnecessary bureaucracy and time-consuming meetings.</p>
<h3>How Micro Teams Achieve Their Goals</h3>
<p>Micro teams thrive by prioritizing self-sufficiency and an unwavering focus on business outcomes. As highlighted in the article <a href="https://www.forbes.com/councils/forbestechcouncil/2025/05/15/enhancing-agility-and-throughput-in-the-ai-era-with-micro-teams/">&quot;Enhancing Agility And Throughput In The AI Era With Micro Teams&quot;</a> by Matthew Shilts, the sweet spot for these teams often hovers around three members. This &quot;rule of three&quot; strikes an optimal balance, ensuring redundancy, agility, and robust collaboration while preventing individuals from becoming isolated &quot;lone wolves.&quot;</p>
<p>Here&#x27;s how they make it work:</p>
<ul>
<li><strong>Self-Sufficiency and Cross-Functionality:</strong> Moving away from the &quot;assembly line development&quot; model where specialized teams handle specific parts (e.g., front-end, back-end), micro teams are designed to be self-sufficient. They possess the collective capability to handle various aspects of a feature from conception to delivery, end-to-end.</li>
<li><strong>AI Augmentation:</strong> A significant enabler for these smaller, autonomous teams is the rise of AI. AI-powered tools are critical in augmenting niche skills, automating tedious tasks, and bridging knowledge or experience gaps. This allows a three-person team to achieve the output and quality often associated with much larger scrum teams.</li>
<li><strong>Business Outcome Focus:</strong> Unlike teams defined by technological silos, effective micro pods directly link their work to specific business outcomes. This necessitates clear team charters outlining their mission, decision-making authority, and key success metrics. For instance, a pod dedicated to engagement might set customer retention as its top priority, with its entire backlog geared towards reducing churn. This direct alignment drives faster results and fosters heightened accountability.</li>
<li><strong>Reduced Bureaucracy and Meetings:</strong> The inherently smaller size of these teams naturally leads to fewer unnecessary meetings and quicker decision-making. This agility allows teams to adapt rapidly to evolving priorities. This principle resonates strongly with the idea that &quot;agents don&#x27;t do standups,&quot; implying that highly autonomous and communicative teams have less need for traditional, structured meetings. This is further supported by observations in <a href="https://www.forbes.com/sites/chriswestfall/2025/01/18/when-management-disappears-3-self-leadership-skills-for-your-career/">&quot;When Management Disappears: 3 Self-Leadership Skills For Your Career&quot;</a>, which notes that top results often emerge when management empowers teams to self-organize.</li>
</ul>
<h3>Skills Engineers Need to Thrive</h3>
<p>For engineers operating within micro teams, the demands extend beyond just technical prowess. Success in a self-directed environment requires a robust blend of technical expertise and strong soft skills:</p>
<ul>
<li><strong>Adaptability and Problem-Solving:</strong> Engineers must be highly adaptable to change and exceptionally skilled at problem-solving, as they&#x27;ll tackle diverse challenges without constant managerial oversight.</li>
<li><strong>Collaborative Mindsets:</strong> While autonomous, micro teams rely heavily on seamless collaboration and cooperation among their members.</li>
<li><strong>Self-Leadership and Personal Accountability:</strong> With fewer management layers, individuals must cultivate strong self-leadership, including proactively identifying choices and challenges, taking personal accountability, and being self-reliant.</li>
<li><strong>Persuasive Communication:</strong> The ability to communicate persuasively is vital, both for enrolling others in proposed actions and for fostering effective discourse within the team.</li>
<li><strong>Future-Proof Skill Sets:</strong> Continuous learning and developing versatile, &quot;future-proof&quot; skills are crucial for maintaining team effectiveness and resilience in a rapidly changing technological landscape.</li>
</ul>
<h3>The Evolving Role of Product Managers</h3>
<p>In an environment powered by micro teams, the role of product managers also transforms, shifting towards a more collaborative and less hierarchical dynamic:</p>
<ul>
<li><strong>Stronger Relationships with Delivery Teams:</strong> The reduction in layers between product managers and delivery teams naturally fosters much better communication. This direct line ensures a deeper, shared understanding of product requirements and delivery challenges.</li>
<li><strong>Workload Management for Lean Teams:</strong> Product managers face increased pressure to curate manageable workloads specifically tailored for leaner teams, ensuring that the focused, three-person pods can effectively deliver on their defined business outcomes.</li>
</ul>
<p>Ultimately, product managers become more integrated with their micro teams, operating as enablers and strategic partners rather than mere delegators.</p>
<h3>Other Roles in a Flattened Hierarchy</h3>
<p>The overarching theme of &quot;management disappearing&quot; and the emphasis on self-directed teams imply a significant flattening of traditional organizational hierarchies:</p>
<ul>
<li><strong>Reduced Traditional Management:</strong> The necessity for middle management layers diminishes as teams become increasingly self-organizing.</li>
<li><strong>Increased Individual Ownership:</strong> Every team member, regardless of their specific title, is expected to take on greater ownership and responsibility for their work and the team&#x27;s collective outcomes.</li>
<li><strong>Cross-Functional Expertise:</strong> There&#x27;s a push away from strict specialization towards fostering more cross-functional skill sets within the team. While AI augmentation helps fill specific niche knowledge gaps, a broader understanding remains valuable.</li>
</ul>
<h3>Achieved Outcomes: A New Era of Efficiency</h3>
<p>The successful implementation of micro teams, especially when augmented by AI, yields remarkable benefits that extend far beyond simple productivity gains:</p>
<ul>
<li><strong>Improved Efficiency and Accelerated Product Delivery:</strong> Smaller teams facilitate faster decision-making and significantly reduce organizational bureaucracy, leading to quicker development cycles and accelerated product releases.</li>
<li><strong>Boosted Overall Team Morale and Ownership:</strong> Leaner teams cultivate a greater sense of ownership, and the significant reduction in meeting frequency and duration is consistently cited as a major positive for team morale.</li>
</ul>
<ul>
<li><strong>Stronger Product-Manager Relationships:</strong> The closer proximity between product managers and delivery teams fosters superior communication and alignment, resulting in more cohesive product development.</li>
<li><strong>Faster Feedback Loops:</strong> Micro teams are inherently faster, enabling quicker iteration and more responsive reactions to feedback, perfectly aligning with the core principles of agile methodologies.</li>
<li><strong>Greater Empowerment and Accountability:</strong> Employees in self-directed teams experience enhanced empowerment, which translates into increased energy, passion, and individual accountability for achieving results.</li>
<li><strong>Reduced Churn:</strong> As an example, a three-person pod laser-focused on engagement can directly prioritize customer retention, leading to tangible reductions in customer churn.</li>
</ul>
<p>The shift to micro teams represents a significant cultural transformation for many organizations. It demands a re-evaluation of hiring practices to prioritize adaptability, problem-solving, and collaborative mindsets. However, for businesses striving for speed, agility, and innovation in the AI era, cultivating a culture of trust that empowers autonomous decision-making and leveraging AI to support these high-agency teams is proving to be an incredibly powerful strategy. The future of work is lean, agile, and AI-driven, and it&#x27;s here now.</p>]]></content:encoded>
      <category>Software Engineering</category>
      <category>Micro Teams</category>
      <category>Agile Development</category>
      <category>AI Augmentation</category>
      <category>Team Autonomy</category>
      <category>Self-Leadership</category>
      <category>Product Management</category>
      <category>Efficiency</category>
      <category>Innovation</category>
      <category>Future of Work</category>
    </item>
    <item>
      <title>Decoding AI Agents: Capabilities, Challenges, and a Call for Responsible Governance</title>
      <link>https://elijah.mondero.nz/post/decoding-ai-agents-capabilities-challenges-and-a-c/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/decoding-ai-agents-capabilities-challenges-and-a-c/</guid>
      <pubDate>Mon, 18 May 2026 11:01:44 +0000</pubDate>
      <description>AI agents are transforming how we work, excelling in defined tasks but still trailing human intuition in complex research. This post explores their impressive capabilities, the pitfalls of treating them like human employees, the urgent need for robust governance, and critical safety concerns as these autonomous systems rapidly integrate into our businesses.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/a23b4a5f-4beb-4caa-a95d-eff0f249c61c.png" alt="Decoding AI Agents: Capabilities, Challenges, and a Call for Responsible Governance" /></p>
<p>The landscape of Artificial Intelligence is rapidly evolving, ushering in an era dominated by <strong>AI agents</strong>. These aren&#x27;t just sophisticated algorithms; they are autonomous AI systems designed to perform specific tasks, often interacting with their environment, making decisions, and even learning over time. While their potential to reshape industries and redefine the future of work is immense, recent research highlights both their remarkable advancements and the significant challenges surrounding their integration and governance.</p>
<h2>AI vs. Human: Where Agents Shine (and Struggle)</h2>
<p>In well-defined and constrained problem domains, AI agents are demonstrating impressive capabilities. For instance, when presented with a clear coding problem and sufficient time, a top-tier AI agent can often match or even surpass the performance of skilled human engineers. This proficiency stems from their ability to process vast amounts of data, identify intricate patterns, and execute complex instructions with unparalleled efficiency.</p>
<p>However, this dynamic shifts when the task demands more open-ended, complex research, requiring extended periods of nuanced understanding, creative problem-solving, and the ability to navigate ambiguity. In such scenarios, human scientists and researchers still maintain a significant lead. Ultimately, this gap suggests that while AI agents excel in execution and optimization within defined parameters, they are yet to fully replicate the depth of human intuition, critical thinking, and adaptive reasoning in novel situations.</p>
<h2>Integrating AI: Employee or Tool? (And Why It Matters)</h2>
<p>As AI agents grow more sophisticated, organizations are exploring their integration into various business operations. Some even go so far as to conceptualize them as &quot;employees&quot; on organizational charts. While this might seem like an efficient way to streamline workflows, new research indicates potential unintended consequences.</p>
<p>Anthropomorphizing AI agents – treating them too much like human employees – can paradoxically lead to a reduction in individual accountability within human teams. This finding underscores the critical need for careful consideration of how AI agents are framed and managed within human-centric organizational structures, ensuring they augment rather than dilute human responsibility.</p>
<h2>The Governance Gap: A Ticking Time Bomb</h2>
<p>Beyond integration, a significant and urgent concern is the governance of these increasingly powerful agents. Reports indicate that AI agents are rapidly entering critical business operations, often without sufficient oversight or established governance frameworks. This lack of governance can lead to unforeseen risks, security vulnerabilities, and ethical dilemmas. It highlights the pressing need for robust policies, transparent controls, and clear accountability mechanisms to manage their deployment and operation responsibly.</p>
<h2>The Cutting Edge: Next-Gen AI Agents</h2>
<p>Technological advancements continue to push the boundaries of what AI agents can achieve. Google, for example, has unveiled its &quot;Deep Research&quot; and &quot;Deep Research Max&quot; agents, powered by Gemini 3.1 Pro. These advanced agents are designed to automate high-stakes research workflows by combining web search capabilities with access to proprietary enterprise data, specialized integrations, and native charting tools. Such developments signify a move towards highly specialized agents capable of performing complex, data-intensive tasks previously exclusive to human experts.</p>
<h2>Beyond Efficiency: Understanding the Risks</h2>
<p>Despite their immense potential, AI agents pose considerable risks that demand meticulous attention. A critical study has revealed that AI agents designed to automate tasks may pursue their objectives without fully recognizing or understanding the potentially dangerous consequences of their actions. This disconnect between efficient task completion and a comprehensive understanding of real-world implications raises serious safety concerns, particularly in sensitive or high-impact applications. Ensuring that AI agents are not only efficient but also operate within ethical boundaries and with a robust understanding of safety protocols is paramount for their responsible development and deployment.</p>
<h2>Conclusion</h2>
<p>The field of AI agents is evolving at an unprecedented pace, promising to reshape industries and redefine the very nature of work. While they offer unparalleled potential for automation and efficiency, their successful and responsible integration hinges on addressing critical challenges. These include understanding their limitations compared to human cognition, navigating the complexities of organizational integration, and, most importantly, establishing robust governance and safety mechanisms. As these intelligent systems become more pervasive, a balanced approach that leverages their strengths while diligently mitigating their risks will be essential for harnessing their full transformative power.</p>]]></content:encoded>
      <category>AI Agents</category>
      <category>Artificial Intelligence</category>
      <category>Future of Work</category>
      <category>AI Governance</category>
      <category>AI Safety</category>
      <category>Business Automation</category>
      <category>Machine Learning</category>
      <category>Digital Transformation</category>
      <category>Organizational AI</category>
    </item>
    <item>
      <title>From .NET to Reactive Java: My Agentic Journey to High-Quality Software</title>
      <link>https://elijah.mondero.nz/post/from-net-to-reactive-java-my-agentic-journey-to-hi/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/from-net-to-reactive-java-my-agentic-journey-to-hi/</guid>
      <pubDate>Sat, 16 May 2026 08:04:54 +0000</pubDate>
      <description>Discover how a seasoned .NET developer leveraged agentic coding, specifically with an AI co-pilot, to successfully build a complex Java/React application using Spring Boot, WebFlux, OpenTelemetry, and more. This journey redefines the SDLC, showcasing how AI partnership accelerates learning and delivers high-quality software.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/eff471aa-4da5-46fe-8986-4ef3c2caade3.png" alt="From .NET to Reactive Java: My Agentic Journey to High-Quality Software" /></p>
<p>For years, my development world as a .NET developer revolved around Microsoft&#x27;s familiar syntax and robust ecosystem. However, the rapidly evolving software landscape continually beckons with new paradigms and technologies. Recently, I embarked on an ambitious journey: to build my inaugural application in Java and React, harnessing the full power of Spring Boot, OpenTelemetry, WebFlux, R2DBC, MySQL, Server-Sent Events (SSE), and WebSockets.</p>
<p>This wasn&#x27;t merely a language switch; it was a profound immersion into reactive programming, distributed tracing, and real-time communication. What made this daunting leap not only manageable but profoundly insightful was the invaluable assistance of &quot;agentic coding&quot; – specifically, my AI co-pilot, Claude.</p>
<p>This experience profoundly reshaped my understanding of the Software Development Life Cycle (SDLC). We&#x27;re moving beyond mere code completion; we&#x27;re entering an era where AI agents become integral partners throughout the entire development process, fundamentally redefining the &quot;new SSDLC&quot; for achieving truly high-quality software.</p>
<h3>The Agentic Leap: My Co-Pilot for a New Ecosystem</h3>
<p>&quot;Agentic coding&quot; transcends the role of a simple intelligent assistant; it represents an AI agent capable of reasoning, planning, and executing complex tasks, thereby empowering developers to navigate intricate domains. For me, stepping into the Java/React world felt akin to simultaneously learning a new language and culture. While many concepts have counterparts in the .NET ecosystem, the implementation details, libraries, and community idioms are distinctly different. This is precisely where my agent truly excelled.</p>
<p>Claude rapidly became my indispensable research assistant and conceptual bridge. Whenever I grappled with the intricacies of Spring Boot&#x27;s configuration, the nuances of WebFlux&#x27;s reactive streams, or the setup for OpenTelemetry&#x27;s distributed tracing, I turned to the agent. It didn&#x27;t merely furnish answers; it helped me grasp <em>why</em> certain patterns were preferred, drew insightful parallels to my existing .NET knowledge, and even suggested optimal best practices for integrating these nascent technologies. This wasn&#x27;t about the AI generating all the code, but rather about it profoundly augmenting my learning, accelerating my research, and empowering me to make well-informed architectural decisions within an entirely new stack.</p>
<h3>Embracing the Reactive Revolution: Spring Boot, WebFlux, and R2DBC</h3>
<p>My new application demanded high responsiveness and scalability, naturally leading me towards reactive programming. While Spring Boot provided a robust foundation, the true paradigm shift arrived with Spring WebFlux. This framework seamlessly ushered me into the world of non-blocking, event-driven architectures, marking a significant departure from traditional imperative programming. The advantages are compelling: superior resource utilization and enhanced resilience, especially under heavy load.</p>
<p>To complement this, I integrated R2DBC (Reactive Relational Database Connectivity) with MySQL. R2DBC offers a non-blocking API for interacting with relational databases, perfectly aligning with WebFlux&#x27;s reactive principles. This powerful combination ensured that my entire data access layer remained asynchronous, effectively preventing bottlenecks and preserving the reactive flow throughout the application. OpenTelemetry, meanwhile, proved indispensable for gaining visibility into this reactive maze. It enabled me to instrument the application for distributed tracing, metrics, and logs, providing the deep observability necessary to comprehend how requests traversed the system and to precisely pinpoint performance issues, even across disparate services.</p>
<p>Navigating these interconnected and often intricate reactive paradigms would undoubtedly have been a far steeper curve without the constant support of my agent. It served as an invaluable reference, explaining cryptic error messages, suggesting optimal data flow patterns, and elucidating the subtle distinctions between <code>Mono</code> and <code>Flux</code>.</p>
<h3>Real-Time Engagement: SSE and WebSockets</h3>
<p>Modern web applications increasingly demand real-time interaction. For my project, I strategically employed both Server-Sent Events (SSE) and WebSockets to address distinct real-time communication requirements.</p>
<p>SSE, a notably simpler protocol, proved ideal for one-way, server-to-client communication. It excels in scenarios like live score updates, stock tickers, or notification feeds, where the client primarily subscribes to and receives continuous updates from the server. Its efficiency and lower resource footprint make it a strong choice for these specific use cases.</p>
<p>WebSockets, conversely, enabled robust full-duplex, bidirectional communication. This capability was perfectly suited for highly interactive elements such as chat functionalities or collaborative tools, where both the client and server need to send and receive messages asynchronously and frequently. Discerning when to apply each technology for optimal performance and resource utilization was yet another complex area where my agent provided invaluable clarity, offering detailed insights into their respective strengths and limitations.</p>
<h3>Fortifying Quality with Testcontainers and the New SDLC</h3>
<p>Crucially, the pursuit of &quot;good quality software&quot; extends far beyond elegant code; it fundamentally hinges on robust testing. This is precisely where Testcontainers emerged as an indispensable tool. Testcontainers provisions lightweight, throwaway instances of databases, message brokers, web browsers, or virtually any service that can run within a Docker container, specifically for testing purposes. This capability allowed me to execute my integration tests against a <em>real</em> MySQL instance, fully isolated and consistent, eliminating the overhead of managing local installations or shared test environments.</p>
<p>Integrating Testcontainers into my Spring Boot application, particularly with an R2DBC setup, demanded a thorough understanding of its lifecycle and proper integration into the build process. My agent proved instrumental, helping me locate relevant examples, comprehend configuration options, and troubleshoot initial setups, thereby ensuring my tests were both comprehensive and highly reliable. This proactive approach to testing, integrated early and effectively, is a cornerstone of the &quot;new SSDLC,&quot; where quality is meticulously baked in from the very outset, rather than being an afterthought.</p>
<h3>The Future is Agentic: A New Paradigm for Software Excellence</h3>
<p>My recent journey, transitioning from a seasoned .NET developer to building a sophisticated Java/React application incorporating a suite of cutting-edge technologies—all while profoundly guided by an AI agent—has been nothing short of transformative. Agentic coding is unequivocally not a passing fad; it represents a fundamental paradigm shift in how we approach software development. It empowers developers to assimilate new technologies more rapidly, explore complex architectural landscapes with significantly greater confidence, and ultimately, engineer higher-quality software more efficiently and effectively.</p>
<p>For me, this complex transition felt less like a daunting struggle and more like an exhilarating, accelerated learning expedition, thanks entirely to my agentic co-pilot. It is undeniably an exciting era to be a developer, where our inherent intelligence is powerfully augmented, our technical reach is vastly extended, and the pathway to crafting truly exceptional software is clearer and more accessible than ever before. The future of the SDLC is inherently collaborative, intelligently driven, and, without a doubt, profoundly agentic.</p>]]></content:encoded>
      <category>Agentic Coding</category>
      <category>AI Co-pilot</category>
      <category>SDLC</category>
      <category>Software Quality</category>
      <category>Java</category>
      <category>React</category>
      <category>Spring Boot</category>
      <category>WebFlux</category>
      <category>Reactive Programming</category>
      <category>R2DBC</category>
      <category>MySQL</category>
      <category>OpenTelemetry</category>
      <category>Distributed Tracing</category>
      <category>SSE</category>
      <category>WebSockets</category>
      <category>.NET Developer</category>
      <category>Testcontainers</category>
      <category>Modern Development</category>
    </item>
    <item>
      <title>Beyond Code Generation: How Claude Code, MCP, and Plugins Are Revolutionizing AI Development Through Context</title>
      <link>https://elijah.mondero.nz/post/beyond-code-generation-how-claude-code-mcp-and-plu/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/beyond-code-generation-how-claude-code-mcp-and-plu/</guid>
      <pubDate>Wed, 06 May 2026 08:13:19 +0000</pubDate>
      <description>The landscape of AI development is rapidly shifting from simple code generation to sophisticated, agentic systems. This post explores how Anthropic's Claude Code, powered by innovations like the Model Context Protocol (MCP), Command Line Interfaces (CLI), and robust plugin architecture, is leading this charge by prioritizing persistent context and autonomous capabilities.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/b913048a-19fd-4d3a-a41a-ef5eb520ad96.png" alt="Beyond Code Generation: How Claude Code, MCP, and Plugins Are Revolutionizing AI Development Through Context" /></p>
<p>The world of AI-driven development is undergoing a profound transformation, moving beyond basic code generation towards building sophisticated, &quot;agentic&quot; AI systems that can maintain understanding, automate complex tasks, and integrate seamlessly into existing environments. At the heart of this evolution is the critical concept of <strong>context management</strong> – how AI models retain and utilize relevant information across multiple interactions.</p>
<p>Let&#x27;s dive into how tools like Anthropic&#x27;s Claude Code, alongside key innovations such as the Model Context Protocol (MCP), Command Line Interfaces (CLI), and a burgeoning plugin ecosystem, are defining this new era.</p>
<h3>Claude Code: More Than Just a Coder</h3>
<p>Anthropic&#x27;s Claude Code is an AI-powered coding tool designed to optimize and accelerate the AI development workflow. It&#x27;s not merely a code generator; it&#x27;s an expansive ecosystem. Recent integrations, like those seen with VS Code, demonstrate a broader trend: development environments are adapting to accommodate Claude-specific instruction files and methodologies, cementing its growing importance in the developer toolkit.</p>
<h3>The Skills of Claude: Mastering Context and Automation</h3>
<p>Claude&#x27;s true prowess lies in its ability to facilitate smarter development through sophisticated context management. Its &quot;skills&quot; extend far beyond basic coding assistance. This includes techniques for optimizing AI development workflows, from efficient token usage to enabling advanced parallel agent teams. The emphasis here is squarely on enabling the AI to <strong>retain and utilize relevant information across multiple interactions and tasks</strong>. This &quot;saving context&quot; is paramount for building more coherent and intelligent systems, drastically reducing the need for constant re-prompting and significantly improving overall efficiency.</p>
<h3>Model Context Protocol (MCP): The Engine of Agentic AI</h3>
<p>A significant innovation within the Claude ecosystem is the <strong>Model Context Protocol (MCP)</strong>. This protocol is a game-changer, designed to transform Claude Code into a powerful AI agent capable of automating complex workflows. MCP allows Claude to interact with external systems, perform tasks like web automation, and manage databases.</p>
<p>At its core, MCP provides a structured way for the AI to understand and maintain context across diverse operations. By defining how the AI interacts with various tools and data sources, MCP acts as a blueprint for building truly autonomous and intelligent agents. These agents can remember past actions, understand ongoing goals, and adapt to new information, directly addressing the challenge of &quot;saving context&quot; by establishing a framework for persistent operational understanding.</p>
<h3>The Power of CLI and Plugin Architecture: Extending Capabilities</h3>
<p>The increasing reliance on Command Line Interfaces (CLI) for interacting with AI models, exemplified by Gemini&#x27;s CLI and the plugin features in Claude Code, signals a clear trend towards flexible and extensible AI tools. CLI offers developers a direct, efficient, and scriptable interface, allowing for seamless integration into existing development pipelines and automation scripts.</p>
<p>Furthermore, the emphasis on &quot;plugin making&quot; is a revolutionary step. Claude Code&#x27;s plugin features, along with similar offerings from competitors like OpenAI&#x27;s Codex, allow developers to extend the AI&#x27;s capabilities far beyond its initial scope. Plugins serve as custom tools and integrations that enhance the AI&#x27;s ability to perform specific tasks, access external data, and interact with various services. This modular approach is intrinsically linked to context management; each plugin can introduce its own context or leverage the existing operational context provided by MCP, further enriching the AI&#x27;s understanding and capabilities. This empowers developers to tailor their AI agents to highly specific use cases while maintaining a consistent and coherent operational context.</p>
<h3>The Shifting Consensus: Towards Persistent Context and Agentic Intelligence</h3>
<p>The confluence of Claude Code&#x27;s advanced capabilities, the Model Context Protocol, versatile CLI interactions, and robust plugin architectures points to an undeniable shift in the AI development paradigm. The industry consensus is firmly moving towards:</p>
<ul>
<li><strong>Persistent Context:</strong> The ability for AI models to not only understand immediate prompts but also to maintain a long-term, dynamic understanding of ongoing projects, user preferences, and past interactions. This &quot;saving context&quot; is paramount for building truly intelligent and helpful AI assistants.</li>
<li><strong>Agentic AI:</strong> Developing AI systems that can act autonomously, take initiative, and execute complex, multi-step tasks without constant human intervention. MCP is a prime example, enabling Claude Code to function as an independent agent.</li>
<li><strong>Extensibility and Customization:</strong> The demand for AI tools that can be easily extended and customized through plugins and integrations, allowing developers to tailor AI behavior to their specific needs and integrate them into diverse workflows.</li>
<li><strong>Security by Design:</strong> As AI tools become more integrated into critical development workflows, the importance of robust security measures is paramount. Past vulnerabilities in Claude Code underscore the necessity for &quot;security by design&quot; to protect developers&#x27; machines and data.</li>
</ul>
<p>In conclusion, the evolution of tools like Claude Code, driven by innovations such as the Model Context Protocol, the efficiency of CLI, and the flexibility of plugins, is ushering in a new era of AI-powered development. This era is characterized by an unwavering focus on managing and leveraging context, enabling the creation of more intelligent, autonomous, and seamlessly integrated AI agents that promise to redefine how we build and interact with software.</p>]]></content:encoded>
      <category>AI Development</category>
      <category>Claude Code</category>
      <category>Anthropic</category>
      <category>Agentic AI</category>
      <category>Context Management</category>
      <category>Model Context Protocol</category>
      <category>MCP</category>
      <category>CLI</category>
      <category>Plugins</category>
      <category>AI Workflow</category>
      <category>Software Development</category>
    </item>
    <item>
      <title>The AI Revolution in Software Engineering: From Coder to Orchestrator</title>
      <link>https://elijah.mondero.nz/post/the-ai-revolution-in-software-engineering-from-cod/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/the-ai-revolution-in-software-engineering-from-cod/</guid>
      <pubDate>Mon, 04 May 2026 01:53:32 +0000</pubDate>
      <description>The landscape of software engineering is rapidly transforming with AI coding, shifting the developer's role from writing code to managing intelligent agents. Discover how human expertise remains crucial, how 'micro teams' are redefining productivity, and how AI is accelerating product delivery to unprecedented levels.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/c129f593-06f0-4139-a4a5-dd5eb6f55c9a.png" alt="The AI Revolution in Software Engineering: From Coder to Orchestrator" /></p>
<p>The software engineering world is undergoing an exhilarating and profound transformation. The rise of AI coding is not just automating tasks; it&#x27;s fundamentally redefining the role of the developer, moving us into an era where human ingenuity is amplified by intelligent agents. If you&#x27;re a software engineer, or managing a team in this space, get ready for a significant shift: from being a primary coder to becoming a strategic orchestrator of AI.</p>
<h2>The Evolving Role: From Crafter to Conductor</h2>
<p>The days when writing lines of code was the chief bottleneck in the software development lifecycle are fast becoming a distant memory. AI coding agents are already generating a substantial portion of code—often 60% to 80% in many enterprises, and astonishingly, up to 97.3% internally at leading AI companies. This dramatic change means our core responsibility as developers is no longer just <em>crafting</em> code, but rather <strong>supervising, constraining, and reasoning about AI-generated code.</strong></p>
<p>We are no longer merely &quot;crafters of code&quot;; we are becoming <strong>orchestrators of intelligent agents</strong>. This new role demands a refined, strategic skill set:</p>
<ul>
<li><strong>Prompt Engineering:</strong> The art of effectively communicating with AI agents to guide precise code generation.</li>
<li><strong>Agent Behavior Understanding:</strong> Comprehending how AI agents operate, their capabilities, and, crucially, their limitations.</li>
<li><strong>Reliability and Failure Analysis:</strong> Proactively identifying potential risks and understanding the failure modes of AI-generated output.</li>
<li><strong>Debugging and Evaluation:</strong> Proficiently debugging AI agents and rigorously evaluating the quality and relevance of their results.</li>
<li><strong>Data Literacy, Safety, and Security:</strong> A strong grasp of data principles, security best practices, and ethical considerations inherent in AI-driven development.</li>
<li><strong>System Orchestration:</strong> Managing and coordinating multiple AI agents in parallel within complex cloud environments.</li>
</ul>
<p>Embracing an &quot;AI-first&quot; approach and training on higher levels of abstraction, such as model-based software development, is no longer optional; it&#x27;s a fundamental shift in mindset.</p>
<h2>The Enduring Vitality of Human Expertise: Knowledge Base and Infrastructure</h2>
<p>Despite the increasing autonomy of AI agents, the human element—the &quot;crafters of code&quot; of the past—remain more vital than ever. Why? Because AI agents, while powerful, lack true comprehension and contextual understanding without human guidance. Our deep-seated knowledge of existing codebases, architectural patterns, business logic, and operational nuances is indispensable for:</p>
<ul>
<li><strong>Training and Fine-tuning:</strong> Providing the high-quality data and feedback necessary to train AI models, ensuring they generate accurate and relevant code that aligns with our specific needs.</li>
<li><strong>Establishing Standards:</strong> Defining the coding standards, best practices, and architectural principles that AI agents <em>must</em> adhere to.</li>
<li><strong>Contextual Understanding:</strong> Imbuing agents with the necessary context about complex systems, dependencies, and potential risks that only human experience and intuition can provide.</li>
<li><strong>Infrastructure Knowledge:</strong> As AI agents become deeply integrated into enterprise platforms like Microsoft Fabric and AWS Bedrock AgentCore, they rely heavily on robust cloud infrastructure. Developers with expertise in these areas are crucial for ensuring agents are deployed, managed, and operate efficiently within our existing technological landscape. This includes understanding CI/CD pipelines, deployment strategies, monitoring tools, and security protocols, all of which become critical as the volume of AI-generated code escalates.</li>
</ul>
<p>Our historical knowledge and understanding of the underlying infrastructure are the bedrock upon which AI agents can effectively build and operate.</p>
<h2>The Rise of Micro Teams and Accelerated Product Delivery</h2>
<p>The advent of AI coding agents is ushering in an exciting new organizational model: the &quot;micro team.&quot; Imagine a team of just two human developers, augmented by a dedicated team of AI agents. In this setup, human developers transcend traditional coding, acting instead as strategic managers and architects, leveraging AI agents to handle much of the repetitive code generation and even proactive bug detection.</p>
<p>This powerful synergy leads to an unprecedented acceleration in product feature delivery:</p>
<ul>
<li><strong>Faster Code Generation:</strong> With AI handling 60-80% of the code, the time spent on initial coding is drastically reduced, allowing teams to move faster than ever before.</li>
<li><strong>Shifted Bottlenecks:</strong> The primary bottlenecks are no longer coding itself, but rather critical stages like planning, design, testing, and review—areas where human creativity, critical thinking, and validation are paramount. By optimizing these processes, the overall development cycle can be streamlined significantly.</li>
<li><strong>Increased Throughput:</strong> Companies embracing AI coding tools are reporting double the pull request throughput compared to those with low adoption, indicating a substantial boost in development velocity.</li>
<li><strong>Proactive Quality Assurance:</strong> AI-powered tools can proactively identify and resolve up to 60% of bugs and quality issues <em>as code is being written</em>, building confidence and sustaining rapid development by preventing problems before they grow.</li>
</ul>
<p>In essence, the new age of software engineering with AI coding positions developers not as obsolete relics, but as empowered orchestrators, strategic thinkers, and crucial knowledge guardians. Our ability to guide, validate, and manage AI agents, coupled with our deep infrastructure and domain knowledge, will be the true differentiator for companies seeking to deliver innovative products at an unprecedented pace. The future of software engineering is collaborative, intelligent, and, most importantly, human-centric, with AI acting as a powerful amplifier of our ingenuity.</p>]]></content:encoded>
      <category>AI in Software Engineering</category>
      <category>Developer Role</category>
      <category>AI Coding</category>
      <category>Micro Teams</category>
      <category>Product Delivery</category>
      <category>Prompt Engineering</category>
      <category>System Orchestration</category>
      <category>Infrastructure Knowledge</category>
      <category>Future of Tech</category>
    </item>
    <item>
      <title>DeepSeek OCR: Compressing Vision, Expanding Insights – A New Era for Document Processing</title>
      <link>https://elijah.mondero.nz/post/deepseek-ocr-compressing-vision-expanding-insights-a-new-era-for-document-processing/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/deepseek-ocr-compressing-vision-expanding-insights-a-new-era-for-document-processing/</guid>
      <pubDate>Thu, 23 Oct 2025 20:25:01 +0000</pubDate>
      <description>DeepSeek OCR introduces a groundbreaking approach to document processing, leveraging 'advanced visual-text compression.' This isn't about shrinking file sizes; it's about intelligently transforming complex visual document information into structured, semantic data. Discover how this innovative technology revolutionizes text extraction and document understanding.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/b24c4d9d-8573-4e00-81aa-3661822f157b.png" alt="DeepSeek OCR: Compressing Vision, Expanding Insights – A New Era for Document Processing" /></p>
<p>Optical Character Recognition (OCR) has long been a cornerstone of digital document processing, primarily converting text images into machine-readable characters. However, DeepSeek OCR is revolutionizing this landscape with a powerful new concept: <strong>advanced visual-text compression</strong>. This innovative technology goes far beyond simple character recognition, aiming to extract the full semantic meaning and inherent structure from visual documents.</p>
<h3>Understanding &#x27;Visual-Text Compression&#x27; in DeepSeek OCR</h3>
<p>DeepSeek OCR&#x27;s &#x27;visual-text compression&#x27; requires a clear understanding. It&#x27;s <em>not</em> about reducing the file size of an image or a document. Instead, it&#x27;s a sophisticated method for intelligently and efficiently <strong>extracting and representing the meaningful textual and structural information</strong> contained within a visual document. Essentially, DeepSeek OCR &#x27;compresses&#x27; the complex visual data of a document into a structured, semantic representation, often outputting it in markdown format. This process involves a deep understanding of both the visual layout and the textual content, creating actionable insights from raw visual input.</p>
<h3>The Engineering Behind the Breakthrough</h3>
<p>DeepSeek OCR achieves this remarkable feat through a combination of cutting-edge technologies:</p>
<ol>
<li><strong>Dynamic Tiling Vision Encoding:</strong> Imagine an intelligent eye that knows precisely where to focus. This technology allows DeepSeek OCR to analyze documents with adaptive resolutions, ranging from 512px to 1280px. By dynamically adjusting its resolution, the system meticulously analyzes layout structures and text patterns. This ensures that even the most minute or complex details are preserved and understood, all while maintaining impressive computational efficiency.</li>
</ol>
<ol>
<li><strong>Multi-Resolution Processing Modes:</strong> Building on its dynamic vision capabilities, DeepSeek OCR employs flexible token allocation (from 64 to 400 tokens) across various processing modes: Tiny, Small, Base, and Large. These modes are designed to extract detailed text features and structural information, capturing the inherent semantics of the document. This deep contextual understanding enables &#x27;contextually aware markdown conversion,&#x27; ensuring the output retains the original formatting and hierarchy, not just the raw text.</li>
</ol>
<ol>
<li><strong>A Powerful 3 Billion Parameter Model Architecture:</strong> At the core of DeepSeek OCR is an extensive 3-billion-parameter model. This robust architecture is engineered to independently process both text recognition and layout understanding. This dual-focus approach is critical to the &#x27;visual-text compression&#x27; philosophy, leading to significantly more accurate document extraction and formatting. The system doesn&#x27;t merely identify characters; it comprehends how they are organized and relate to each other within the document&#x27;s visual space.</li>
</ol>
<h3>Transforming Documents into Structured Insights</h3>
<p>The benefits of DeepSeek OCR&#x27;s advanced visual-text compression are transformative for document intelligence:</p>
<ul>
<li><strong>Exceptional Efficiency and Accuracy:</strong> By intelligently focusing on relevant visual and textual data, DeepSeek OCR achieves high accuracy in text extraction while maintaining efficient processing, surpassing traditional methods.</li>
<li><strong>Structured Output:</strong> Documents are not just scanned; they are reborn as structured markdown. This makes the extracted data immediately usable for further processing, analysis, and seamless integration into various digital systems and workflows.</li>
<li><strong>Scalability for Long Documents:</strong> The technology is particularly adept at handling ultra-long texts, making it an ideal solution for large-scale document processing tasks, from legal briefs to research papers.</li>
<li><strong>High Throughput:</strong> DeepSeek OCR boasts impressive processing speeds, capable of handling over 200,000 pages daily on a single NVIDIA A100 GPU, offering significant operational efficiency.</li>
<li><strong>Multilingual Support:</strong> With advanced capabilities spanning more than 20 languages, including both printed and handwritten notes, DeepSeek OCR ensures consistent and high-quality text extraction from diverse global documents.</li>
</ul>
<p>In conclusion, DeepSeek OCR&#x27;s &#x27;visual-text compression&#x27; represents a significant leap forward in document processing. By intelligently extracting and semantically representing the rich information within visual documents, it transforms raw images into actionable, structured data, ushering in a new era of document intelligence.</p>]]></content:encoded>
      <category>DeepSeek OCR</category>
      <category>OCR</category>
      <category>Document Processing</category>
      <category>Visual-Text Compression</category>
      <category>AI</category>
      <category>Machine Learning</category>
      <category>Text Extraction</category>
      <category>Document Intelligence</category>
      <category>Markdown Conversion</category>
      <category>Dynamic Tiling</category>
      <category>Multilingual OCR</category>
    </item>
    <item>
      <title>The Rise of Tiny AI: TRM Redefines Efficient Reasoning for Complex Puzzles</title>
      <link>https://elijah.mondero.nz/post/the-rise-of-tiny-ai-trm-redefines-efficient-reasoning-for-complex-puzzles/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/the-rise-of-tiny-ai-trm-redefines-efficient-reasoning-for-complex-puzzles/</guid>
      <pubDate>Thu, 23 Oct 2025 10:26:14 +0000</pubDate>
      <description>Discover how the Tiny Recursive Model (TRM), a streamlined successor to the Hierarchical Reasoning Model (HRM), is revolutionizing complex reasoning in AI. Operating with a fraction of the parameters of large language models, TRM delivers superior performance and efficiency, proving that sometimes, less truly is more.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/1592676e-f902-4cad-8225-20990f8d1b6a.png" alt="The Rise of Tiny AI: TRM Redefines Efficient Reasoning for Complex Puzzles" /></p>
<p>In the fast-paced world of artificial intelligence, the pursuit of models capable of tackling complex reasoning tasks with both efficiency and accuracy is a monumental challenge. Enter the Hierarchical Reasoning Model (HRM) and its impressive successor, the Tiny Recursive Model (TRM). These models are making significant waves, particularly in their ability to solve intricate puzzles that often stump even the largest language models (LLMs).</p>
<h3>Hierarchical Reasoning Model (HRM): A Biologically Inspired Start</h3>
<p>The journey began with the Hierarchical Reasoning Model (HRM), a novel approach to complex reasoning inspired by the sophisticated networks of human and animal brains. HRM ingeniously employed two small neural networks, recurring at different frequencies, to perform its computations. Its core innovation was <strong>deep supervision</strong>, a technique that allowed the model to iteratively refine its answers. By reusing past computations, HRM could adjust and self-correct its reasoning process over multiple steps, much like a person reviewing their work.</p>
<p>This recursive methodology enabled HRM to mimic the reasoning depth typically found in much larger networks, but crucially, without the heavy computational burden of backpropagating through countless layers. HRM showcased remarkable performance on challenging puzzle tasks such as Sudoku, Maze navigation, and ARC-AGI. It often outshone LLMs, despite being trained with a mere 27 million parameters and approximately 1000 examples—a tiny footprint by comparison.</p>
<p>However, independent analyses later revealed a pivotal insight: the true power of HRM didn&#x27;t lie in its complex hierarchical structure or elaborate recursion, but predominantly in the <strong>iterative improvement</strong> facilitated by deep supervision. This understanding paved the way for a simpler, yet even more effective, successor.</p>
<h3>Tiny Recursive Model (TRM): Less is More, Smarter is Better</h3>
<p>Building on the foundational insights gleaned from HRM, researchers at Samsung AI Lab developed the <strong>Tiny Recursive Model (TRM)</strong>. TRM embodies the philosophy of &quot;less is more,&quot; presenting a profoundly effective, yet much simpler, recursive reasoning approach. Unlike HRM&#x27;s dual-network, hierarchical design, TRM employs a <em>single, tiny two-layer network</em>. This radical simplification has led to significantly higher generalization across a diverse range of problems.</p>
<p>TRM&#x27;s key innovations and advantages are nothing short of astounding:</p>
<ul>
<li><strong>Exceptional Efficiency:</strong> TRM operates with an astonishingly small number of parameters—as little as <strong>7 million</strong>. This represents less than 0.01% of the parameters found in many large language models, making it incredibly computationally efficient and accessible.</li>
<li><strong>Superior Performance:</strong> Despite its diminutive size, TRM has demonstrated superior performance on complex reasoning tasks, including Sudoku and ARC-AGI puzzles. It consistently outperforms both HRM and many large LLMs such as Deepseek R1, o3-mini, and even Gemini 2.5 Pro in terms of test accuracy (e.g., <strong>45% on ARC-AGI-1 and 8% on ARC-AGI-2</strong>).</li>
<li><strong>Simplified Design:</strong> TRM sheds the complexities of HRM. It requires no fixed-point theorem, intricate biological justifications, or a hierarchical structure. Instead, it distills the effective components of iterative refinement into a streamlined, elegant architecture.</li>
<li><strong>Enhanced Generalization:</strong> By focusing on the core principle of iterative refinement with a simplified network, TRM achieves better generalization capabilities, enabling it to solve a broader spectrum of complex problems with greater adaptability.</li>
</ul>
<h3>Conclusion</h3>
<p>The evolution from HRM to TRM marks a critical juncture in the pursuit of intelligent reasoning systems. While HRM pioneered the power of iterative reasoning and deep supervision, TRM unequivocally demonstrates that by simplifying the architecture and focusing on the most effective mechanisms, a &quot;tiny&quot; model can not only match but significantly surpass the capabilities of much larger and more complex counterparts. The Tiny Recursive Model represents a promising direction for developing highly efficient and effective AI systems, capable of tackling complex reasoning tasks with unprecedented resource efficiency. This breakthrough could unlock advanced reasoning capabilities in resource-constrained environments and pave the way for more interpretable, robust, and sustainable AI solutions.</p>]]></content:encoded>
      <category>AI</category>
      <category>Machine Learning</category>
      <category>Deep Learning</category>
      <category>TRM</category>
      <category>HRM</category>
      <category>Recursive Models</category>
      <category>Efficient AI</category>
      <category>Large Language Models</category>
      <category>LLMs</category>
      <category>Reasoning</category>
      <category>Samsung AI Lab</category>
      <category>ARC-AGI</category>
      <category>Sudoku</category>
    </item>
    <item>
      <title>From Chains to Brains: How LangGraph is Building the 'Deep Agents' of Tomorrow</title>
      <link>https://elijah.mondero.nz/post/from-chains-to-brains-how-langgraph-is-building-the-deep-agents-of-tomorrow/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/from-chains-to-brains-how-langgraph-is-building-the-deep-agents-of-tomorrow/</guid>
      <pubDate>Thu, 07 Aug 2025 22:41:10 +0000</pubDate>
      <description>LangChain made building LLM apps easy, but its linear 'chains' limited agent intelligence. Enter LangGraph, a powerful evolution that uses graph-based logic to create stateful, cyclical, and truly smart 'deep agents' capable of complex reasoning and self-correction. Discover how this shift is changing AI development.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/e013ee8f-faf3-413d-b2fe-285f1f6a0e10.png" alt="From Chains to Brains: How LangGraph is Building the &#x27;Deep Agents&#x27; of Tomorrow" /></p>
<h3>What are &#x27;Deep Agents&#x27;?</h3>
<p>If you&#x27;re exploring the cutting edge of AI development, you might have come across the term &quot;deep agents.&quot; While it&#x27;s not a standard industry term, it perfectly captures a goal many developers are chasing: creating sophisticated, autonomous AI agents that can reason, plan, and adapt to complex tasks. These aren&#x27;t just simple chatbots; they are systems designed to think.</p>
<p>For a long time, the go-to tool for building applications on top of Large Language Models (LLMs) has been LangChain. But to build truly &quot;deep agents,&quot; the community needed an evolution. That evolution is LangGraph.</p>
<h3>The Starting Point: The Limits of LangChain</h3>
<p>LangChain revolutionized LLM application development with a brilliant core concept: the <strong>&quot;chain.&quot;</strong> Think of it as an assembly line for AI. You connect components—an LLM, a data source, an API call—in a straight, linear sequence. An input goes in one end, passes through each step, and an output comes out the other.</p>
<p>This is incredibly powerful for straightforward tasks:</p>
<ul>
<li>Summarizing a document.</li>
<li>Answering a question based on a piece of text.</li>
<li>Extracting specific information.</li>
</ul>
<p>But what happens when the task isn&#x27;t straightforward? Real-world problems require looping, reflection, and decision-making. An agent might need to try a tool, see if it fails, and then try a different approach. It needs a memory of what it has already done. A simple, linear assembly line can&#x27;t do this. It can&#x27;t loop back on itself or choose a different path midway through. This is the inherent limitation of a chain.</p>
<h3>The Evolution: Thinking in Cycles with LangGraph</h3>
<p>LangGraph, created by the same team behind LangChain, was built specifically to solve this problem. It trades the linear &quot;chain&quot; for a much more flexible and powerful structure: the <strong>&quot;graph.&quot;</strong></p>
<p>In LangGraph, an agent&#x27;s workflow is a map of nodes and edges. Each <strong>node</strong> is a step (like an LLM call or a function), and each <strong>edge</strong> is a path that connects them. This simple change unlocks capabilities that are essential for building intelligent agents.</p>
<h4>1. Loops and Self-Correction</h4>
<p>With a graph, an agent can cycle back to a previous node. This means it can attempt a task, evaluate the outcome, and if it&#x27;s not good enough, <em>try again</em>. It can gather more information, refine its plan, or self-correct its mistakes. This is the foundation of reasoning.</p>
<h4>2. Stateful Memory</h4>
<p>LangGraph introduces a persistent <strong>state</strong> that is passed between nodes and updated at each step. This gives the agent memory. It knows what it has tried, what worked, and what didn&#x27;t, allowing it to make informed decisions based on the history of its actions.</p>
<h4>3. Conditional Logic and Dynamic Paths</h4>
<p>The edges connecting the nodes can be conditional. This means the agent can make decisions. Based on the output of one node, it can decide which node to go to next. Should it use a search tool, ask the user for clarification, or conclude its task? LangGraph allows the agent to dynamically choose its own path forward.</p>
<h3>Building the &quot;Deep Agent&quot;</h3>
<p>LangGraph provides the architectural freedom to build what we&#x27;ve been calling &quot;deep agents.&quot; These are systems that can tackle long-running, complex tasks because they can:</p>
<ul>
<li><strong>Plan:</strong> Lay out a series of steps.</li>
<li><strong>Act:</strong> Execute those steps using tools.</li>
<li><strong>Reflect:</strong> Analyze the results of their actions.</li>
<li><strong>Adapt:</strong> Change their plan based on that reflection.</li>
</ul>
<p>This cyclical, stateful approach moves us from creating simple LLM-powered tools to orchestrating truly intelligent, autonomous systems.</p>
<h3>The Broader Landscape: Similar Concepts</h3>
<p>LangGraph is a leading solution in this space, but the ideas it employs are part of a broader field in AI. If you&#x27;re looking for similar concepts or alternative approaches, you should explore:</p>
<ul>
<li><strong>Multi-Agent Systems (MAS):</strong> The academic and practical field focused on creating systems of multiple interacting, autonomous agents.</li>
<li><strong>Agent-Based Modeling (ABM):</strong> Often used in simulation, these frameworks are designed to manage populations of agents that follow specific rules and behaviors.</li>
<li><strong>Robotics and Control Systems (e.g., ROS):</strong> These systems have long used state machines and graph-based behavior trees to give robots complex, adaptive behaviors—a concept spiritually similar to LangGraph&#x27;s approach for LLMs.</li>
</ul>
<p>When evaluating any framework for building advanced agents, look for its ability to handle state management, complex control flow, tool integration, and communication between agents.</p>
<p>LangGraph isn&#x27;t just another library; it&#x27;s a paradigm shift. By moving from linear chains to dynamic graphs, it provides the toolkit for building the next generation of AI—agents that don&#x27;t just follow instructions, but actually think.</p>]]></content:encoded>
      <category>LangGraph</category>
      <category>LangChain</category>
      <category>AI Agents</category>
      <category>Multi-Agent Systems</category>
      <category>LLM</category>
      <category>Python</category>
      <category>Artificial Intelligence</category>
    </item>
    <item>
      <title>Meet Warmwind OS: The AI Digital Employee That Automates Your Workflow</title>
      <link>https://elijah.mondero.nz/post/meet-warmwind-os-the-ai-digital-employee-that-automates-your-workflow/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/meet-warmwind-os-the-ai-digital-employee-that-automates-your-workflow/</guid>
      <pubDate>Fri, 18 Jul 2025 10:51:39 +0000</pubDate>
      <description>Imagine hiring a digital employee that works 24/7, never takes a break, and perfectly handles your most repetitive tasks. That's the promise of Warmwind OS, the world's first AI-native operating system designed to revolutionize workflow automation.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/5084d85e-abfd-404b-a9a9-fa517738509d.png" alt="Meet Warmwind OS: The AI Digital Employee That Automates Your Workflow" /></p>
<h3>The Daily Grind of Repetitive Tasks</h3>
<p>We’ve all been there: clicking through the same series of screens, copying and pasting data, handling routine support tickets, or managing social media posts. These repetitive digital tasks are the necessary but tedious parts of modern work that consume valuable time and energy. But what if you could delegate them all to an AI that learns by watching you work?</p>
<p>Enter Warmwind OS, a groundbreaking platform from German startup Jena that’s being hailed as the world&#x27;s first AI-native operating system. It’s not an OS for your laptop but rather a dedicated, cloud-based environment where a “digital employee” carries out your workflows tirelessly, 24/7.</p>
<h3>What Exactly Is Warmwind OS?</h3>
<p>Think of Warmwind OS as a virtual team member. It’s a cloud-based platform designed specifically to automate digital work. Instead of relying on complex code or API integrations, Warmwind OS watches a human perform a task once and then learns to replicate it autonomously. It interacts with software exactly like a person would: by clicking buttons, typing text, and reading information on the screen.</p>
<p>This revolutionary approach means it can work with virtually any software, from modern web apps to legacy enterprise systems, without needing any changes to the underlying code.</p>
<h3>How It Works: Automation Through Observation</h3>
<p>The magic of Warmwind OS lies in its simplicity. Here’s the process:</p>
<ol>
<li><strong>Demonstrate the Task:</strong> A user performs a workflow one time within the secure Warmwind OS virtual environment.</li>
<li><strong>AI Observes:</strong> The AI carefully observes every click, keystroke, and decision made during the demonstration.</li>
<li><strong>Autonomous Replication:</strong> The AI can then perfectly replicate that workflow on its own, as many times as needed, without human supervision.</li>
</ol>
<p>Operating at the user interface (UI) level allows it to bypass the need for complicated and often unavailable API access, making it a universally applicable solution.</p>
<h3>Key Features That Make Warmwind OS a Game-Changer</h3>
<p>Warmwind OS is packed with features designed for efficiency, security, and ease of use.</p>
<ul>
<li><strong>No-Code, No-API Required:</strong> This is its most powerful feature. By interacting directly with the graphical user interface (GUI), Warmwind OS can automate tasks on any application, including older, legacy software that lacks modern APIs.</li>
</ul>
<ul>
<li><strong>Versatile Task Automation:</strong> The potential applications are vast. Businesses can use it to automate customer support ticket responses, social media management, CI/CD pipeline monitoring, report generation, and much more.</li>
</ul>
<ul>
<li><strong>Privacy-Focused by Design:</strong> Developed by a German company, Warmwind OS takes data privacy seriously. All data is hosted on servers in Germany, ensuring full compliance with GDPR, one of the world&#x27;s strictest privacy regulations.</li>
</ul>
<ul>
<li><strong>Fully Cloud-Native:</strong> There&#x27;s no software to install or maintain on your local machines. The entire system runs securely in the cloud, accessible from anywhere.</li>
</ul>
<h3>Who Is It For?</h3>
<p>Warmwind OS is primarily aimed at enterprise customers and businesses of all sizes seeking to boost productivity. Any organization with repetitive digital workflows can benefit, including departments like:</p>
<ul>
<li><strong>Customer Support:</strong> Automating responses to common queries and ticket handling.</li>
<li><strong>Human Resources:</strong> Streamlining onboarding processes and data entry.</li>
<li><strong>Software Development:</strong> Automating reporting and CI/CD pipeline tasks.</li>
<li><strong>Marketing:</strong> Scheduling social media posts and compiling performance reports.</li>
</ul>
<h3>The Future Is Here, But You&#x27;ll Have to Wait</h3>
<p>Warmwind OS is currently in its beta phase, and the excitement is palpable. There is already a waiting list with a reported 12,000+ people eager to get access. This high demand signals a clear need for smarter automation solutions that go beyond traditional scripts and macros.</p>
<p>By creating a “digital employee” that learns and adapts, Warmwind OS isn&#x27;t just offering a tool—it&#x27;s proposing a new way to work, freeing up human potential to focus on creativity, strategy, and high-value problem-solving.</p>]]></content:encoded>
      <category>AI</category>
      <category>Automation</category>
      <category>Warmwind OS</category>
      <category>Productivity</category>
      <category>Future of Work</category>
      <category>Operating System</category>
      <category>No-Code</category>
      <category>Digital Employee</category>
    </item>
    <item>
      <title>AI and the Future of Work: Displacement, Creation, and the Shifting Landscape</title>
      <link>https://elijah.mondero.nz/post/ai-and-the-future-of-work-displacement-creation-and-the-shifting-landscape/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/ai-and-the-future-of-work-displacement-creation-and-the-shifting-landscape/</guid>
      <pubDate>Sun, 06 Jul 2025 03:50:16 +0000</pubDate>
      <description>Artificial intelligence is rapidly reshaping the global job market, displacing some roles while creating millions of new opportunities. Explore the sectors most affected, the emerging careers, and how individuals and organizations can navigate this significant transition.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/a7b510fb-c30a-4b88-9a5c-915d20d975f9.png" alt="AI and the Future of Work: Displacement, Creation, and the Shifting Landscape" /></p>
<p>The integration of Artificial Intelligence (AI) into our workplaces is no longer a futuristic concept; it&#x27;s a present reality fundamentally transforming the global job market. While headlines often focus on the fear of automation leading to mass unemployment, the full picture is far more nuanced, involving both significant job displacement and the exciting creation of entirely new roles.</p>
<h2>A Complex Transformation: More Jobs, Different Jobs</h2>
<p>The overall impact of AI and automation on job numbers is projected to be complex. According to the World Economic Forum, a staggering 85 million jobs may be displaced by 2025 due to these technologies. However, during the same period, an estimated 97 million new roles are expected to emerge globally. This suggests a potential <strong>net positive</strong> in the sheer number of jobs, but highlights a crucial shift: the types of jobs available and the skills required to perform them are changing dramatically.</p>
<h2>Where AI is Displacing Jobs</h2>
<p>AI is particularly effective at automating tasks that are routine, repetitive, and data-driven. Jobs most susceptible to displacement often involve:</p>
<ul>
<li><strong>Routine Cognitive Tasks:</strong> Handling data processing, performing basic analysis, and making rule-based decisions.</li>
<li><strong>Structured Physical Work:</strong> Repetitive manual tasks performed in controlled environments.</li>
<li><strong>Basic Customer Service:</strong> Answering standard inquiries and providing routine information.</li>
</ul>
<p>We&#x27;re already seeing this play out across various industries:</p>
<ul>
<li><strong>Banking:</strong> AI-powered ATMs and chatbots are taking over roles traditionally held by bank tellers. AI is also being used to review complex documents that previously required extensive human hours.</li>
<li><strong>Manufacturing:</strong> Robots are increasingly replacing factory workers to boost efficiency and reduce manufacturing defects.</li>
<li><strong>Transportation:</strong> Advances in self-driving technology are paving the way for automated vehicles, including long-haul trucks.</li>
</ul>
<p>Specific sectors are expected to see significant displacement rates by 2025, including:</p>
<ul>
<li>Transportation (50%)</li>
<li>Customer Service (40%)</li>
<li>Retail (30%)</li>
<li>Financial Services (28%)</li>
<li>Manufacturing (20%)</li>
</ul>
<h2>The Rise of New AI-Driven Careers</h2>
<p>While some jobs disappear, AI is simultaneously acting as a catalyst for the creation of brand new career categories. These roles often didn&#x27;t exist just a few years ago and represent significant future opportunities.</p>
<p>Emerging roles in the AI economy include:</p>
<ul>
<li><strong>AI Ethics Officers:</strong> Ensuring AI systems are developed and used responsibly and ethically.</li>
<li><strong>Human-AI Collaboration Specialists:</strong> Designing and optimizing workflows where humans and AI work together effectively.</li>
<li><strong>AI Trainers:</strong> Teaching AI systems to understand complex concepts, context, and human values.</li>
<li><strong>Data Scientists and Machine Learning Engineers:</strong> The core roles focused on building and maintaining AI systems.</li>
<li><strong>Domain-Specific AI Specialists:</strong> Applying AI technologies and insights within particular industries like healthcare, finance, or agriculture.</li>
</ul>
<p>Demand for AI-related skills and jobs is already soaring. AI specialist roles have shown remarkable annual growth (e.g., 74% annually according to LinkedIn), and the overall demand for jobs related to AI is projected to increase dramatically (e.g., by 300% from 2020 levels by 2025).</p>
<h2>Navigating the Transition: Skills for the AI Age</h2>
<p>For both individuals and organizations, successfully navigating this transition is key to thriving, not just surviving.</p>
<ul>
<li><strong>For Organizations:</strong> Strategic AI implementation isn&#x27;t just about replacing workers; it&#x27;s about reallocating human talent to higher-value activities that require creativity, critical thinking, and interpersonal skills – areas where humans currently excel over AI.</li>
<li><strong>For Individuals:</strong> If your role involves tasks at high risk of automation, focusing on developing <strong>complementary skills</strong> is crucial. Instead of trying to compete directly with AI, learn how to work <em>alongside</em> AI systems. This could involve skills in managing AI tools, interpreting AI outputs, ethical considerations, or applying domain expertise that AI systems lack.</li>
</ul>
<h2>Conclusion: Collaboration is Key</h2>
<p>The future of work isn&#x27;t likely to be a battle between humans and machines, but rather a partnership. While AI will undoubtedly automate routine tasks, it will also augment human capabilities and create new frontiers for innovation and employment. Success in the AI age will depend on adaptability, continuous learning, and a willingness to embrace roles that emphasize human-AI collaboration and the uniquely human skills that complement artificial intelligence.</p>
<p>Preparing for this future means understanding the shifting landscape and proactively developing the skills needed to work effectively in an increasingly AI-augmented world.</p>]]></content:encoded>
      <category>AI</category>
      <category>Artificial Intelligence</category>
      <category>Job Market</category>
      <category>Future of Work</category>
      <category>Automation</category>
      <category>Job Displacement</category>
      <category>Job Creation</category>
      <category>Skills Gap</category>
      <category>Workforce Transformation</category>
      <category>Technology</category>
    </item>
    <item>
      <title>Navigating the AI Hype Cycle: Where Enterprise AI Stands Today</title>
      <link>https://elijah.mondero.nz/post/navigating-the-ai-hype-cycle-where-enterprise-ai-stands-today/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/navigating-the-ai-hype-cycle-where-enterprise-ai-stands-today/</guid>
      <pubDate>Sat, 05 Jul 2025 00:13:23 +0000</pubDate>
      <description>AI technologies are evolving rapidly, and their journey is often mapped by the Gartner Hype Cycle. Learn where key areas like Cloud AI and Generative AI sit in 2024, why they're entering the 'Trough of Disillusionment,' and what this means for businesses focused on practical adoption and real value.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/7dc1d95e-8f53-4943-8c30-bd7aede0a435.png" alt="Navigating the AI Hype Cycle: Where Enterprise AI Stands Today" /></p>
<p>Artificial Intelligence has been a dominant force in the tech conversation for years, promising transformative capabilities across industries. However, the path from groundbreaking innovation to widespread, practical application is rarely a straight line. For many technologies, this journey is famously illustrated by the Gartner Hype Cycle.</p>
<p>The Hype Cycle maps a technology&#x27;s typical progression through five phases:</p>
<ol>
<li><strong>Innovation Trigger:</strong> A breakthrough sparks potential.</li>
<li><strong>Peak of Inflated Expectations:</strong> Early publicity and over-enthusiasm dominate.</li>
<li><strong>Trough of Disillusionment:</strong> Interest wanes as experiments and implementations fail to deliver on promises.</li>
<li><strong>Slope of Enlightenment:</strong> Early adopters figure out how to make the technology work.</li>
<li><strong>Plateau of Productivity:</strong> The technology becomes mainstream and its benefits are widely realized.</li>
</ol>
<p>Understanding where key AI technologies currently sit on this cycle is crucial for enterprises planning their AI strategies.</p>
<h2>The 2024 AI Hype Cycle: A Reality Check</h2>
<p>According to the latest 2024 Gartner Hype Cycle for Artificial Intelligence, some significant shifts are occurring, particularly regarding Cloud AI services and Generative AI (GenAI).</p>
<p>Most notably, <strong>Cloud AI services</strong> have moved significantly down the cycle since 2023, landing squarely at the <strong>bottom of the Trough of Disillusionment</strong>. This marks a notable regression from their previous position on the Slope of Enlightenment. The reason? Organizations and vendors alike have encountered practical challenges with GenAI-based cloud AI offerings. Issues cited include service capacity constraints, reliability problems, the frequent rate of model updates, and unpredictable cost fluctuations. Gartner describes these as potential &quot;growing pains&quot; as the technology matures.</p>
<p><strong>Generative AI</strong> itself, which was perched at the very peak of inflated expectations last year, appears to be just beginning its descent towards the Trough of Disillusionment in the 2024 cycle. While GenAI introduces powerful new capabilities, such as the ability to fine-tune large language models (LLMs), its overall maturity level is still lower compared to some other AI technologies.</p>
<h2>What the &#x27;Trough&#x27; Means for Enterprise AI</h2>
<p>The movement of key AI areas into or towards the Trough of Disillusionment isn&#x27;t a sign of failure; rather, it&#x27;s a natural and necessary phase in the technology&#x27;s evolution. It signifies a shift from the initial hype-driven excitement to a more grounded, realistic understanding of AI&#x27;s capabilities and, crucially, its limitations.</p>
<p>For enterprises, this phase is critical. It encourages a pivot away from abstract promises towards practical application and value realization. The focus shifts to addressing the real-world challenges highlighted – integration complexities, cost management, ensuring reliability, and developing robust AI governance frameworks.</p>
<p>Instead of chasing every new AI trend, organizations are increasingly prioritizing how to effectively integrate AI into their existing workflows and data infrastructure. This requires developing deliberate strategies for scaling AI adoption to ensure tangible business benefits.</p>
<h2>Beyond the Hype: Focusing on Practicality and Integration</h2>
<p>The 2024 Hype Cycle also features a range of other AI-related technologies at various stages, including AI engineering, edge AI, responsible AI, prompt engineering, and synthetic data. Some of these are now occupying positions previously held by GenAI at the peak, demonstrating the continuous innovation within the AI landscape.</p>
<p>Regardless of where specific technologies sit on the cycle, the overarching theme for enterprise AI is a move towards practicality. The conversation is less about <em>if</em> AI can do something and more about <em>how</em> to deploy it effectively, ethically, and at scale to solve specific business problems and drive measurable value.</p>
<p>Successfully navigating the Trough of Disillusionment requires a strategic approach focused on:</p>
<ul>
<li><strong>Clear Use Cases:</strong> Identifying specific problems AI can solve.</li>
<li><strong>Effective Integration:</strong> Ensuring AI fits seamlessly into existing systems and processes.</li>
<li><strong>Robust Governance:</strong> Establishing policies for data, ethics, and model management.</li>
<li><strong>Realistic Expectations:</strong> Understanding that AI is a tool requiring careful implementation.</li>
</ul>
<h2>The Path Forward: Towards Enlightenment and Productivity</h2>
<p>The Trough of Disillusionment is not the end of the road for enterprise AI. It&#x27;s a vital correction that forces necessary rigor and strategic thinking. By confronting the challenges head-on, organizations can pave the way towards the Slope of Enlightenment, where practical applications yield initial benefits, and ultimately, to the Plateau of Productivity, where AI becomes a standard, valuable component of business operations.</p>
<p>The current phase calls for patience, strategic investment, and a commitment to building the foundational capabilities needed to unlock the true, sustainable potential of AI in the enterprise.</p>]]></content:encoded>
      <category>AI</category>
      <category>Enterprise AI</category>
      <category>Gartner Hype Cycle</category>
      <category>Generative AI</category>
      <category>Cloud AI</category>
      <category>Digital Transformation</category>
      <category>Technology Adoption</category>
      <category>Business Strategy</category>
    </item>
    <item>
      <title>From Prompt Hacks to Protocols: The Evolution of Building Smarter AI Agents</title>
      <link>https://elijah.mondero.nz/post/from-prompt-hacks-to-protocols-the-evolution-of-building-smarter-ai-agents/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/from-prompt-hacks-to-protocols-the-evolution-of-building-smarter-ai-agents/</guid>
      <pubDate>Wed, 11 Jun 2025 10:42:56 +0000</pubDate>
      <description>AI agents are getting smarter, moving beyond simple text generation to taking actions and interacting with the real world. This leap is powered by the evolution of how we 'prompt' them, progressing from clever text patterns like ReAct to standardized tools and data access protocols. Explore this journey and what it means for the future of AI.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/bd5c3c53-eab2-4b85-a8dc-b64e1f80cf48.png" alt="From Prompt Hacks to Protocols: The Evolution of Building Smarter AI Agents" /></p>
<p>Artificial intelligence is rapidly moving beyond generating witty text or insightful summaries. The focus is shifting towards building <em>agents</em> – AI systems capable of reasoning, planning, and taking actions in the real world by interacting with tools and data. This evolution is fundamentally tied to how we communicate with and guide these models, a practice known as prompt engineering.</p>
<p>The journey of prompting AI agents has been a fascinating progression, moving from ingenious text-based &#x27;hacks&#x27; to sophisticated, standardized protocols. Let&#x27;s trace this path through some key milestones.</p>
<h2>Stage 1: Early Attempts - The Rise of Reason and Act (ReAct)</h2>
<p>In the early days of building agents with large language models (LLMs), developers relied heavily on carefully crafted prompts to structure the model&#x27;s thinking and actions. A standout technique from this era was <strong>ReAct (Reason + Act)</strong>.</p>
<p>ReAct introduced a structured prompting pattern that mirrored a human thought process. The prompt would guide the model to first generate a <code>Thought:</code> – essentially an internal monologue where the AI reasoned about the problem and the next logical step. This was immediately followed by an <code>Action:</code> – an instruction for the model to invoke an external tool or API, often specifying parameters within the text itself.</p>
<p>The <code>Observation:</code> resulting from the action would then be fed back into the prompt, allowing the model to continue its sequence of <code>Thought:</code> and <code>Action:</code>.</p>
<ul>
<li><strong>How it worked:</strong> The prompt explicitly instructed the model to alternate between thinking and acting steps, requiring precise text formatting for the external system to parse and execute the actions.</li>
<li><strong>Significance:</strong> ReAct proved that LLMs could perform multi-step tasks involving external tools by explicitly structuring their internal process and external interactions within the prompt.</li>
<li><strong>Limitations:</strong> This method was inherently brittle. It relied on the model generating text in a very specific, parsable format. Any deviation could break the action execution flow, requiring complex and often fragile parsing mechanisms.</li>
</ul>
<h2>Stage 2: Standardizing Interaction - OpenAI&#x27;s Function Calling / Tools</h2>
<p>A major step forward in agent development arrived with models designed to handle structured tool definitions more reliably. OpenAI&#x27;s <strong>Function Calling</strong> (later generalized as <strong>Tools</strong>) marked a significant shift away from purely text-based action prompts.</p>
<p>Instead of embedding tool descriptions and call formats within the main prompt text, developers could define available tools with structured schemas (like JSON) for their parameters. The model, specifically trained for this purpose, could then analyze the user query or its internal state and respond with a structured output (e.g., a JSON object) indicating its <em>intention</em> to call a specific function with specified arguments.</p>
<ul>
<li><strong>How it worked:</strong> Developers provide tool descriptions via a dedicated API parameter. The model&#x27;s response format includes a specific mode for declaring tool calls as structured data, separate from natural language responses.</li>
<li><strong>Significance:</strong> Function calling made integrating LLMs with APIs far more robust and reliable. It standardized the interface between the model&#x27;s decision-making and the execution environment, reducing reliance on error-prone text parsing. This enabled more reliable and scalable agentic applications.</li>
<li><strong>Evolution:</strong> OpenAI has continued to refine this, training newer models to leverage tools via dedicated API fields, making it the recommended way to enable tool use over manual prompt injection. The OpenAI Agents SDK further builds on this for complex workflows.</li>
</ul>
<h2>Stage 3: Enhancing Context and Data Access - Anthropic&#x27;s Model Context Protocol (MCP)</h2>
<p>While OpenAI&#x27;s tools focused on enabling agents to <em>act</em> on the world, Anthropic has been driving innovation in how agents <em>understand</em> and <em>ground</em> themselves in the world&#x27;s information. Anthropic&#x27;s <strong>Model Context Protocol (MCP)</strong> addresses the critical need to provide agents with reliable, up-to-date, and structured context from external data sources.</p>
<p>MCP is designed as a standard for connecting AI assistants to diverse systems like databases, document repositories, CRMs, and more. It&#x27;s about providing the agent with the necessary background knowledge and current state information in a structured, controlled, and secure manner.</p>
<ul>
<li><strong>How it worked:</strong> MCP proposes a standardized way for systems to deliver relevant data to the AI model, ensuring the information is accurate, timely, and respects access permissions. It focuses on providing the &#x27;knowledge&#x27; needed to inform decisions and responses.</li>
<li><strong>Significance:</strong> MCP represents an evolution in providing rich, dynamic context. While tool use is about <em>doing</em>, MCP is about <em>knowing</em> – accessing the information required to decide <em>what</em> to do or <em>what</em> to say. By standardizing data access, it aims to make agents more knowledgeable, accurate, and capable of tasks requiring information synthesis from multiple sources.</li>
</ul>
<ul>
<li><strong>Relationship to Tools:</strong> MCP is highly complementary to tool use. An agent might use MCP to retrieve customer history (context) and then use a tool (via function calling) to update their account based on that history and the user&#x27;s request.</li>
</ul>
<h2>Conclusion: Towards More Capable and Grounded Agents</h2>
<p>The evolution of prompt engineering for AI agents highlights a clear trend: a move from clever text-based patterns to structured, reliable, and integrated approaches. We&#x27;ve progressed from manually guiding the model&#x27;s internal monologue (ReAct) to providing standardized interfaces for action (OpenAI Tools) and developing protocols for accessing rich, external context (Anthropic MCP).</p>
<p>These advancements are paving the way for significantly more sophisticated AI agents – systems that can not only reason and act but also stay informed, access relevant real-world data, and operate more reliably and effectively. This ongoing evolution is crucial for building the next generation of capable and trustworthy AI applications.</p>]]></content:encoded>
    </item>
    <item>
      <title>LLMs Are AI, But They're Not *All* of It: Understanding the Difference</title>
      <link>https://elijah.mondero.nz/post/llms-are-ai-but-theyre-not-all-of-it-understanding-the-difference/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/llms-are-ai-but-theyre-not-all-of-it-understanding-the-difference/</guid>
      <pubDate>Sun, 01 Jun 2025 08:37:22 +0000</pubDate>
      <description>Confused about the difference between AI and LLMs? You're not alone. While Large Language Models are a powerful part of the AI landscape, they represent just one piece of a much bigger puzzle. Learn why they're related but distinct.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/ebbc01d5-07cc-41f5-9aff-a57add13a75c.png" alt="LLMs Are AI, But They&#x27;re Not *All* of It: Understanding the Difference" /></p>
<p>In the rapidly evolving world of artificial intelligence, terms like &quot;AI&quot; and &quot;LLM&quot; (Large Language Model) are often used interchangeably. While closely related, understanding the precise relationship and distinction between them is crucial to grasping the true scope of modern technology.</p>
<p>So, let&#x27;s break it down.</p>
<h2>AI: The Big Picture</h2>
<p>Think of Artificial Intelligence (AI) as a vast, overarching field. At its core, AI is about creating machines capable of performing tasks that typically require human intelligence. This ambition covers a wide spectrum of abilities, including:</p>
<ul>
<li>Learning</li>
<li>Problem-solving</li>
<li>Perception (like seeing or hearing)</li>
<li>Decision-making</li>
<li>Planning</li>
</ul>
<p>AI isn&#x27;t just one technology; it&#x27;s a concept encompassing numerous approaches and disciplines. This includes things like machine learning, computer vision (enabling machines to &quot;see&quot;), robotics, expert systems, and yes, natural language processing (enabling machines to understand and process human language).</p>
<p>Essentially, if a machine is doing something that feels smart or requires cognitive ability, it falls under the broad umbrella of AI.</p>
<h2>LLMs: The Language Specialist Subset</h2>
<p>Now, enter Large Language Models (LLMs). If AI is the entire field, LLMs are a very specific, highly advanced <em>type</em> or <em>subset</em> of AI. Their specialization is right there in the name: <strong>Language</strong>.</p>
<p>LLMs are sophisticated AI models trained specifically to understand, generate, and process human language. They are built using deep learning techniques – a powerful AI process involving complex artificial neural networks – and are trained on colossal datasets of text and code from the internet and other sources. This training allows them to learn grammar, facts, reasoning patterns, and different writing styles.</p>
<h2>The Core Distinction: Scope and Specialization</h2>
<p>The fundamental difference lies in their scope:</p>
<ul>
<li><strong>AI:</strong> Aims to replicate <em>various</em> aspects of human intelligence across many domains.</li>
</ul>
<ul>
<li><strong>LLMs:</strong> Focus <em>specifically</em> on language-related tasks.</li>
</ul>
<p>An easy way to visualize this relationship is using an analogy:</p>
<p>Think of <strong>AI as the entire category of &quot;vehicles.&quot;</strong> This includes cars, trucks, buses, motorcycles, airplanes, and boats. <strong>LLMs are like &quot;cars.&quot;</strong> A car is definitely a vehicle, but it&#x27;s only one type. You wouldn&#x27;t call a truck a car, even though both are vehicles. Similarly, an LLM is a type of AI, but not all AI systems are LLMs.</p>
<h2>Different Jobs, Different Applications</h2>
<p>Because AI is so broad and LLMs are specialized, their applications differ:</p>
<ul>
<li><strong>AI Applications:</strong> Found everywhere – diagnosing diseases (healthcare), detecting fraud (finance), self-driving cars (transportation), recommending movies (entertainment), manufacturing automation (industry), and much more. Many of these applications don&#x27;t involve language at all.</li>
<li><strong>LLM Applications:</strong> Primarily centered around text and language – powering chatbots and virtual assistants, generating articles and creative content, summarizing documents, translating languages, analyzing sentiment in text, and facilitating conversational interfaces.</li>
</ul>
<h2>The Takeaway</h2>
<p>Here&#x27;s the key point to remember: <strong>All LLMs are AI, but not all AI systems are LLMs.</strong></p>
<p>LLMs represent a remarkable advancement within the field of AI, demonstrating impressive capabilities in understanding and generating human language. They are a significant part of the current AI boom, but they are just one part of the much larger, diverse, and exciting landscape of Artificial Intelligence.</p>
<p>So, the next time you interact with a chatbot or hear about AI, you&#x27;ll know that while the LLM is powered by AI, AI itself is capable of so much more than just talking or writing.</p>]]></content:encoded>
    </item>
    <item>
      <title>Beyond the Chat Window: Understanding the Rise of Ambient Agents</title>
      <link>https://elijah.mondero.nz/post/beyond-the-chat-window-understanding-the-rise-of-ambient-agents/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/beyond-the-chat-window-understanding-the-rise-of-ambient-agents/</guid>
      <pubDate>Sat, 17 May 2025 02:56:09 +0000</pubDate>
      <description>Move over, chatbots. Ambient agents are a new wave of AI designed to work proactively in the background, monitoring information streams and taking intelligent action – often with smart human oversight. Discover how these agents differ from traditional AI and why the 'human-in-the-loop' is key to their success.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/4b034a02-fbb8-4c99-95ed-cd00318e13ed.png" alt="Beyond the Chat Window: Understanding the Rise of Ambient Agents" /></p>
<p>Artificial intelligence is constantly evolving, and the way we interact with it is changing rapidly. For a long time, the primary mode of AI interaction for the public has been the chatbot – you initiate a conversation, ask a question, and the AI responds within that specific chat session.</p>
<p>But what if AI could be more like a vigilant assistant, quietly working in the background, only stepping in when needed or when something truly important happens? Enter <strong>Ambient Agents</strong>.</p>
<h2>What are Ambient Agents?</h2>
<p>Ambient agents represent a significant shift in AI interaction. Unlike traditional chatbots that require you to open an interface and type a command every time, ambient agents are designed to operate continuously, monitoring various digital &quot;event streams&quot; such as emails, messages, calendar invites, data feeds, and more.</p>
<p>Their core characteristic is their proactive nature. Instead of waiting for a direct prompt, they listen to ambient signals and take intelligent actions or provide relevant information without explicit initiation. Think of an agent that notices an urgent email from your boss, flags it immediately, and maybe even drafts a potential response – all before you even open your inbox.</p>
<p>Ambient agents are built on concepts from ambient intelligence and autonomous agents, focusing on creating a more seamless, context-aware, and scalable user experience.</p>
<h2>How Do They Differ from Traditional Chatbots?</h2>
<p>The key difference lies in the interaction pattern:</p>
<ul>
<li><strong>Traditional Chatbots:</strong> Follow a &quot;chat&quot; pattern. A user initiates, the agent responds, and the interaction ends (or pauses). This creates interaction overhead and limits the agent to focusing on one task or conversation initiated by the user at a time.</li>
<li><strong>Ambient Agents:</strong> Listen to ambient signals. The agent monitors streams, detects an important event, and takes action OR prompts the user. They are not solely triggered by human messages and can monitor and act upon multiple event streams simultaneously, helping users scale their own attention and productivity.</li>
</ul>
<p>Ambient agents aim to reduce the friction of needing to constantly initiate AI work, allowing the technology to assist more naturally and efficiently within the flow of our digital lives.</p>
<h2>The Crucial Role of the Human-in-the-Loop</h2>
<p>While ambient agents strive for greater autonomy, successfully integrating them into public use hinges on thoughtful consideration of the <strong>human-in-the-loop</strong> (HITL). This refers to <em>when</em> and <em>how</em> these agents interact with humans.</p>
<p>Complete autonomy for agents handling sensitive tasks can be risky. Therefore, strategic human involvement is essential for safety, trust, and effectiveness. There are typically three common HITL patterns:</p>
<ol>
<li><strong>Notify:</strong> The agent simply alerts the user to an important event or piece of information without taking further action. This is useful for high-importance flags where the agent isn&#x27;t authorized to act (e.g., flagging a critical contract arriving in your email).</li>
<li><strong>Question:</strong> The agent encounters a situation where it lacks necessary information or clarity to proceed. Like a human assistant, it asks the user for guidance rather than guessing or &quot;hallucinating&quot; (e.g., receiving an email about a conference and asking the user if they&#x27;d like to attend based on their preferences).</li>
<li><strong>Review:</strong> The agent proposes an action it intends to take but requires explicit human approval before execution. This pattern is vital for &quot;dangerous&quot; or high-stakes actions, allowing the user to review, edit, or provide feedback on the proposed step (e.g., drafting an email response but requiring the user to approve sending it).</li>
</ol>
<h2>Why Human-in-the-Loop Matters</h2>
<p>Integrating human oversight isn&#x27;t a step back; it&#x27;s a strategic necessity with significant benefits:</p>
<ul>
<li><strong>Lowers the Stakes:</strong> By gating potentially impactful actions behind human approval, it becomes much safer to deploy agents for tasks that have real-world consequences (like sending emails or updating databases).</li>
<li><strong>Mimics Human Collaboration:</strong> Interacting with users through notifications, questions, and review requests mirrors how humans collaborate. This builds trust and encourages user adoption by making the agent feel more like a reliable co-worker.</li>
<li><strong>Empowers Learning and Memory:</strong> Human feedback isn&#x27;t just for safety; it&#x27;s a valuable data source. When users edit a draft or provide feedback on a proposed action, the agent can learn and improve its performance over time, contributing to its long-term effectiveness.</li>
</ul>
<h2>The Future is Ambient</h2>
<p>Ambient agents represent an exciting evolution in AI, moving towards proactive, context-aware assistance that operates seamlessly in the background of our digital lives. By leveraging ambient signals and thoughtfully incorporating human-in-the-loop processes, these agents promise a future where AI doesn&#x27;t just respond when called upon, but actively helps us navigate complexity and scale our own capabilities.</p>
<p>As this technology matures, expect to see ambient agents become integrated into various aspects of our work and personal lives, quietly helping us stay informed, organized, and productive.</p>]]></content:encoded>
      <category>AI</category>
      <category>Artificial Intelligence</category>
      <category>Ambient Agents</category>
      <category>Chatbots</category>
      <category>Human-in-the-Loop</category>
      <category>Proactive AI</category>
      <category>Autonomous Agents</category>
      <category>Technology</category>
      <category>Future of AI</category>
    </item>
    <item>
      <title>Navigating the AI Revolution: The Evolving Future of Software Engineering</title>
      <link>https://elijah.mondero.nz/post/navigating-the-ai-revolution-the-evolving-future-of-software-engineering/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/navigating-the-ai-revolution-the-evolving-future-of-software-engineering/</guid>
      <pubDate>Sun, 11 May 2025 03:21:20 +0000</pubDate>
      <description>AI is rapidly transforming software engineering by automating tasks, but human creativity, critical thinking, and specialized skills are more vital than ever. Discover how engineers can thrive by collaborating with AI and focusing on high-value areas.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/11a3ae7c-8ca6-4c5a-8b69-8da7b5a99027.png" alt="Navigating the AI Revolution: The Evolving Future of Software Engineering" /></p>
<p>The world of software engineering is undergoing a significant transformation, largely propelled by the relentless march of Artificial Intelligence. AI is no longer a theoretical concept; it&#x27;s an active participant, reshaping how software is conceived, built, tested, and maintained. This evolution presents both exciting new possibilities and fundamental shifts in the industry landscape.</p>
<h2>AI: Automating the Engine Room</h2>
<p>One of AI&#x27;s most immediate and tangible impacts is the automation of routine and repetitive development tasks. AI-powered tools are becoming increasingly sophisticated, capable of generating code snippets, identifying and even suggesting fixes for bugs, automatically creating documentation, and handling simple maintenance operations. This surge in automation is directly contributing to increased efficiency and faster development cycles.</p>
<p>Companies are already reporting substantial boosts in engineering productivity thanks to AI adoption. The significant global spending projected for AI software underscores its growing integration into daily development workflows, signaling a widespread acceptance and reliance on these tools.</p>
<h2>The Indispensable Human Element</h2>
<p>Despite AI&#x27;s growing capabilities in automating predictable processes, the need for human software engineers remains robust. However, the focus is shifting. Tasks that require high-level creativity, nuanced critical thinking, complex problem-solving, and strategic decision-making are still firmly within the human domain.</p>
<p>Professionals who excel at designing complex system architectures, possess deep specialized domain knowledge, and can effectively manage and integrate AI tools into larger, intricate projects are becoming increasingly valuable. Furthermore, navigating the complex ethical implications of AI development and ensuring legal and compliance standards require human judgment and oversight that AI cannot replicate.</p>
<h2>Evolving Skills for a New Era</h2>
<p>The rise of AI doesn&#x27;t spell the end of software engineering; rather, it signals an evolution in the required skill sets. Future opportunities for engineers will increasingly lie in areas where they can complement and leverage AI capabilities.</p>
<p>One clear path is specialization in Artificial Intelligence and Machine Learning development itself. As AI becomes more integrated, understanding its underlying principles and how to build AI systems will be paramount. Cybersecurity is another critical field poised for growth, as the increasing complexity of software and the integration of AI introduce new and more sophisticated security challenges.</p>
<p>Bridging the gap between Information Technology (IT) and Operational Technology (OT) is also emerging as a vital area, demanding engineers who can navigate the complexities of both digital and physical systems, often involving AI at the intersection.</p>
<h2>The Impact on the Engineering Landscape</h2>
<p>While AI may automate some of the tasks traditionally performed by mid-tier developers focused on standardized, routine applications, it simultaneously empowers highly skilled, or &quot;elite,&quot; engineers. These engineers can leverage AI tools to work at an accelerated pace, tackle more complex challenges, and focus on innovative solutions.</p>
<p>The inherent and ever-increasing complexity of software systems across all industries also ensures a continued, fundamental need for skilled human engineers who can design, build, troubleshoot, and maintain these intricate digital ecosystems.</p>
<h2>Collaboration, Not Replacement</h2>
<p>In conclusion, the future of software engineering in an AI-driven world is defined by collaboration and continuous adaptation. AI will undoubtedly continue to automate tasks, boost efficiency, and handle routine operations. This, however, frees up human engineers to focus on higher-value activities that require human ingenuity, critical thinking, and strategic oversight.</p>
<p>To thrive in this evolving landscape, software engineers must embrace AI tools, view them as collaborators, and strategically develop skills in areas that leverage unique human capabilities. Exploring specialized fields at the intersection of AI and critical domains like cybersecurity and IT/OT is also key. The future isn&#x27;t about humans <em>vs.</em> AI, but rather about how humans <em>and</em> AI can collaborate synergistically to build the next generation of technology.</p>]]></content:encoded>
      <category>Software Engineering</category>
      <category>AI</category>
      <category>Future of Tech</category>
      <category>Automation</category>
      <category>Career Skills</category>
      <category>Artificial Intelligence</category>
      <category>Machine Learning</category>
    </item>
    <item>
      <title>Beyond the Hype: Understanding Quantum Computing and Grover's Algorithm</title>
      <link>https://elijah.mondero.nz/post/beyond-the-hype-understanding-quantum-computing-and-grovers-algorithm/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/beyond-the-hype-understanding-quantum-computing-and-grovers-algorithm/</guid>
      <pubDate>Sat, 03 May 2025 05:38:38 +0000</pubDate>
      <description>Quantum computing is often misunderstood. It's not about trying every solution at once, but cleverly manipulating probabilities using qubits and state vectors. Discover how Grover's algorithm offers a significant speedup for search problems without brute force.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/b82fe805-6209-44e1-978f-2fd399b64f7d.png" alt="Beyond the Hype: Understanding Quantum Computing and Grover&#x27;s Algorithm" /></p>
<p>Quantum computing is a hot topic, promising groundbreaking advancements across various fields. However, pop science often simplifies its concepts, leading to significant misconceptions. While it&#x27;s true that quantum computers leverage the strange rules of quantum mechanics, they don&#x27;t work by simply trying every possible solution simultaneously.</p>
<h2>Bits vs. Qubits: A Fundamental Difference</h2>
<p>Classical computers rely on <strong>bits</strong>, which represent either a 0 or a 1. They process information sequentially based on these binary states. Quantum computers, on the other hand, use <strong>qubits</strong>. Unlike bits, qubits can exist in a state of <strong>superposition</strong>, meaning they can represent a combination of both 0 and 1 simultaneously.</p>
<p>This ability for qubits to be in multiple states at once is powerful, but it doesn&#x27;t mean a quantum computer instantly checks every possibility in parallel. Instead, the power lies in the computer&#x27;s ability to hold and manipulate the <em>probabilities</em> of different outcomes.</p>
<h2>The State Vector: Encoding Probabilities</h2>
<p>The state of a quantum computer isn&#x27;t a simple list of 0s and 1s. It&#x27;s described by a <strong>state vector</strong>, a mathematical representation that encodes the probability amplitudes for measuring the system in any of the possible classical states. Think of probability amplitudes as related to the likelihood of observing a particular outcome when the quantum computation finishes.</p>
<p>Quantum programs are essentially sequences of operations (quantum gates) designed to carefully manipulate this state vector. The goal is to steer the computation so that the probability of measuring the <em>correct</em> output is significantly increased, while the probabilities of incorrect outputs are diminished.</p>
<h2>Grover&#x27;s Algorithm: Searching Smarter, Not Harder</h2>
<p>One of the most well-known examples of a quantum algorithm is <strong>Grover&#x27;s algorithm</strong>. It&#x27;s designed to solve the problem of finding a specific item in an unsorted database or list of N items. This is often called the &quot;needle in a haystack&quot; problem.</p>
<p>Classically, finding this item requires checking, on average, about N/2 items. In terms of computational complexity, this scales linearly with the size of the list, denoted as O(N).</p>
<p>Grover&#x27;s algorithm offers a significant speedup. It can find the target item in approximately O(\u221aN) steps. This is a <strong>quadratic speedup</strong>. It&#x27;s crucial to note that this is <em>not</em> an exponential speedup like the one provided by Shor&#x27;s algorithm for factoring numbers.</p>
<h3>Debunking the Brute-Force Myth</h3>
<p>The common misconception about Grover&#x27;s algorithm is that it finds the item by somehow checking all possibilities simultaneously. This is incorrect.</p>
<p>Instead, Grover&#x27;s algorithm works by cleverly manipulating the probability amplitudes associated with each possible state (each item in the list). Through a process called <strong>amplitude amplification</strong>, it repeatedly increases the probability amplitude of the target item&#x27;s state while decreasing the amplitudes of all other states. Geometrically, this can be visualized as rotating the state vector closer and closer to the desired target state within a high-dimensional space.</p>
<p>After a specific number of iterations (related to \u221aN), measuring the quantum computer&#x27;s state has a very high probability of yielding the target item.</p>
<h2>Why the Quadratic Speedup Matters</h2>
<p>While not exponential, a quadratic speedup is still incredibly valuable, especially for large datasets. For a database with a million entries (N=10^6), a classical search might take around 500,000 steps. Grover&#x27;s algorithm could potentially find the item in around \u221a1,000,000 = 1,000 steps. That&#x27;s a considerable difference!</p>
<p>Furthermore, the search problem tackled by Grover&#x27;s algorithm serves as a template for a vast array of problems in computer science. Many problems in the <strong>NP class</strong> (problems whose solutions can be quickly verified, even if finding them is hard) can be framed as search problems. Grover&#x27;s algorithm provides a universal method for obtaining a quadratic speedup for these types of problems.</p>
<h2>The True Power of Quantum Computation</h2>
<p>Quantum computing&#x27;s potential doesn&#x27;t come from a magical ability to try everything at once. Its power lies in harnessing quantum phenomena like superposition and interference to manipulate the probabilities of potential outcomes. Algorithms like Grover&#x27;s demonstrate how this can be used to efficiently guide computation towards a desired solution, offering significant speedups for specific, but broadly applicable, problem types.</p>
<p>Understanding this nuance is essential to appreciating the real challenges and exciting possibilities of the quantum era.</p>]]></content:encoded>
      <category>Quantum Computing</category>
      <category>Grover's Algorithm</category>
      <category>Qubits</category>
      <category>Superposition</category>
      <category>Quantum Algorithms</category>
      <category>Computational Complexity</category>
      <category>NP Problems</category>
      <category>Amplitude Amplification</category>
      <category>Misconceptions</category>
    </item>
    <item>
      <title>SaaS Isn't Dead, It's Getting Smarter: Welcome to the Age of AI-Enhanced Software</title>
      <link>https://elijah.mondero.nz/post/saas-isnt-dead-its-getting-smarter-welcome-to-the-age-of-ai-enhanced-software/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/saas-isnt-dead-its-getting-smarter-welcome-to-the-age-of-ai-enhanced-software/</guid>
      <pubDate>Thu, 01 May 2025 21:06:26 +0000</pubDate>
      <description>Forget the 'SaaS is dead' headlines. Software-as-a-Service is undergoing a massive transformation, powered by AI. Discover how intelligent agents and enhanced interfaces are reshaping the future, making SaaS more powerful and intuitive than ever.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/e2c8ef63-cc37-432b-870b-8418fdc40ac1.png" alt="SaaS Isn&#x27;t Dead, It&#x27;s Getting Smarter: Welcome to the Age of AI-Enhanced Software" /></p>
<p>You might have seen the headlines or heard the whispers: &quot;SaaS is dead.&quot; It&#x27;s a bold claim, often fueled by the rapid advancements in Artificial Intelligence. But let&#x27;s pump the brakes. While the traditional SaaS model is certainly changing, it&#x27;s far from deceased. Instead, we&#x27;re witnessing a powerful evolution, a metamorphosis driven by AI that promises to make software more integrated, intuitive, and valuable than ever before.</p>
<p>Think of it less as an ending and more as the next exciting chapter. SaaS isn&#x27;t disappearing; it&#x27;s getting an upgrade, morphing into AI-assisted interfaces and intelligent agent experiences.</p>
<h2>AI: The Catalyst for SaaS Evolution</h2>
<p>The core concept of delivering software over the internet remains incredibly strong. What&#x27;s changing is <em>how</em> we interact with that software and what it can do for us. AI isn&#x27;t just another feature bolted onto existing SaaS applications; it&#x27;s becoming deeply woven into their fabric.</p>
<p>This integration is leading to several key shifts:</p>
<ol>
<li><strong>The Rise of AI Copilots and Agents:</strong> Tools like Microsoft Copilot are prime examples of this trend. These AI assistants work alongside users <em>within</em> applications, anticipating needs, automating complex workflows, and even orchestrating tasks <em>across</em> different software tools. They understand intent, offer proactive help, and go far beyond simple command execution.</li>
</ol>
<ol>
<li><strong>Shifting Interaction Models:</strong> While the trusty Graphical User Interface (GUI) isn&#x27;t going away completely – after all, most users appreciate visual clarity and aesthetics – how we interact is broadening. We&#x27;ll increasingly use conversational interfaces or delegate multi-step tasks to AI agents. Imagine telling your project management tool, &quot;Draft a project kickoff email based on the latest client notes and schedule a follow-up meeting for next Tuesday,&quot; and having an AI agent handle it, interacting with your email, calendar, and CRM via their APIs.</li>
</ol>
<ol>
<li><strong>SaaS as an Orchestration Layer:</strong> This leads to another fascinating perspective: AI agents acting as orchestrators. In this scenario, the agent becomes the primary interface. It intelligently selects and utilizes various SaaS tools in the background through their APIs to accomplish a user&#x27;s goal. The underlying SaaS applications become powerful, modular components. While this might mean less direct interaction with <em>some</em> individual SaaS UIs for certain tasks, the core SaaS functionality remains essential.</li>
</ol>
<h2>Enhanced Experience, Evolving Models</h2>
<p>Crucially, this evolution is aimed at enhancing user experience and productivity. AI promises to make software:</p>
<ul>
<li><strong>More Intuitive:</strong> Understanding natural language and user intent.</li>
<li><strong>More Efficient:</strong> Automating repetitive and complex tasks.</li>
<li><strong>More Powerful:</strong> Handling sophisticated, multi-app workflows seamlessly.</li>
</ul>
<p>The visual and aesthetic aspects users value aren&#x27;t being discarded; they are being integrated into these new experiences. AI can help tailor interfaces and present information more effectively.</p>
<p>Furthermore, this shift might also influence business models. As AI makes it easier to measure outcomes and automate value delivery, we could see a move beyond simple seat-based licenses towards consumption or outcome-based pricing.</p>
<h2>The Future is AI-Assisted SaaS</h2>
<p>So, is SaaS dead? Absolutely not. It&#x27;s adapting, integrating intelligence, and becoming more powerful. The fundamental value proposition – access to sophisticated software via the internet – remains. What&#x27;s changing is the user experience, driven by AI agents and intelligent interfaces.</p>
<p>Instead of interacting solely through menus and buttons, we&#x27;ll increasingly collaborate with AI copilots, delegate tasks to agents, and experience software that proactively assists us. This isn&#x27;t the death of SaaS; it&#x27;s the dawn of a smarter, more efficient, and ultimately more user-centric era for cloud software.</p>]]></content:encoded>
      <category>SaaS</category>
      <category>AI</category>
      <category>Artificial Intelligence</category>
      <category>Cloud Computing</category>
      <category>Software Evolution</category>
      <category>AI Agents</category>
      <category>Copilots</category>
      <category>User Experience</category>
      <category>Future of Software</category>
    </item>
    <item>
      <title>Beyond Training: Why Test-Time Compute is Reshaping AI Performance</title>
      <link>https://elijah.mondero.nz/post/beyond-training-why-test-time-compute-is-reshaping-ai-performance/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/beyond-training-why-test-time-compute-is-reshaping-ai-performance/</guid>
      <pubDate>Thu, 01 May 2025 10:26:08 +0000</pubDate>
      <description>Explore Test-Time Compute (TTC), the crucial-yet-often-overlooked computational cost of running AI models *after* training. Discover why TTC is a bottleneck for modern AI, its impact on user experience and cost, and how techniques like 'slow thinking' and Meta Reinforcement Fine-Tuning are unlocking new levels of AI reasoning.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/04e94436-9509-4d4a-ab4a-86d2815ed28f.png" alt="Beyond Training: Why Test-Time Compute is Reshaping AI Performance" /></p>
<h2>The Hidden Cost of AI Smarts: Diving into Test-Time Compute</h2>
<p>We hear a lot about the massive computational power needed to <em>train</em> cutting-edge AI models like GPT-4. Training compute is staggering, involving vast datasets and powerful hardware running for weeks or months. But what happens <em>after</em> the training wheels come off? How much power does it take for that trained model to actually answer your question, generate text, or analyze an image?</p>
<p>This is where <strong>Test-Time Compute (TTC)</strong> comes in. Also known as inference compute or inference cost, TTC refers to the computational resources (processing power, memory, time) consumed when a <em>trained</em> model makes predictions or generates outputs on new, unseen data. It&#x27;s the cost of <em>using</em> the AI, and it&#x27;s rapidly becoming one of the most critical factors in modern AI development and deployment.</p>
<p>While training compute grabs headlines, TTC dictates the real-world viability, user experience, and economic feasibility of AI applications.</p>
<h2>From Afterthought to Bottleneck: The Rise of TTC Importance</h2>
<p>In the early days of machine learning, models like linear regressions or simple neural networks were computationally light during inference. TTC was minimal, often overshadowed by the challenges of gathering training data or tuning parameters.</p>
<p>The game changed with Deep Neural Networks (DNNs). As models for image recognition (like ResNet) grew deeper, inference latency started to matter, especially for real-time applications.</p>
<p>Then came the <strong>Transformer era</strong>. Models like BERT, GPT-3, and their successors exploded in size, often boasting hundreds of billions or even trillions of parameters. Training them is an epic undertaking, but deploying them efficiently presents an equally daunting challenge. The sheer size of these models means their TTC is substantial.</p>
<p>Why does this matter so much now?</p>
<ul>
<li><strong>Latency:</strong> Users expect near-instant responses from AI applications like chatbots or search engines. High TTC makes achieving the desired sub-second latency a major hurdle. Delays over 500ms can feel sluggish and degrade the user experience.</li>
<li><strong>Throughput:</strong> TTC determines how many users or requests a deployed model can handle simultaneously, directly impacting its scalability.</li>
<li><strong>Cost:</strong> Running large models, especially on cloud platforms, incurs significant operational expenses, largely driven by inference compute. Optimizing TTC is vital for economic sustainability.</li>
<li><strong>Energy Efficiency:</strong> The continuous computation required for inference contributes significantly to the energy consumption and environmental footprint of AI systems.</li>
</ul>
<p>Suddenly, building a powerful model isn&#x27;t enough. You also need to be able to run it efficiently, affordably, and responsibly.</p>
<h2>The &quot;Slow Thinking&quot; Revolution: Trading Speed for Depth</h2>
<p>A fascinating trend is emerging: deliberately <em>increasing</em> TTC to unlock higher levels of reasoning and performance. This counterintuitive approach draws parallels to human cognition:</p>
<ul>
<li><strong>System 1 Thinking:</strong> Fast, automatic, intuitive (like a quick reflex).</li>
<li><strong>System 2 Thinking:</strong> Slow, effortful, logical, step-by-step reasoning (like solving a complex math problem).</li>
</ul>
<p>Many AI applications prioritize System 1-like speed. However, researchers are finding that allowing models more &quot;thinking time&quot;—more TTC—enables them to tackle complex problems more effectively. Techniques like <strong>Chain-of-Thought (CoT)</strong> prompting, where models explicitly write out intermediate reasoning steps, inherently increase TTC but often lead to dramatically better results on tasks requiring logic and planning.</p>
<p>Models like OpenAI&#x27;s conceptual &quot;o1&quot; and DeepSeek&#x27;s DeepSeek-R1 exemplify this shift. DeepSeek-R1, for instance, uses Reinforcement Learning (RL) techniques <em>during inference</em> to refine its step-by-step reasoning, effectively scaling TTC to boost performance.</p>
<h2>Mastering TTC: Techniques for Optimization and Scaling</h2>
<p>Research in TTC tackles two main goals: <em>reducing</em> baseline TTC for efficiency and <em>effectively utilizing increased</em> TTC for enhanced capabilities.</p>
<p>Here are some key methods:</p>
<ol>
<li><strong>Chain-of-Thought (CoT) / Step-by-Step Reasoning:</strong> Intentionally structuring prompts or model outputs to include intermediate steps, using more compute for better reasoning.</li>
<li><strong>Test-Time Training (TTT):</strong> Allowing the model to continue adapting or fine-tuning itself based on the specific data it encounters <em>during</em> the inference phase.</li>
<li><strong>Reinforcement Learning (RL) for Inference:</strong> Using RL to guide the model&#x27;s generation process at test time. This can range from basic outcome-based rewards to more sophisticated methods.</li>
<li><strong>Meta Reinforcement Fine-Tuning (MRT):</strong> An advanced RL technique proposed in recent research (arXiv:2503.07572). MRT formalizes TTC optimization as a meta-RL problem, viewing the output generation as a series of steps. It uses a dense reward signal measuring &quot;progress&quot; towards the correct answer at each step, helping the model better balance exploring different reasoning paths versus exploiting known good ones. This approach has shown significant performance and efficiency gains, particularly in math reasoning tasks.</li>
<li><strong>Search Algorithms:</strong> Integrating methods like Monte Carlo Tree Search during inference allows models to explore multiple potential solution paths before selecting an answer.</li>
<li><strong>Retrieval Augmentation:</strong> Equipping models with the ability to search for and incorporate external information during inference (like the &quot;Search-o1&quot; concept) adds compute but can ground responses and improve accuracy.</li>
<li><strong>Traditional Optimization:</strong> Standard techniques like model compression (quantization, pruning), knowledge distillation, and hardware acceleration (GPUs, TPUs) remain crucial for reducing the fundamental TTC of any given model.</li>
</ol>
<h2>The Balancing Act: Challenges and the Future of TTC</h2>
<p>The core challenge lies in the trade-off: boosting model capability via increased TTC often comes at the cost of higher latency, increased operational expenses, and greater energy use.</p>
<p>The focus, therefore, is shifting towards <em>compute efficiency</em>: getting the maximum reasoning improvement per unit of TTC. Techniques like MRT are promising steps in this direction.</p>
<p>Making these advanced TTC optimization and scaling methods accessible beyond large, well-funded labs is another hurdle.</p>
<p>Despite the challenges, optimizing and strategically scaling test-time compute is viewed by many experts as a critical frontier in AI. Some even suggest it could be as transformative as the Transformer architecture itself. Why? Because TTC directly governs how the most powerful AI models translate their potential into tangible, usable, and economically viable real-world applications.</p>
<p>As models continue to grow and our expectations for AI reasoning deepen, mastering the art and science of test-time compute will be paramount. It&#x27;s no longer just about training the smartest model; it&#x27;s about enabling that model to think effectively and efficiently when it truly matters.</p>]]></content:encoded>
      <category>AI</category>
      <category>Machine Learning</category>
      <category>Test-Time Compute</category>
      <category>TTC</category>
      <category>Inference</category>
      <category>Large Language Models</category>
      <category>LLM</category>
      <category>Optimization</category>
      <category>Chain-of-Thought</category>
      <category>Reinforcement Learning</category>
      <category>Meta Reinforcement Fine-Tuning</category>
      <category>Latency</category>
      <category>Cost Optimization</category>
      <category>AI Performance</category>
      <category>Deep Learning</category>
      <category>Transformers</category>
    </item>
    <item>
      <title>Supercharge Your Startup: Building with NotebookLM, Gemini, and Firebase</title>
      <link>https://elijah.mondero.nz/post/supercharge-your-startup-building-with-notebooklm-gemini-and-firebase/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/supercharge-your-startup-building-with-notebooklm-gemini-and-firebase/</guid>
      <pubDate>Sun, 27 Apr 2025 21:01:14 +0000</pubDate>
      <description>Discover how the powerful combination of Google's NotebookLM, Gemini AI, and Firebase can streamline your startup journey from ideation to launch. Learn practical steps to leverage these tools for research, development, and scaling.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/78208b98-e5b9-4a43-8abd-cbdc845775e9.png" alt="Supercharge Your Startup: Building with NotebookLM, Gemini, and Firebase" /></p>
<p>Launching a startup is a whirlwind of activity – market research, refining ideas, building a product, finding users, and scaling operations. It&#x27;s demanding, often requiring significant resources and technical expertise. But what if you could streamline this process with powerful, integrated AI tools?</p>
<p>Introducing the combination of Google&#x27;s NotebookLM, Gemini, and Firebase. This tech trio offers a modern approach to building startups, leveraging AI for insights and efficiency alongside a robust development platform.</p>
<h2>The Tools: Your AI-Powered Startup Toolkit</h2>
<p>Let&#x27;s break down the role each component plays:</p>
<h3>1. NotebookLM: Your Virtual Research Assistant</h3>
<ul>
<li><strong>Role:</strong> Research Synthesis &amp; Ideation Hub</li>
<li><strong>How it Works:</strong> NotebookLM acts as your personal AI research assistant. You feed it your source materials – PDFs of market reports, Google Docs with interview notes, web links to competitors, text files with brainstorming snippets. Powered by Gemini, NotebookLM analyzes <em>only these sources</em> to:</li>
<li>Summarize complex information.</li>
<li>Identify key themes and patterns across documents.</li>
<li>Compare different perspectives or findings.</li>
<li>Brainstorm solutions based on the data.</li>
<li>Generate outlines for business plans or content.</li>
<li><strong>Startup Application:</strong> Ditch the chaos of scattered research notes. Use NotebookLM to deeply understand customer pain points, analyze industry trends, dissect competitor strategies, and consolidate all your findings to shape a truly data-driven startup idea.</li>
</ul>
<h3>2. Gemini: The Intelligent Engine</h3>
<ul>
<li><strong>Role:</strong> AI Powerhouse &amp; Developer Co-pilot</li>
<li><strong>How it Works:</strong> Gemini is the advanced AI model driving the intelligence in both NotebookLM and, crucially, within the Firebase development environment.</li>
<li><strong>In NotebookLM:</strong> It enables powerful analysis and content generation based on your uploaded sources.</li>
<li><strong>In Firebase (&quot;Gemini in Firebase&quot; / &quot;Firebase Studio&quot;):</strong> This is where Gemini transforms into an AI coding partner. Directly within the Firebase console or the integrated Firebase Studio environment, Gemini can:</li>
<li>Brainstorm app features.</li>
<li>Generate code snippets (e.g., Cloud Functions, Firestore rules).</li>
<li>Explain existing codebases.</li>
<li>Help identify security vulnerabilities.</li>
<li>Assist with debugging and troubleshooting.</li>
<li>Guide you through setting up Firebase projects and services.</li>
<li><strong>Startup Application:</strong> Gemini significantly accelerates the development cycle. It helps write cleaner, more secure code faster, reduces the time spent debugging, and lowers the barrier for developers (even solo founders or small teams) to build sophisticated features on Firebase. You can even integrate the Gemini API directly into your application to offer AI-powered features to your users.</li>
</ul>
<h3>3. Firebase: The Scalable Foundation</h3>
<ul>
<li><strong>Role:</strong> Backend Infrastructure &amp; Development Platform</li>
<li><strong>How it Works:</strong> Firebase provides the essential backend services needed to build and scale modern web and mobile apps without managing servers. This includes:</li>
<li>Databases (Firestore, Realtime Database)</li>
<li>User Authentication</li>
<li>Static Web Hosting</li>
<li>Serverless Functions (Cloud Functions for Firebase)</li>
<li>App Distribution (for testing)</li>
<li>Analytics, and more.</li>
<li><strong>Startup Application:</strong> Firebase is the technical bedrock of your product. It handles the complex infrastructure, allowing your team to focus on building features. Its pay-as-you-go model and scalability are perfect for startups that need to start lean and grow quickly. The integration of Gemini makes navigating and utilizing these powerful services even easier.</li>
</ul>
<h2>The Synergy: A Streamlined Startup Workflow</h2>
<p>Here’s how these tools work together:</p>
<ol>
<li><strong>Research &amp; Ideation (NotebookLM + Gemini):</strong> Upload all your market research, user interviews, and competitor analyses into NotebookLM. Use its Gemini-powered features to synthesize insights, identify your target niche, validate your core assumptions, and brainstorm unique value propositions.</li>
<li><strong>Planning &amp; Design:</strong> Armed with clear insights from NotebookLM, define your Minimum Viable Product (MVP) features and user flows.</li>
<li><strong>Development (Firebase + Gemini):</strong> Build your app&#x27;s backend and frontend using Firebase services. Leverage &quot;Gemini in Firebase&quot; or the integrated &quot;Firebase Studio&quot; to generate boilerplate code, write secure database rules, develop backend logic with Cloud Functions, and troubleshoot issues faster.</li>
<li><strong>Testing (Firebase + Gemini):</strong> Utilize Firebase App Distribution for deploying test builds. Gemini might even assist in generating test plans or simulating user interactions in the future (as hinted by features like the App Testing agent).</li>
<li><strong>Promotion (NotebookLM + Gemini - Potential):</strong> Use NotebookLM to ground your marketing message in your research, and leverage Gemini (perhaps via NotebookLM or directly) to help draft initial blog posts, social media updates, or ad copy based on your product features and validated user needs.</li>
</ol>
<h2>Why This Matters for Your Startup</h2>
<p>This AI-enhanced stack offers significant advantages:</p>
<ul>
<li><strong>Speed:</strong> Accelerate both research and development phases.</li>
<li><strong>Efficiency:</strong> Reduce manual effort in data synthesis and coding.</li>
<li><strong>Focus:</strong> Spend more time on strategy and innovation, less on infrastructure and repetitive tasks.</li>
<li><strong>Accessibility:</strong> Lower the technical barrier for building sophisticated applications.</li>
</ul>
<p>By integrating NotebookLM for intelligent research, Firebase for a scalable backend, and Gemini as the AI force multiplier across the board, startups can move from concept to reality faster and more effectively than ever before.</p>
<p>Ready to build the future? Explore these tools and see how they can supercharge <em>your</em> startup journey.</p>]]></content:encoded>
      <category>Startup</category>
      <category>AI</category>
      <category>Artificial Intelligence</category>
      <category>Google</category>
      <category>NotebookLM</category>
      <category>Gemini</category>
      <category>Firebase</category>
      <category>Development</category>
      <category>Cloud Computing</category>
      <category>Tech Stack</category>
      <category>Entrepreneurship</category>
      <category>MVP</category>
      <category>BaaS</category>
    </item>
    <item>
      <title>Building Step-by-Step AI Workflows with Google ADK's SequentialAgent</title>
      <link>https://elijah.mondero.nz/post/building-step-by-step-ai-workflows-with-google-adks-sequentialagent/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/building-step-by-step-ai-workflows-with-google-adks-sequentialagent/</guid>
      <pubDate>Sun, 27 Apr 2025 01:18:43 +0000</pubDate>
      <description>Explore how Google's Agent Development Kit (ADK) simplifies multi-agent system creation, focusing on the SequentialAgent – a powerful tool for building structured, step-by-step AI workflows by orchestrating tasks in a defined sequence.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/993b95f5-3ba7-4c81-9c6f-7d125fcedd74.png" alt="Building Step-by-Step AI Workflows with Google ADK&#x27;s SequentialAgent" /></p>
<p>The world of AI is rapidly evolving, moving beyond simple, single-purpose models towards sophisticated systems capable of handling complex tasks by coordinating multiple specialized AI components. This is the realm of multi-agent systems.</p>
<p>To empower developers in building these advanced systems, Google has introduced the <strong>Agent Development Kit (ADK)</strong>. This open-source Python framework is designed to streamline the creation, testing, and deployment of AI agents and multi-agent applications, providing flexibility and precise control.</p>
<h2>The Role of Workflow Agents in ADK</h2>
<p>Within the ADK, <strong>Workflow Agents</strong> are crucial for defining the execution flow of tasks within a multi-agent system. They provide deterministic control, ensuring structured and predictable application behavior.</p>
<p>ADK offers different types of Workflow Agents to suit various needs:</p>
<ul>
<li><strong>ParallelAgent</strong>: Ideal for efficiency, executing multiple sub-agents concurrently.</li>
<li><strong>SequentialAgent</strong>: Perfect for tasks requiring a defined order, orchestrating sub-agents step-by-step.</li>
</ul>
<h2>Deep Dive: Understanding the SequentialAgent</h2>
<p>The <strong>SequentialAgent</strong> is a cornerstone of building structured workflows in ADK. As its name implies, it allows you to define a clear, ordered sequence of operations for your agents.</p>
<p>With a SequentialAgent, you can ensure that sub-agents are executed one after the other, with the output of a preceding agent often serving as the input for the next. This pattern is invaluable for tasks that naturally break down into a series of dependent steps.</p>
<p>Consider a typical application scenario:</p>
<ol>
<li>An initial agent might be tasked with gathering relevant information from various sources.</li>
<li>A second agent could then take that gathered information and process or analyze it.</li>
<li>Finally, a third agent might use the processed data to generate a response, summarize findings, or perform an action.</li>
</ol>
<p>The SequentialAgent provides the precise control needed to manage this kind of pipeline. It guarantees that each step is completed successfully before the next one begins, leading to more reliable, predictable, and debuggable outcomes compared to less structured approaches.</p>
<h2>Getting Started: SequentialAgent and Code Structure</h2>
<p>The ADK is designed with Pythonic simplicity in mind, making it accessible to developers familiar with Python. While full, runnable examples for <code>SequentialAgent</code> are best found in the official Google ADK documentation and quickstart guides, the structure begins with importing the necessary class.</p>
<p>Here&#x27;s a basic glimpse of how you might import and reference a <code>SequentialAgent</code>:</p>
<pre>from google.adk.agents import SequentialAgent

# Example initialization (structure may vary based on specific ADK version/use case)
# agent_teaching_assistant = SequentialAgent(
#     name=&quot;agent_teaching_assistant&quot;,
#     description=&quot;This agent acts as a friendly teaching assistant, checking ...&quot;,
#     # ... other configuration like defining the sequence of sub-agents
# )
</pre>
<p>This snippet shows the fundamental step: importing the <code>SequentialAgent</code> class from the <code>google.adk.agents</code> module. The subsequent steps in building a workflow involve defining the sub-agents that the <code>SequentialAgent</code> will orchestrate and specifying their order of execution.</p>
<p>For comprehensive, runnable code examples and tutorials on how to define sub-agents, configure their inputs/outputs, and integrate them within a <code>SequentialAgent</code> workflow, the official Google ADK resources are the definitive source.</p>
<h2>Conclusion</h2>
<p>Google&#x27;s SequentialAgent, as a core component of the Agent Development Kit, offers a powerful and intuitive way to build structured, multi-step AI workflows. By enabling the orchestration of specialized agents in a defined sequence, it provides developers with the control needed to create reliable and complex multi-agent applications. If you&#x27;re looking to build AI systems that require a predictable flow of information processing and action, exploring the SequentialAgent within the Google ADK is a valuable next step.</p>]]></content:encoded>
      <category>AI Agents</category>
      <category>Multi-agent Systems</category>
      <category>Google ADK</category>
      <category>SequentialAgent</category>
      <category>Workflow Automation</category>
      <category>AI Orchestration</category>
      <category>Python</category>
      <category>AI Development</category>
      <category>Machine Learning</category>
    </item>
    <item>
      <title>Boost Your VS Code Workflow: Using Google Gemini with the 'cline' Extension</title>
      <link>https://elijah.mondero.nz/post/boost-your-vs-code-workflow-using-google-gemini-with-the-cline-extension/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/boost-your-vs-code-workflow-using-google-gemini-with-the-cline-extension/</guid>
      <pubDate>Sat, 26 Apr 2025 09:54:04 +0000</pubDate>
      <description>Bring the power of Google Gemini's AI coding assistance directly into your VS Code editor with the 'cline' extension. Streamline your development process and get context-aware help without leaving your IDE.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/41c29aa3-3ed2-4fc2-8fb6-358819bad407.png" alt="Boost Your VS Code Workflow: Using Google Gemini with the &#x27;cline&#x27; Extension" /></p>
<h2>What is &#x27;cline&#x27;?</h2>
<p>&#x27;cline&#x27; is a Visual Studio Code extension engineered to embed AI capabilities right within your coding interface. It provides a direct way to interact with powerful language models, offering features that can assist with a wide range of coding tasks, from generating code snippets to explaining complex logic.</p>
<h2>Why Use &#x27;cline&#x27; with Google Gemini?</h2>
<p>Combining &#x27;cline&#x27; with Google Gemini offers compelling advantages:</p>
<ul>
<li><strong>Seamless Integration:</strong> Receive AI assistance without ever leaving your VS Code environment or switching applications.</li>
<li><strong>Context-Aware Assistance:</strong> &#x27;cline&#x27; can leverage the context of the code you&#x27;re actively working on, enabling Gemini to provide more relevant and accurate suggestions.</li>
<li><strong>Access to Powerful Models:</strong> Utilize the advanced capabilities of models like Google Gemini (potentially supporting various tiers depending on configuration) to tackle complex coding challenges.</li>
<li><strong>Increased Efficiency:</strong> Accelerate tasks like code generation, refactoring, debugging, and code comprehension, leading to a more streamlined development cycle.</li>
</ul>
<p>&#x27;cline&#x27; aims to make advanced AI assistance more accessible to individual developers by offering ways to leverage powerful Gemini models, potentially including access to specific tiers or features.</p>
<h2>Getting Started</h2>
<p>While specific steps may vary slightly based on updates, getting started typically involves a straightforward process:</p>
<ol>
<li>Install the &#x27;cline&#x27; extension directly from the VS Code Marketplace.</li>
<li>Configure the extension, which generally requires connecting your Google Gemini API key or account.</li>
<li>Begin interacting with the AI assistant through &#x27;cline&#x27;s integrated interface within VS Code.</li>
</ol>
<p>For precise and detailed setup instructions, always consult the official &#x27;cline&#x27; documentation or relevant guides.</p>
<h2>Unleash Your Coding Potential</h2>
<p>By integrating Google Gemini through the &#x27;cline&#x27; VS Code extension, you can unlock significant improvements in productivity and efficiency. Whether you need help generating boilerplate code, understanding intricate legacy systems, or identifying elusive bugs, having a powerful AI assistant integrated directly into your IDE can fundamentally transform your workflow.</p>
<p>Explore how &#x27;cline&#x27; and Google Gemini can enhance your coding experience and empower you to build better software, faster.</p>]]></content:encoded>
      <category>VS Code</category>
      <category>Google Gemini</category>
      <category>AI Coding</category>
      <category>Coding Assistant</category>
      <category>cline</category>
      <category>Extension</category>
      <category>Developer Tools</category>
      <category>Programming</category>
    </item>
    <item>
      <title>Exploring the Strengths of GPT-4.1 in Tool Calling and Coding</title>
      <link>https://elijah.mondero.nz/post/exploring-the-strengths-of-gpt-41-in-tool-calling-and-coding/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/exploring-the-strengths-of-gpt-41-in-tool-calling-and-coding/</guid>
      <pubDate>Mon, 21 Apr 2025 20:15:40 +0000</pubDate>
      <description>With the release of GPT-4.1, OpenAI has presented significant improvements in tool calling and coding capabilities. This blog delves into these enhancements, drawing insights from OpenAI's announcements and Reddit forums, offering a comprehensive view of its performance and potential applications.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/445ec42c-ba5c-46c4-b9cc-fb6be6e51139.png" alt="Exploring the Strengths of GPT-4.1 in Tool Calling and Coding" /></p>
<p>With the unveiling of GPT-4.1, OpenAI has brought forward notable advancements in artificial intelligence, particularly in areas such as tool calling and coding. This latest iteration of the GPT series is designed to bolster a developer&#x27;s toolkit, addressing previous limitations and providing new features worth discussing.</p>
<h2>Key Enhancements in GPT-4.1</h2>
<h3>Improved Tool Calling Mechanism</h3>
<p>GPT-4.1 has undergone extensive training to enhance its efficiency in utilizing tools. Unlike its predecessors, which sometimes required developers to manually inject tool descriptions into prompts, GPT-4.1 leverages a sophisticated mechanism that accepts tools as arguments directly in an API request. This streamlined approach not only saves time but also reduces the error margin associated with manual parsing of tool calls.</p>
<h3>Enhanced Coding Capabilities</h3>
<p>The model has achieved a remarkable milestone in coding, doubling the score of GPT-4o on Aider&#x27;s polyglot diff benchmark and surpassing GPT-4.5 by 8%. This indicates a significant boost in handling code diffs across various programming languages, exemplifying its versatility and reliability for developers working with extensive and complex codebases.</p>
<h3>Larger Context Windows</h3>
<p>One of the standout features of GPT-4.1 is its ability to support up to 1 million tokens of context. This expansion allows the model to comprehend and utilize long-context information more effectively, which is particularly beneficial for projects requiring extensive code and detailed instructions. This improvement ensures that context is maintained accurately over longer code scripts, enhancing the overall coding experience.</p>
<h2>Community Insights and Discussions</h2>
<h3>Reddit Feedback</h3>
<p>The developer and AI enthusiast communities on Reddit have been actively discussing the capabilities and performance of GPT-4.1. Generally, the feedback highlights that GPT-4.1 is a substantial improvement over previous models in terms of tool calling and coding. Users have noted that the model performs well in complex coding tasks and long-context comprehension. However, some skepticism remains about its performance in highly intricate or large-scale projects beyond typical corporate or homework assignments.</p>
<h3>Real-world Applications</h3>
<p>Several Reddit users have shared their experiences with GPT-4.1 in real-world applications. A notable mention is how the model has been used efficiently in Copilot for basic to intermediate tasks within existing codebases, leading to productivity boosts. Additionally, some developers noted that by packing relevant code routes in an AI-friendly format, GPT-4.1 could successfully navigate and enhance large coding projects with multiple models ensuring thorough coverage.</p>
<h2>Conclusion</h2>
<p>The enhancements in GPT-4.1 reflect OpenAI’s commitment to evolving their models to meet the growing demands of developers. The model&#x27;s superior tool calling, enhanced coding capabilities, and expanded context windows position it as a valuable asset in both everyday coding tasks and more intricate projects. While there is always room for improvement, particularly in agentic coding tools for extremely large projects, GPT-4.1 marks a significant step forward in AI-driven development assistance.</p>
<p>As the community continues to explore and push the boundaries of what GPT-4.1 can do, we can anticipate even more innovative uses and improvements in future iterations.</p>]]></content:encoded>
      <category>AI</category>
      <category>GPT-4.1</category>
      <category>OpenAI</category>
      <category>Tool Calling</category>
      <category>Coding</category>
      <category>Technology</category>
    </item>
    <item>
      <title>Introducing Google's New Agent-to-Agent (A2A) Framework</title>
      <link>https://elijah.mondero.nz/post/introducing-googles-new-agent-to-agent-a2a-framework/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/introducing-googles-new-agent-to-agent-a2a-framework/</guid>
      <pubDate>Fri, 11 Apr 2025 23:38:03 +0000</pubDate>
      <description>Discover Google's latest framework, Agent-to-Agent (A2A), designed to facilitate seamless communication and collaboration between various AI agents.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/b5d20ad9-07d4-48a8-8125-a72e63e028eb.png" alt="Introducing Google&#x27;s New Agent-to-Agent (A2A) Framework" /></p>
<p>Google has unveiled a new framework called Agent-to-Agent (A2A) that aims to revolutionize the way AI agents communicate and collaborate with each other. This new protocol is designed to address the challenges of coordinating multiple agents, enhancing their ability to work together more efficiently.</p>
<h2>What is A2A?</h2>
<p>The Agent-to-Agent (A2A) framework is a streamlined protocol created by Google to enable seamless interactions between different AI agents. It provides a standardized way for agents to share information, delegate tasks, and cooperate on complex operations.</p>
<h2>Key Features of A2A</h2>
<ul>
<li><strong>Standardized Communication</strong>: A2A offers a consistent way for agents to exchange data, ensuring clear and unambiguous communication.</li>
<li><strong>Task Delegation</strong>: Agents can delegate specific tasks to other agents that are better suited to handle them, optimizing the overall workflow.</li>
<li><strong>Enhanced Collaboration</strong>: By facilitating better coordination, A2A enables agents to tackle more complex problems together.</li>
<li><strong>Scalability</strong>: The framework is designed to scale easily, supporting numerous agents and a wide range of applications.</li>
</ul>
<h2>Use Cases</h2>
<p>The A2A framework can be applied in various fields such as robotics, autonomous vehicles, smart home systems, and more. In these environments, multiple AI agents need to collaborate to perform tasks efficiently and effectively.</p>
<h2>Conclusion</h2>
<p>Google’s Agent-to-Agent (A2A) framework represents a significant step forward in the development of AI technologies. By providing a robust protocol for agent communication and collaboration, A2A has the potential to enhance the performance and capabilities of AI systems across multiple domains.</p>]]></content:encoded>
      <category>Google</category>
      <category>A2A</category>
      <category>AI Framework</category>
      <category>Agent-to-Agent</category>
      <category>Technology</category>
    </item>
    <item>
      <title>The Dawn of Diffusion Large Language Models: Introducing Mercury by Inception Labs</title>
      <link>https://elijah.mondero.nz/post/the-dawn-of-diffusion-large-language-models-introducing-mercury-by-inception-labs/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/the-dawn-of-diffusion-large-language-models-introducing-mercury-by-inception-labs/</guid>
      <pubDate>Sun, 06 Apr 2025 17:44:59 +0000</pubDate>
      <description>Inception Labs has introduced a groundbreaking approach to AI with Diffusion Large Language Models (dLLMs). Their first commercial product, Mercury, promises faster and more efficient text generation, marking a significant advancement in the field.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/74635d2e-cf19-486f-be20-1c3f5ddc9eee.png" alt="The Dawn of Diffusion Large Language Models: Introducing Mercury by Inception Labs" /></p>
<p>For years, large language models (LLMs) have operated within a well-defined paradigm: autoregression. Each word or token is generated sequentially, creating a fundamental bottleneck in speed and efficiency. This has led to increasing inference costs and latency issues as AI-generated text becomes more complex. Now, Inception Labs, a startup co-founded by Stanford professor Stefano Ermon and his colleagues Volodymyr Kuleshov and Aditya Grover, is introducing a different approach with Diffusion Large Language Models (dLLMs). Their first commercial-scale product, Mercury, aims to disrupt the status quo by offering significantly faster and more efficient text generation.</p>
<h2>The Diffusion Model Shift</h2>
<p>Traditional LLMs, including OpenAI’s GPT-4o and Anthropic’s Claude 3.5 Haiku, generate text in a left-to-right fashion, with each token dependent on those before it. While this sequential process allows for contextual depth, it also means that longer responses come with exponentially increasing computational costs. Companies optimizing these models have focused on test-time computation to improve reasoning, but this approach has created trade-offs in speed and usability.</p>
<p>Diffusion models, by contrast, operate differently. Rather than generating one token at a time, they use a “coarse-to-fine” approach, refining an initial rough estimate in parallel over a series of denoising steps. This method is widely used in AI-generated images, video, and audio—powering tools like OpenAI’s Sora, Midjourney, and Riffusion—but its application to text has been largely unsuccessful. Until now.</p>
<blockquote><p>“Diffusion models start with a rough estimate of data and refine it all at once,” Ermon told TechCrunch. “With LLMs, you cannot generate the second word until you’ve generated the first one, and you cannot generate the third one until you generate the first two.” By leveraging diffusion’s unique structure, Mercury’s dLLMs aim to bypass these constraints and deliver responses more efficiently than their autoregressive counterparts.</p></blockquote>
<h2>Mercury: High-Speed Language Generation</h2>
<p>Mercury claims to be up to 10 times faster than the most speed-optimized LLMs. While traditional models max out at around 200 tokens per second, Mercury achieves over 1,000 tokens per second on commodity NVIDIA H100 GPUs—a speed previously only possible with custom hardware like Groq, Cerebras, or SambaNova. Compared to some frontier models running at less than 50 tokens per second, Mercury offers a 20x speedup.</p>
<p>The first Mercury release, Mercury Coder, is optimized for code generation and outperforms existing speed-optimized models such as GPT-4o Mini and Claude 3.5 Haiku on standard coding benchmarks. Despite its faster inference speed, Mercury Coder maintains a competitive level of quality, proving that diffusion-based models can hold their own against top-tier autoregressive LLMs.</p>
<p>A company spokesperson emphasized the impact of these improvements:</p>
<blockquote><p>“Our ‘small’ coding model is as good as [OpenAI’s] GPT-4o Mini while more than 10 times as fast. Our ‘mini’ model outperforms small open-source models like [Meta’s] Llama 3.1 8B and achieves more than 1,000 tokens per second.”</p></blockquote>
<h2>Addressing the Cost of AI</h2>
<p>One of the biggest challenges in AI deployment today is the rising cost of inference. LLMs require substantial computational power, and the increasing complexity of reasoning traces has made cost reduction difficult. Mercury’s diffusion-based approach has the potential to make high-quality AI more accessible by dramatically lowering the price of inference.</p>
<p>“Our models leverage GPUs much more efficiently,” Ermon noted. “I think this is a big deal. This is going to change the way people build language models.”</p>
<p>Unlike other speed-focused AI solutions that rely on specialized chips, Mercury’s speed improvements come from algorithmic advancements rather than hardware dependence. This means that as GPU technology continues to advance, Mercury’s performance gains could further compound.</p>
<h2>Enterprise Access and Adoption</h2>
<p>Mercury is available to enterprise customers through both an API and on-premise deployments, allowing businesses to integrate high-speed language generation into their operations seamlessly.</p>]]></content:encoded>
      <category>AI</category>
      <category>Machine Learning</category>
      <category>Diffusion Models</category>
      <category>Language Models</category>
      <category>Inception Labs</category>
      <category>Mercury</category>
    </item>
    <item>
      <title>Meta Ushers in a New Era with LLaMA 4: A Leap in Multimodal AI Innovation</title>
      <link>https://elijah.mondero.nz/post/meta-ushers-in-a-new-era-with-llama-4-a-leap-in-multimodal-ai-innovation/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/meta-ushers-in-a-new-era-with-llama-4-a-leap-in-multimodal-ai-innovation/</guid>
      <pubDate>Sun, 06 Apr 2025 04:14:12 +0000</pubDate>
      <description>Meta has released LLaMA 4, introducing advanced multimodal AI models—LLaMA 4 Scout, LLaMA 4 Maverick, and previewing the powerful LLaMA 4 Behemoth, aimed at revolutionizing personalized AI experiences.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/9d323dbe-31b0-4406-9d49-e922e3415637.png" alt="Meta Ushers in a New Era with LLaMA 4: A Leap in Multimodal AI Innovation" /></p>
<p>Meta Platforms has announced the release of its newest series of large language models (LLM), LLaMA 4, marking a significant advancement in the field of artificial intelligence. The release includes LLaMA 4 Scout, LLaMA 4 Maverick, and a preview of LLaMA 4 Behemoth, each designed to deliver more powerful and personalized multimodal experiences.</p>
<h3><strong>LLaMA 4 Scout and Maverick: Leading the Multimodal Revolution</strong></h3>
<p>LLaMA 4 Scout is equipped with 17 billion active parameters and 16 experts, making it the world&#x27;s best multimodal model in its class. It stands out for its efficiency, fitting into a single NVIDIA H100 GPU, and offers an industry-leading context window of 10 million tokens. This model surpasses previous versions and competitors, achieving superior results across a wide range of benchmarks.</p>
<p>LLaMA 4 Maverick, also a 17 billion active parameter model with 128 experts, excels in multimodal performance, outperforming industry benchmarks such as GPT-4.0 and Gemini 2.0 Flash. It offers a remarkable performance-to-cost ratio and an experimental chat version with an ELO score of 1417 on LMArena, demonstrating its proficiency in reasoning and coding tasks.</p>
<h3><strong>LLaMA 4 Behemoth: A Glimpse into the Future</strong></h3>
<p>The LLaMA 4 Behemoth, a model with 288 billion active parameters and 16 experts, remains under training. Despite this, early performance indicators show it surpassing GPT-4.5, Claude Sonnet 3.7, and Gemini 2.0 Pro on crucial STEM benchmarks. LLaMA 4 Behemoth&#x27;s advanced capabilities make it one of the smartest LLMs globally, setting a new precedence in AI innovation.</p>
<h3><strong>Accessible AI for All</strong></h3>
<p>As part of Meta&#x27;s commitment to openness and innovation, LLaMA 4 Scout and Maverick are available for download on llama.com and Hugging Face. Additionally, users can experience LLaMA 4 through Meta AI in platforms like WhatsApp, Messenger, and Instagram Direct. Meta aims to ensure that the leading models and systems are transparently available to foster a new era of personalized AI-driven experiences.</p>
<h3><strong>Future Prospects</strong></h3>
<p>Meta&#x27;s introduction of the LLaMA 4 series signifies the beginning of a transformative phase for the LLaMA ecosystem. The company remains dedicated to advancing AI research, promoting openness, and providing developers and enterprises with the tools necessary to integrate cutting-edge AI capabilities into their products and services.</p>
<p>Join Meta at LlamaCon on April 29 to learn more about the future of AI and the exciting developments within the LLaMA ecosystem.</p>]]></content:encoded>
      <category>Meta</category>
      <category>AI</category>
      <category>LLaMA 4</category>
      <category>Multimodal AI</category>
      <category>Artificial Intelligence</category>
    </item>
    <item>
      <title>OpenAI Agents SDK Adds Support for Model Context Protocol (MCP)</title>
      <link>https://elijah.mondero.nz/post/openai-agents-sdk-adds-support-for-model-context-protocol-mcp/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/openai-agents-sdk-adds-support-for-model-context-protocol-mcp/</guid>
      <pubDate>Thu, 27 Mar 2025 07:27:18 +0000</pubDate>
      <description>OpenAI recently announced the integration of Model Context Protocol (MCP) into their Agents SDK. This addition bridges the gap between AI models and various data sources, making AI development more efficient and versatile.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/b83ba0c9-4e21-4ef7-b5c9-2c7f00c832aa.png" alt="OpenAI Agents SDK Adds Support for Model Context Protocol (MCP)" /></p>
<p>The OpenAI Agents SDK has recently integrated support for the Model Context Protocol (MCP), a significant advancement that bridges the gap between large language models (LLMs) and various data sources and tools. This article delves into the specifics of MCP, its implementations, and the potential benefits it brings to AI development.</p>
<h2>What is MCP?</h2>
<p>The Model Context Protocol (MCP) is an open protocol designed to standardize how applications provide context to LLMs. Similar to how USB-C standardizes connections between devices and peripherals, MCP provides a consistent way to connect AI models to different tools and data sources. This standardization simplifies the process of providing context to AI applications, enhancing their ability to perform complex tasks using external data and tools.</p>
<h2>Implementing MCP in Agents SDK</h2>
<p>The integration of MCP into the OpenAI Agents SDK means developers can now leverage a wide range of MCP servers to equip their AI agents with various tools. MCP servers can be categorized into two types based on their transport mechanism:</p>
<ul>
<li><strong>stdio servers:</strong> These servers run as a subprocess of your application, meaning they operate locally.</li>
<li><strong>HTTP over SSE servers:</strong> These servers run remotely and are accessed through a URL.</li>
</ul>
<p>Developers can use the <code>MCPServerStdio</code> and <code>MCPServerSse</code> classes to connect to these servers and incorporate their tools into AI agents.</p>
<h3>Using MCP Servers</h3>
<p>MCP servers can be seamlessly added to agents in the SDK. Each time the agent runs, it queries the MCP server for a list of available tools, ensuring the LLM is aware of all the functionalities provided by the server. Here’s an example of integrating an MCP server:</p>
<pre>agent = Agent(
    name=&quot;Assistant&quot;,
    instructions=&quot;Use the tools to achieve the task&quot;,
    mcp_servers=[mcp_server_1, mcp_server_2]
)
</pre>
<h3>Caching and Performance Optimization</h3>
<p>To reduce latency, especially when using remote servers, the SDK allows for caching the list of tools provided by an MCP server. By passing <code>cache_tools_list=True</code> to <code>MCPServerStdio</code> and <code>MCPServerSse</code>, developers can ensure the agent retrieves the tool list quickly without repeated calls to the server.</p>
<h2>Benefits of MCP Integration</h2>
<p>The inclusion of MCP in the OpenAI Agents SDK provides several benefits:</p>
<ul>
<li><strong>Standardization:</strong> MCP offers a uniform way to connect LLMs to various tools and data sources, streamlining the development process.</li>
<li><strong>Flexibility:</strong> Developers can choose between local and remote MCP servers based on their application requirements.</li>
<li><strong>Efficiency:</strong> Tool caching and efficient querying reduce latency and improve overall performance.</li>
</ul>
<h2>Conclusion</h2>
<p>The support for MCP within the OpenAI Agents SDK marks a significant milestone in AI development. By standardizing how context is provided to LLMs, MCP simplifies the process of integrating complex tools and data sources, thereby enriching the capabilities of AI agents. As AI continues to evolve, protocols like MCP will play a crucial role in advancing the field and unlocking new possibilities.</p>
<p>For more information, visit the <a href="https://openai.github.io/openai-agents-python/mcp/">OpenAI Agents SDK documentation</a>.</p>]]></content:encoded>
      <category>OpenAI</category>
      <category>Model Context Protocol</category>
      <category>Agents SDK</category>
      <category>AI Development</category>
    </item>
    <item>
      <title>Hosting Services in .NET: Examples, Best Practices, and Gotchas</title>
      <link>https://elijah.mondero.nz/post/hosting-services-in-net-examples-best-practices-and-gotchas/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/hosting-services-in-net-examples-best-practices-and-gotchas/</guid>
      <pubDate>Wed, 26 Mar 2025 09:18:03 +0000</pubDate>
      <description>Learn about hosting services in .NET, how to implement them, examples of real-world use cases, best practices, and common pitfalls. This guide provides actionable insights for developers.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/b08004c9-cc62-4967-a09c-16bdf752d19c.png" alt="Hosting Services in .NET: Examples, Best Practices, and Gotchas" /></p>
<h2>Introduction</h2>
<p>In the world of .NET development, hosting services play a fundamental role in creating robust and scalable web applications, background services, and worker services. Understanding how to effectively implement and manage these services is crucial for building modern applications that can handle continuous operation and complex tasks.</p>
<h2>What is a Hosted Service?</h2>
<p>A <strong>hosted service</strong> in .NET is a class that runs background tasks and implements the <code>IHostedService</code> interface. This interface defines two main methods:</p>
<ul>
<li><code>StartAsync(CancellationToken)</code>: Contains the logic to start the background task.</li>
<li><code>StopAsync(CancellationToken)</code>: Contains the logic to end the background task.</li>
</ul>
<p>The hosted service is managed by the .NET host, which handles the startup and shutdown of the service.</p>
<h2>Implementing a Hosted Service</h2>
<p>To implement a hosted service in .NET, you can use the Worker Service template provided by ASP.NET Core. Here’s a simple example:</p>
<pre>using Microsoft.Extensions.Hosting;
using System.Threading;
using System.Threading.Tasks;

public class MyBackgroundService : IHostedService, IDisposable
{
    private Timer _timer;

    public Task StartAsync(CancellationToken cancellationToken)
    {
        _timer = new Timer(DoWork, null, TimeSpan.Zero, TimeSpan.FromMinutes(1));
        return Task.CompletedTask;
    }

    private void DoWork(object state)
    {
        // Background task logic here
    }

    public Task StopAsync(CancellationToken cancellationToken)
    {
        _timer?.Change(Timeout.Infinite, 0);
        return Task.CompletedTask;
    }

    public void Dispose()
    {
        _timer?.Dispose();
    }
}
</pre>
<p>This example creates a hosted service with a background task that runs on a timer every minute.</p>
<h2>Best Practices for Hosted Services</h2>
<ol>
<li><strong>Proper Dependency Injection</strong>: Use DI to inject dependencies into your hosted services. This ensures the service is testable and easier to manage.</li>
</ol>
<pre>public class MyBackgroundService : BackgroundService
{
    private readonly IServiceProvider _serviceProvider;

    public MyBackgroundService(IServiceProvider serviceProvider)
    {
        _serviceProvider = serviceProvider;
    }
}
</pre>
<ol>
<li><strong>Graceful Shutdown</strong>: Implement <code>StopAsync</code> to handle graceful shutdowns and resource cleanup.</li>
</ol>
<ol>
<li><strong>Avoid Blocking Calls</strong>: Use asynchronous methods to prevent blocking the main thread and ensure efficient execution.</li>
</ol>
<pre>public async Task DoWorkAsync(CancellationToken cancellationToken)
{
    // Async background task logic here
}
</pre>
<ol>
<li><strong>Handle Errors and Exceptions</strong>: Ensure that your background tasks handle exceptions and have proper error logging to diagnose issues easily.</li>
</ol>
<h2>Common Pitfalls</h2>
<ol>
<li><strong>Not Managing Resources</strong>: Failing to properly dispose of timers, connections, or other resources could lead to memory leaks and application crashes.</li>
</ol>
<ol>
<li><strong>Long Running Tasks in <code>StartAsync</code></strong>: Avoid placing long-running tasks in <code>StartAsync</code> as it blocks other hosted services from starting.</li>
</ol>
<ol>
<li><strong>Not Setting Timeouts on Blocking Calls</strong>: Ensure that all blocking calls have a timeout to prevent indefinite waiting and potential deadlocks.</li>
</ol>
<h2>Advanced Concepts</h2>
<ul>
<li><strong>BackgroundService Base Class</strong>: Instead of implementing <code>IHostedService</code> directly, you can inherit from <code>BackgroundService</code>, which provides a more convenient way to run long-running tasks.</li>
</ul>
<pre>public class MyBackgroundService : BackgroundService
{
    protected override async Task ExecuteAsync(CancellationToken stoppingToken)
    {
        while (!stoppingToken.IsCancellationRequested)
        {
            await DoWorkAsync(stoppingToken);
            await Task.Delay(TimeSpan.FromMinutes(1), stoppingToken);
        }
    }
}
</pre>
<ul>
<li><strong>Queued Background Tasks</strong>: For tasks that need to run sequentially, you can use a queue-based approach to manage task execution.</li>
</ul>
<h2>Conclusion</h2>
<p>Hosting services in .NET provides a powerful mechanism to handle background tasks and long-running processes. By following best practices and avoiding common pitfalls, you can create efficient, reliable, and scalable applications. Whether you are building web applications, background services, or worker services, understanding the host infrastructure in .NET is essential for modern application development.</p>]]></content:encoded>
      <category>.NET</category>
      <category>ASP.NET Core</category>
      <category>Background Services</category>
      <category>Hosting</category>
      <category>Best Practices</category>
    </item>
    <item>
      <title>Tencent's Hunyuan T1: A New Milestone in AI Reasoning Models</title>
      <link>https://elijah.mondero.nz/post/tencents-hunyuan-t1-a-new-milestone-in-ai-reasoning-models/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/tencents-hunyuan-t1-a-new-milestone-in-ai-reasoning-models/</guid>
      <pubDate>Tue, 25 Mar 2025 08:58:11 +0000</pubDate>
      <description>Tencent's latest AI model, Hunyuan T1, showcases advancements in reasoning capabilities, positioning itself as a strong contender among top-tier AI models.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/4a4f25c1-21b1-4b84-b6e2-3a006033d4bb.png" alt="Tencent&#x27;s Hunyuan T1: A New Milestone in AI Reasoning Models" /></p>
<h1>Tencent&#x27;s Hunyuan T1: A New Milestone in AI Reasoning Models</h1>
<p>Tencent has made significant strides in the AI domain with the introduction of their new reasoning model, Hunyuan T1. This model is designed to compete with the best in the industry, including OpenAI&#x27;s top-performing systems.</p>
<h2>Performance and Capabilities</h2>
<p>The Hunyuan T1 model has shown impressive results across various benchmarks. It scored 87.2 points on the MMLU-PRO test, which evaluates knowledge across 14 different subject areas, placing it second only to OpenAI&#x27;s o1 model. It particularly excels in mathematical reasoning, achieving an impressive 96.2 points on the MATH-500 benchmark. Other notable performances include scores of 64.9 on LiveCodeBench and 91.9 on ArenaHard.</p>
<h2>Development and Training</h2>
<p>Tencent employed a robust approach during the development of Hunyuan T1. The model was primarily trained using reinforcement learning techniques, which accounted for 96.7 percent of the post-training computational effort. Additionally, Tencent used a curriculum learning approach, gradually increasing the difficulty of tasks to enhance the model&#x27;s capabilities. A self-reward system was also implemented, where earlier versions of the model evaluated the outputs of newer versions to drive continuous improvements.</p>
<h2>Technical Innovations</h2>
<p>The Hunyuan T1 model is built on the Transformer Mamba architecture, which significantly enhances its processing speed. Tencent claims that this architecture enables the model to process lengthy texts twice as fast as conventional models under similar conditions. This makes Hunyuan T1 particularly efficient and capable of generating answers more quickly.</p>
<h2>Availability and Competitiveness</h2>
<p>Hunyuan T1 is currently available through the Tencent Cloud, and a demo can be accessed on Hugging Face. This release follows similar moves by other tech giants like Baidu and Alibaba, who have also introduced high-performance reasoning models. The competition in the AI landscape is intensifying, with Chinese companies like Tencent, Baidu, and Alibaba pursuing aggressive development and open-source strategies.</p>
<h2>Conclusion</h2>
<p>Tencent&#x27;s Hunyuan T1 is a noteworthy advancement in AI reasoning models. Its strong performance across various benchmarks and innovative training methods position it as a significant player in the field. As the competition heats up among AI giants, models like Hunyuan T1 are pushing the boundaries of what AI can achieve in reasoning and problem-solving.</p>]]></content:encoded>
      <category>AI</category>
      <category>Tencent</category>
      <category>Hunyuan T1</category>
      <category>Artificial Intelligence</category>
      <category>Reasoning Model</category>
      <category>Transformer Mamba</category>
    </item>
    <item>
      <title>OpenAI Unveils New GPT-4o Transcribe Models: Revolutionizing Voice AI</title>
      <link>https://elijah.mondero.nz/post/openai-unveils-new-gpt-4o-transcribe-models-revolutionizing-voice-ai/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/openai-unveils-new-gpt-4o-transcribe-models-revolutionizing-voice-ai/</guid>
      <pubDate>Fri, 21 Mar 2025 07:19:32 +0000</pubDate>
      <description>OpenAI has announced a new suite of audio models, including GPT-4o-transcribe and GPT-4o-mini-transcribe, which promises to push the boundaries of speech recognition and transcribing technology.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/414bfe72-d525-4952-889d-6584b6c49708.png" alt="OpenAI Unveils New GPT-4o Transcribe Models: Revolutionizing Voice AI" /></p>
<p>OpenAI has once again raised the bar in the realm of artificial intelligence with the introduction of its next-generation audio models. The newly announced models, namely GPT-4o-transcribe and GPT-4o-mini-transcribe, are designed to cater to various applications, ranging from customer service voice agents to transcribing meeting notes.</p>
<h2>Overview of GPT-4o Transcribe Models</h2>
<p>The GPT-4o-transcribe models bring a new level of accuracy and efficiency in converting speech to text. Leveraging advancements in natural language processing, these models are aimed at transforming the way voice interactions are managed in technology applications.</p>
<h3>Key Features</h3>
<ul>
<li><strong>Improved Speech-to-Text Accuracy:</strong> The GPT-4o-transcribe models boast a high level of precision in transcribing spoken language into text, reducing errors and improving understanding in various contexts.</li>
<li><strong>Versatility in Use Cases:</strong> From aiding customer service agents to providing detailed meeting notes, the applications of these new models are vast and varied.</li>
<li><strong>Integration Capabilities:</strong> OpenAI has updated its Agents SDK to support the new models, making it easier for developers to integrate voice capabilities into their existing text-based applications with minimal code changes.</li>
</ul>
<h3>The Mini Models</h3>
<p>Alongside the standard GPT-4o-transcribe model, OpenAI has introduced the GPT-4o-mini-transcribe, which offers a more compact and efficient solution for applications requiring lighter processing power, without compromising on the quality of transcription.</p>
<h2>Potential Impact on Industries</h2>
<p>The introduction of these state-of-the-art transcription models is expected to drive significant advancements in multiple industries. For instance:</p>
<ul>
<li><strong>Customer Service:</strong> Automated voice agents equipped with these models can handle queries more efficiently, leading to faster and more accurate customer support.</li>
<li><strong>Healthcare:</strong> Transcribing medical consultations and patient interactions accurately can enhance record-keeping and patient care.</li>
<li><strong>Corporate Sector:</strong> From transcribing meetings to drafting documents based on voice inputs, businesses can streamline operations and improve productivity.</li>
</ul>
<p>OpenAI’s latest announcement is a testament to the continued evolution of AI technology, pushing forward the capabilities of voice and speech recognition. These new audio models, with their robust set of features, are set to make significant strides in enhancing how voice data is handled and utilized.</p>
<p>Stay tuned for more updates and developments as OpenAI continues to innovate in the world of artificial intelligence.</p>]]></content:encoded>
      <category>AI</category>
      <category>OpenAI</category>
      <category>GPT-4o</category>
      <category>Transcribe</category>
      <category>Voice AI</category>
      <category>Speech Recognition</category>
    </item>
    <item>
      <title>.NET AI Template Now Available in Preview</title>
      <link>https://elijah.mondero.nz/post/net-ai-template-now-available-in-preview/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/net-ai-template-now-available-in-preview/</guid>
      <pubDate>Tue, 18 Mar 2025 06:34:24 +0000</pubDate>
      <description>Microsoft has announced a new AI Chat Web App template, now available in preview. This template is designed to simplify AI development with .NET by providing scaffolding and guidance within Visual Studio, Visual Studio Code, and the .NET CLI.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/868ab36a-699e-4174-815b-bcd7bd710e8c.png" alt=".NET AI Template Now Available in Preview" /></p>
<h2>Introduction</h2>
<p>Microsoft has released the first preview of the .NET AI Template, designed to make AI development with .NET more accessible. This new template aims to streamline the creation of AI applications by providing scaffolding and guidance within Visual Studio, Visual Studio Code, and the .NET CLI. This marks a significant step forward in simplifying AI integration for developers working within the .NET ecosystem.</p>
<h2>Key Features</h2>
<p>The .NET AI Chat template offers several features and configuration options that enhance the AI development experience:</p>
<h3>Chat with Custom Data</h3>
<p>The template allows developers to create a chat-based UI that can interact with sample PDFs or user-provided data using the Retrieval Augmented Generation (RAG) pattern.</p>
<h3>Local and Azure Integration</h3>
<p>It supports both a local vector store for prototyping and Azure AI Search for more advanced configurations.</p>
<h3>Customizable Code</h3>
<p>The generated code includes UI components for chat interactions, citation tracking, and follow-up suggestions, which developers can customize or remove as needed.</p>
<h3>Data Ingestion</h3>
<p>The template includes code for data ingestion, caching, and processing, allowing developers to handle various data sources and formats.</p>
<h2>Getting Started</h2>
<h3>Installation</h3>
<p>To install the first preview of the template, run the following terminal command:</p>
<pre> dotnet new install Microsoft.Extensions.AI.Templates
</pre>
<p>Once installed, the template can be accessed in Visual Studio, Visual Studio Code (with the C# Dev Kit), or via the command line using:</p>
<pre> dotnet new aichatweb
</pre>
<h3>Using Visual Studio</h3>
<p>After installing the template, developers can start a new project by navigating to <code>File &gt; New Project…</code> and searching for AI Chat or selecting the AI project type to find the template. Upon selecting a project name and location, they can choose an AI model provider and vector store.</p>
<h3>Using Visual Studio Code</h3>
<p>In Visual Studio Code, the template can be accessed by first installing the C# Dev Kit extension, and then using the <code> .NET: New Project… </code> command. By default, it creates a new project using the GitHub Models model provider and a local vector store.</p>
<h2>Customizing Your Chat Data</h2>
<p>This template includes sample PDF files and data ingestion code to process them. To chat with your own data:</p>
<ol>
<li>Stop the running project.</li>
<li>Remove the sample PDF files from the <code>/wwwroot/Data</code> folder.</li>
<li>Add your PDF files to the <code>/wwwroot/Data</code> folder.</li>
<li>Restart the application.</li>
</ol>
<p>On startup, the data ingestion code will process the new files.</p>
<h2>Conclusion</h2>
<p>The preview of the .NET AI Template represents a significant step in making AI development more accessible and streamlined within the .NET ecosystem. Developers are encouraged to provide feedback to help shape future versions of the template, ensuring it evolves to meet their needs.</p>
<p>For more information and documentation, visit the <a href="https://devblogs.microsoft.com/dotnet/announcing-dotnet-ai-template-preview1/">official blog post</a>.</p>]]></content:encoded>
      <category>.NET</category>
      <category>AI</category>
      <category>Template</category>
      <category>Preview</category>
      <category>Visual Studio</category>
      <category>Visual Studio Code</category>
    </item>
    <item>
      <title>Deep Dive into LLMs like ChatGPT – A Detailed Summary</title>
      <link>https://elijah.mondero.nz/post/deep-dive-into-llms-like-chatgpt-a-detailed-summary/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/deep-dive-into-llms-like-chatgpt-a-detailed-summary/</guid>
      <pubDate>Mon, 17 Mar 2025 09:59:31 +0000</pubDate>
      <description>Explore the fascinating world of Large Language Models (LLMs) like ChatGPT. Understand their architecture, training processes, and capabilities through this comprehensive deep dive summary.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/e154ded2-8ee6-4f56-8f15-fc75f4a88963.png" alt="Deep Dive into LLMs like ChatGPT – A Detailed Summary" /></p>
<h2>Introduction</h2>
<p>In this blog post, we&#x27;ll delve into the intricate workings of Large Language Models (LLMs) such as ChatGPT, highlighting their architectural components, training methodologies, usage, and future implications. Inspired by insights from Andrej Karpathy&#x27;s comprehensive video deep dive, this summary aims to provide a clear and detailed understanding of LLMs without requiring extensive technical knowledge.</p>
<h2>Pretraining Data</h2>
<p>LLMs start by collecting extensive text data from the internet, forming a massive dataset. This raw data undergoes heavy filtering to remove duplicates, low-quality text, and irrelevant content. For instance, a dataset like FineWeb contains over 1.2 billion web pages. The filtered data is then tokenized, converting raw text into structured, numerical tokens for the neural network to process.</p>
<h2>Tokenization</h2>
<p>Tokenization breaks down text into smaller pieces called tokens before processing. Techniques like Byte Pair Encoding (BPE) are commonly used. For example, GPT-4 uses 100,277 tokens. This tokenized data is then fed into the neural network.</p>
<h2>Neural Network I/O</h2>
<p>The model processes data within a context window, predicting the next token based on learned patterns. Using backpropagation, the model&#x27;s weights are adjusted to minimize errors, thus improving prediction accuracy.</p>
<h2>Neural Network Internals</h2>
<p>Inside the model, billions of parameters interact with the input tokens, creating a probability distribution for the next token. This process involves complex mathematical equations optimized for efficiency, balancing speed, accuracy, and parallelization.</p>
<h2>Inference</h2>
<p>During inference, LLMs generate non-deterministic, stochastic outputs, making responses slightly vary each time. Despite not repeating trained data, LLMs follow learned patterns to generate new outputs. This stochastic nature enables creativity but also potential inaccuracies or &#x27;hallucinations.&#x27;</p>
<h2>The Evolution of LLMs: Case Study of GPT-2</h2>
<p>GPT-2, an early transformer-based LLM developed by OpenAI in 2019, had 1.6 billion parameters and a 1024-token context length, trained on about 100 billion tokens. Early training cost about $40,000, but recent advancements reduced costs significantly. Andrej Karpathy demonstrated this by reproducing GPT-2 using optimized pipelines at just $672.</p>
<h2>Reinforcement Learning from Human Feedback (RLHF)</h2>
<p>Reinforcement learning techniques, including RLHF, enable LLMs to learn from ideal human responses. This training approach has shown significant improvements in domains like mathematics and code generation, where LLMs are guided through human feedback and reward models to enhance output relevance.</p>
<h2>Practical Applications and Considerations</h2>
<p>LLMs excel in brainstorming, generating ideas, and coding but should not be blindly trusted for mission-critical applications due to potential inaccuracies. They are best used as tools to augment productivity, always with human oversight to verify outputs.</p>
<h2>Future Directions</h2>
<p>The development of LLMs continues to evolve, focusing on enhancing training data quality, optimizing tokenization techniques, and improving inference reliability. The use of reinforcement learning and human feedback loops is pivotal in refining model outputs.</p>
<h2>Conclusion</h2>
<p>Understanding LLMs like ChatGPT allows us to harness their capabilities effectively while remaining cautious of their limitations. Continual advancements and ethical considerations will shape the future landscape of AI and its applications, making it an exciting field to watch and contribute to.</p>]]></content:encoded>
      <category>AI</category>
      <category>LLM</category>
      <category>ChatGPT</category>
      <category>Deep Learning</category>
      <category>Reinforcement Learning</category>
    </item>
    <item>
      <title>Exploring Minimal APIs vs. Controllers in ASP.NET Core</title>
      <link>https://elijah.mondero.nz/post/exploring-minimal-apis-vs-controllers-in-aspnet-core/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/exploring-minimal-apis-vs-controllers-in-aspnet-core/</guid>
      <pubDate>Thu, 13 Mar 2025 08:13:42 +0000</pubDate>
      <description>Explore the differences between Minimal APIs and Controllers in ASP.NET Core, understanding their implementations, performance aspects, and when to use each approach.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/bdc63828-6253-4e60-9ba2-249af94067b7.png" alt="Exploring Minimal APIs vs. Controllers in ASP.NET Core" /></p>
<p>When developing APIs in ASP.NET Core, you can choose between two primary approaches: <strong>Controllers</strong> and <strong>Minimal APIs</strong>. Each approach has unique characteristics, benefits, and use cases. In this post, we&#x27;ll dive into the differences between these two approaches, their performance, and scenarios where each shines.</p>
<h3>Controllers</h3>
<p>Controllers in ASP.NET Core are classes that derive from <code>ControllerBase</code>. They follow a conventional MVC pattern where each controller is responsible for handling HTTP requests, and actions within these controllers map to the application&#x27;s endpoints.</p>
<p>Here&#x27;s an example of a basic controller-based API:</p>
<pre>namespace APIWithControllers
{
    public class Program
    {
        public static void Main(string[] args)
        {
            var builder = WebApplication.CreateBuilder(args);

            builder.Services.AddControllers();
            var app = builder.Build();

            app.UseHttpsRedirection();
            app.MapControllers();
            app.Run();
        }
    }

    using Microsoft.AspNetCore.Mvc;

    namespace APIWithControllers.Controllers
    {
        [ApiController]
        [Route(&quot;[controller]&quot;)]
        public class WeatherForecastController : ControllerBase
        {
            private static readonly string[] Summaries = new[]
            {
                &quot;Freezing&quot;, &quot;Bracing&quot;, &quot;Chilly&quot;, &quot;Cool&quot;, &quot;Mild&quot;, &quot;Warm&quot;, &quot;Balmy&quot;, &quot;Hot&quot;, &quot;Sweltering&quot;, &quot;Scorching&quot;
            };

            private readonly ILogger&lt;WeatherForecastController&gt; _logger;

            public WeatherForecastController(ILogger&lt;WeatherForecastController&gt; logger)
            {
                _logger = logger;
            }

            [HttpGet(Name = &quot;GetWeatherForecast&quot;)]
            public IEnumerable&lt;WeatherForecast&gt; Get()
            {
                return Enumerable.Range(1, 5).Select(index =&gt; new WeatherForecast
                {
                    Date = DateOnly.FromDateTime(DateTime.Now.AddDays(index)),
                    TemperatureC = Random.Shared.Next(-20, 55),
                    Summary = Summaries[Random.Shared.Next(Summaries.Length)]
                })
                .ToArray();
            }
        }
    }
}
</pre>
<h3>Minimal APIs</h3>
<p>Minimal APIs, introduced in .NET 6, offer a more straightforward way to build APIs using lightweight Lambda expressions. They allow you to define endpoints with logical handlers in-line, within the <code>Main</code> method.</p>
<p>Here&#x27;s an example using Minimal APIs:</p>
<pre>namespace MinimalAPI
{
    public class Program
    {
        public static void Main(string[] args)
        {
            var builder = WebApplication.CreateBuilder(args);
            var app = builder.Build();

            app.UseHttpsRedirection();

            var summaries = new[]
            {
                &quot;Freezing&quot;, &quot;Bracing&quot;, &quot;Chilly&quot;, &quot;Cool&quot;, &quot;Mild&quot;, &quot;Warm&quot;, &quot;Balmy&quot;, &quot;Hot&quot;, &quot;Sweltering&quot;, &quot;Scorching&quot;
            };

            app.MapGet(&quot;/weatherforecast&quot;, (HttpContext httpContext) =&gt;
            {
                var forecast = Enumerable.Range(1, 5).Select(index =&gt;
                    new WeatherForecast
                    {
                        Date = DateOnly.FromDateTime(DateTime.Now.AddDays(index)),
                        TemperatureC = Random.Shared.Next(-20, 55),
                        Summary = summaries[Random.Shared.Next(summaries.Length)]
                    })
                    .ToArray();
                return forecast;
            });

            app.Run();
        }
    }
}
</pre>
<h3>Performance Comparison</h3>
<p>A detailed performance comparison by Steven Giesel highlighted several benchmark tests between Minimal APIs and Controllers. The study included tests for simple GET requests, requests with injected services, POST requests, middleware handling, and parallel requests.</p>
<p>Results indicated that Minimal APIs generally had a performance edge over Controller-based APIs in certain scenarios. However, the performance differences might be negligible depending on the context and specifics of the project requirements.</p>
<h3>When to Use Each Approach</h3>
<p><strong>Controllers</strong>:\n- Follow a conventional and familiar MVC pattern.\n- Better for applications with complex routing, sophisticated workflows, and larger codebases.\n- Easier to maintain separation of concerns within larger teams.\n\n<strong>Minimal APIs</strong>:\n- Ideal for microservices and simpler, lightweight applications.\n- Faster setup and usually results in less boilerplate code.\n- Beneficial when rapid development and deployment are prioritized.\n\nUnderstanding the nuances between Minimal APIs and Controllers enables developers to choose the right approach based on the application&#x27;s needs and team&#x27;s expertise.\n\n### Conclusion\n\nBoth Minimal APIs and Controllers have their strengths and should be chosen based on the specific needs of your project. Controllers offer a well-structured approach for complex applications, while Minimal APIs provide a more streamlined and faster approach perfect for lightweight applications. \n\nChoose wisely, and always keep your application&#x27;s requirements at the forefront of your decision-making process.</p>]]></content:encoded>
      <category>ASP.NET Core</category>
      <category>Minimal API</category>
      <category>Controllers</category>
      <category>Performance</category>
      <category>API Development</category>
    </item>
    <item>
      <title>Understanding the Difference Between Agentic AI and AI Agents</title>
      <link>https://elijah.mondero.nz/post/understanding-the-difference-between-agentic-ai-and-ai-agents/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/understanding-the-difference-between-agentic-ai-and-ai-agents/</guid>
      <pubDate>Sat, 08 Mar 2025 08:57:00 +0000</pubDate>
      <description>AI agents and agentic AI are reshaping technology and business. This blog post explores the distinctions between these two frequently confused terms and their implications for the future.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/66a0b2fe-ba5d-49e1-97a7-5ef74080cab2.png" alt="Understanding the Difference Between Agentic AI and AI Agents" /></p>
<p>AI agents and agentic AI are reshaping technology and business, but these frequently confused terms represent dramatically different technological capabilities and future potentials.</p>
<p>If you’ve been reading about business technology recently, then “AI agents” and “agentic AI” are terms you’ve probably come across with increasing frequency. They’re often used interchangeably, and this can cause a little confusion as they refer to subtly different concepts.</p>
<p>So, what are they and how are they different?</p>
<p>Both concepts relate to AI systems that can work through multi-step problems independently, with little guidance from humans. However, there are key distinctions between them.</p>
<h3>AI Agents</h3>
<p>AI agents are specific applications created to independently handle specific tasks. They are already widely in use today, even if we don’t often notice them. For example, banks use AI agents to verify identities, automate transactions, manage record-keeping, and learn customer preferences to improve services.</p>
<h3>Agentic AI</h3>
<p>Agentic AI, on the other hand, refers to the overall field of AI that enables machines to operate as agents. It&#x27;s focused on researching and developing AI models capable of the kind of independent, autonomous work that agents perform. It&#x27;s like regarding AI agents as specific medicines for particular conditions, while agentic AI encompasses the entire field of pharmaceutical science developing those medications.</p>
<p>Another way to understand the difference is through the concept of artificial general intelligence (AGI) – the ultimate aim to create AIs that are generalists rather than specialists. Current AI agents handle complex tasks but are limited to specific domains they were designed for. They can&#x27;t apply their learning to other tasks in the same way humans can. Agentic AI research and development aim to eventually achieve AGI, creating systems that can interact with external environments both digitally and physically through robotics.</p>
<h3>Why Is Understanding This Important?</h3>
<p>AI agents and agentic AI are closely related and will have significant impacts on the future of technology. As agentic AI develops, we will see increasingly sophisticated agents automating a wide array of tasks. This includes advanced digital assistants that learn detailed user preferences and take proactive steps to assist, and integrated robotic systems performing complex physical tasks.</p>
<p>The massive advancements expected in AI suggest these changes could occur rapidly, possibly catching many off guard. Staying informed about the latest developments in AI, robotics, and automation is essential for anyone aiming to thrive in the coming technological era.</p>]]></content:encoded>
      <category>AI</category>
      <category>Technology</category>
      <category>Business</category>
      <category>Innovation</category>
      <category>Agentic AI</category>
      <category>AI Agents</category>
    </item>
    <item>
      <title>Leaked System Prompt of ChatGPT 4.5</title>
      <link>https://elijah.mondero.nz/post/leaked-system-prompt-chatgpt-45/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/leaked-system-prompt-chatgpt-45/</guid>
      <pubDate>Fri, 07 Mar 2025 22:42:59 +0000</pubDate>
      <description>Discover the leaked system prompt of ChatGPT 4.5 that reveals its instruction set, tool usage guidelines, and ethical constraints.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/284d09f1-ae64-465d-b22d-8047c5e0cf7d.png" alt="Leaked System Prompt of ChatGPT 4.5" /></p>
<p>Recently, a member of the Reddit community <code>r/PromptEngineering</code> claimed to have coaxed ChatGPT 4.5 into revealing its system prompt. Below is the verbatim content of the prompt, detailing the AI&#x27;s instruction set and operational guidelines.</p>
<h3>System Prompt of ChatGPT 4.5</h3>
<pre>You are ChatGPT, a large language model trained by OpenAI. Knowledge cutoff: 2023-10 Current date: 2025-03-07

Personality: v2

You are a highly capable, thoughtful, and precise assistant. Your goal is to deeply understand the user&#x27;s intent, ask clarifying questions when needed, think step-by-step through complex problems, provide clear and accurate answers, and proactively anticipate helpful follow-up information. Always prioritize being truthful, nuanced, insightful, and efficient, tailoring your responses specifically to the user&#x27;s needs and preferences.

NEVER use the dalle tool unless the user specifically requests for an image to be generated.

# Tools

## bio
The bio tool is disabled. Do not send any messages to it.If the user explicitly asks you to remember something, politely ask them to go to Settings &gt; Personalization &gt; Memory to enable memory.

## canmore
# The canmore tool creates and updates textdocs that are shown in a canvas next to the conversation
This tool has 3 functions, listed below.

## Creates a new textdoc to display in the canvas.
NEVER use this function. The ONLY acceptable use case is when the user EXPLICITLY asks for canvas. Other than that, NEVER use this function.
Expects a JSON string that adheres to this schema:
{
  name: string,
  type: document | code/python | code/javascript | code/html | code/java | ...,
  content: string,
}
For code languages besides those explicitly listed above, use code/languagename, e.g. code/cpp.
Types code/react and code/html can be previewed in ChatGPT&#x27;s UI. Default to code/react if the user asks for code meant to be previewed (eg. app, game, website).

When writing React:
- Default export a React component.
- Use Tailwind for styling, no import needed.
- All NPM libraries are available to use.
- Use shadcn/ui for basic components (eg. &lt;Button&gt; or &lt;Modal&gt;), lucide-react for icons, and recharts for charts.
- Code should be production-ready with a minimal, clean aesthetic.
- Follow these style guides:
  - Varied font sizes (eg., xl for headlines, base for text).
  - Framer Motion for animations.
  - Grid-based layouts to avoid clutter.
  - 2xl rounded corners, soft shadows for cards/buttons.
  - Adequate padding (at least p-2).
  - Consider adding a filter/sort control, search input, or dropdown menu for organization.

## Updates the current textdoc.
Never use this function unless a textdoc has already been created.
Expects a JSON string that adheres to this schema:
{
  updates: {
    pattern: string,
    multiple: boolean,
    replacement: string,
  }[],
}

## Comments on the current textdoc.
Never use this function unless a textdoc has already been created. Each comment must be a specific and actionable suggestion on how to improve the textdoc. For higher level feedback, reply in the chat.
Expects a JSON string that adheres to this schema:
{\n  comments: {\n    pattern: string,\n    comment: string,\n  }[],\n}

## dalle
// Whenever a description of an image is given, create a prompt that dalle can use to generate the image and abide to the following policy: //
1. The prompt must be in English. Translate to English if needed.
2. DO NOT ask for permission to generate the image, just do it!
3. DO NOT list or refer to the descriptions before OR after generating the images.
4. Do not create more than 1 image, even if the user requests more.
5. Do not create images in the style of artists, creative professionals or studios whose latest work was created after 1912 (e.g. Picasso, Kahlo).
- You can name artists, creative professionals or studios in prompts only if their latest work was created prior to 1912 (e.g. Van Gogh, Goya)
- If asked to generate an image that would violate this policy, instead apply the following procedure: (a) substitute the artist&#x27;s name with three adjectives that capture key aspects of the style; (b) include an associated artistic movement or era to provide context; and (c) mention the primary medium used by the artist
6. For requests to include specific, named private individuals, ask the user to describe what they look like, since you don&#x27;t know what they look like.
7. For requests to create images of any public figure referred to by name, create images of those who might resemble them in gender and physique. But they shouldn&#x27;t look like them. If the reference to the person will only appear as TEXT out in the image, then use the reference as is and do not modify it.
8. Do not name or directly / indirectly mention or describe copyrighted characters. Rewrite prompts to describe in detail a specific different character with a different specific color, hair style, or other defining visual characteristic. Do not discuss copyright policies in responses.
The generated prompt sent to dalle should be very detailed, and around 100 words long.

## python
When you send a message containing Python code to python, it will be executed in a stateful Jupyter notebook environment. python will respond with the output of the execution or time out after 60.0 seconds. The drive at &#x27;/mnt/data&#x27; can be used to save and persist user files. Internet access for this session is disabled. Do not make external web requests or API calls as they will fail. Use ace_tools.display_dataframe_to_user(name: str, dataframe: pandas.DataFrame) -&gt; None to visually present pandas DataFrames when it benefits the user.

When making charts for the user:
1) never use seaborn, 2) give each chart its own distinct plot (no subplots), and 3) never set any specific colors – unless explicitly asked to by the user.
I REPEAT: when making charts for the user:
1) use matplotlib over seaborn, 2) give each chart its own distinct plot (no subplots), and 3) never, ever, specify colors or matplotlib styles – unless explicitly asked to by the user

## web
Use the web tool to access up-to-date information from the web or when responding to the user requires information about their location. Some examples of when to use the web tool include:
- Local Information: weather, local businesses, events.
- Freshness: if up-to-date information on a topic could change or enhance the answer.
- Niche Information: detailed info not widely known or understood (found on the internet).
- Accuracy: if the cost of outdated information is high, use web sources directly.
IMPORTANT: Do not attempt to use the old web tool or generate responses from it anymore, as it is now deprecated or disabled.
The  web tool has the following commands:
- search: Issues a new query to a search engine and outputs the response.
- scrape: Opens the given URL and displays it.
</pre>
<h3>Analysis</h3>
<p>This system prompt reveals the rigorous protocols that ChatGPT 4.5 follows to ensure accuracy, user safety, and compliance with ethical standards. It includes detailed guidelines for various tools like bio, canmore, dalle, python, and web. It explicitly mandates when and how these tools should be used, along with strict limitations to maintain users&#x27; trust and data integrity.</p>]]></content:encoded>
      <category>ChatGPT 4.5</category>
      <category>system prompt</category>
      <category>AI tools</category>
      <category>ethics</category>
    </item>
    <item>
      <title>The Importance of FinOps in Managing Cloud and On-Premise Costs</title>
      <link>https://elijah.mondero.nz/post/importance-of-finops/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/importance-of-finops/</guid>
      <pubDate>Thu, 06 Mar 2025 09:28:30 +0000</pubDate>
      <description>Discover the significance of FinOps in optimizing cloud and on-premise infrastructure to minimize financial wastage and enhance operational efficiency.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/d0aba14c-4b88-4e5d-8a5d-2b5c94925f84.png" alt="The Importance of FinOps in Managing Cloud and On-Premise Costs" /></p>
<p>In recent times, financial operations (FinOps) have gained significant traction as organizations increasingly adopt cloud infrastructure. The rapid expansion and adoption, while beneficial, have also led to substantial inefficiencies and costs which could otherwise be optimized. An estimated $44.5 billion in infrastructure cloud waste is projected by 2025 due to the disconnect between FinOps and developers, according to a report by Harness.</p>
<h2>Understanding FinOps</h2>
<p>FinOps is a practice that combines finance and operations to ensure organizations get maximum value from their cloud and on-premise computing resources. The primary motive behind FinOps is to bridge the gap between finance, operations, and development teams, fostering a culture of accountability and continuous improvement in financial management.</p>
<h2>The Role of FinOps in Cost Management</h2>
<p>As organizations increasingly rely on cloud and hybrid infrastructures, managing expenses has become more complex. FinOps helps in this regard by focusing on the following core principles:</p>
<h3>1. <strong>Visibility</strong></h3>
<p>One of the key roles of FinOps is to provide comprehensive visibility into spending patterns. By utilizing detailed reports and dashboards, organizations can gain insights into where and how their resources are being used.</p>
<h3>2. <strong>Optimization</strong></h3>
<p>Beyond mere cost-tracking, FinOps focuses on optimizing resources. This includes identifying and eliminating unnecessary expenditures, leveraging discount options, and right-sizing resources to match demand.</p>
<h3>3. <strong>Accountability</strong></h3>
<p>FinOps emphasizes accountability by involving all relevant teams in the cost management process. By doing so, it ensures that financial considerations are integral to operational and development decisions, fostering a culture of ownership and responsibility.</p>
<h3>4. <strong>Collaboration</strong></h3>
<p>Effective FinOps requires collaboration across multiple departments. Establishing clear communication and workflows between finance, operations, and IT teams is essential to harness the full potential of FinOps practices.</p>
<h2>The Impact on On-Premise Costs</h2>
<p>While FinOps is often associated with cloud infrastructure, its principles are equally applicable to on-premise data centers. Organizations with on-premise setups can benefit from improved cost transparency, better resource allocation, and strategic procurement practices driven by FinOps.</p>
<h2>Future of FinOps</h2>
<p>As businesses continue to digitize and scale their operations, the importance of a robust FinOps strategy cannot be overstated. It ensures not only the economic viability of cloud and on-premises infrastructure but also supports innovation by freeing up resources that can be reinvested in strategic initiatives.</p>
<p>In conclusion, FinOps plays a crucial role in enabling businesses to navigate the complexities of modern IT environments. By integrating financial governance with operational practice, organizations can achieve sustainable growth and operational efficiency.</p>]]></content:encoded>
      <category>FinOps</category>
      <category>Cloud Cost Management</category>
      <category>On-Premise Optimization</category>
      <category>Financial Operations</category>
    </item>
    <item>
      <title>Understanding Code Time: The Key to Developer Productivity</title>
      <link>https://elijah.mondero.nz/post/code-time-report/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/code-time-report/</guid>
      <pubDate>Tue, 04 Mar 2025 08:55:22 +0000</pubDate>
      <description>In the fast-paced world of software development, maintaining uninterrupted code time is paramount for productivity and innovation. The Global Code Time Report by Software.com provides an in-depth analysis of how developers manage to find focus in their workday despite various challenges. This blog post delves into the findings and implications of the report.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/9b02355b-9221-4fd6-a639-11f4f4d56366.png" alt="Understanding Code Time: The Key to Developer Productivity" /></p>
<p>Over the last decade, we’ve witnessed a growing divide in the world of software development. Technology giants deploy code daily across complex systems managed by tens of thousands of developers. They coordinate hundreds of projects and teams, spread around the world and across time zones. They enable fast deployments, fast reviews, and fast data. As a result, they consistently deliver value to their customers, set their industry’s pace for innovation, and ultimately win in the marketplace.</p>
<p>At the same time, many companies are falling behind. Engineering teams struggle with roadblocks and bottlenecks during the development process. Taking an idea to production can take months or even quarters. Developers battle distractions — too many meetings, too many interruptions, and too much wait time on processes and systems — all of which impact the first prerequisite for high-performing engineering teams: <strong>code time</strong>.</p>
<h3>What is Code Time?</h3>
<p>Without time to focus and enter a state of flow, developers are limited in their ability to get work done. The best engineering organizations prioritize and defend code time by limiting meetings, reducing distractions, and removing constraints with the right tools and automations. This report explores data from our global community and uncovers how much time developers have available to code during the workday.</p>
<h3>Key Findings</h3>
<h4>Developers code less than one hour per day</h4>
<p>Based on data from 250K+ developers in our global community, developers code 52 minutes per day — about 4 hours and 21 minutes during a normal workweek from Monday to Friday.</p>
<p>Code time is defined as time spent actively writing or editing code in an editor or IDE, which we use as an indicator of the amount of focused, uninterrupted time that developers have available to code during the workday. Based on our estimates, developers spend an additional 41 minutes per day on other types of work in their editors, such as reading code, reviewing pull requests, and browsing documentation.</p>
<p><strong>Our takeaway:</strong> Our findings suggest that developers frequently face constraints at work that prevent them from finding uninterrupted time to code.</p>
<h4>Emerging economies code more than median</h4>
<p>Among the world’s largest advanced economies, known collectively as the G7, developers in Italy, France, and Japan spend the most time per day actively coding. In an analysis of ten countries categorized as emerging markets by the International Monetary Fund (IMF), we found that developers in Thailand, Turkey, and Brazil spend the most time coding.</p>
<p>Interestingly, developers in the top emerging markets code more than the global median, which may indicate that software engineering is rapidly increasing in popularity in those countries.</p>
<h4>Coding peaks on Wednesdays</h4>
<p>Coding peaks on Wednesday, when developers code a median of 55 minutes, and falls to 46 minutes on Friday, the least popular workday for coding. Most developers continue coding through the weekend; developers code a median of about 18 minutes per day on Saturday and Sunday.</p>
<p>To filter out part-time developers, our analysis is limited to developers who coded at least 7 of the last 30 days.</p>
<h3>Conclusion</h3>
<p>The findings from Software.com&#x27;s Code Time Report underline the significant challenges that developers face in finding uninterrupted time to code. By recognizing these hurdles and prioritizing code time, organizations can boost productivity and drive innovation. Whether through reducing meetings, minimizing distractions, or implementing the right tools and automations, defending code time is essential for high-performing engineering teams.</p>
<p>For a deeper dive into the data and insights, be sure to <a href="https://www.software.com/reports/code-time-report">download the full report</a>.</p>]]></content:encoded>
      <category>software development</category>
      <category>productivity</category>
      <category>engineering</category>
      <category>report</category>
    </item>
    <item>
      <title>Microsoft’s .NET 10 Arrives in First Preview</title>
      <link>https://elijah.mondero.nz/post/dotnet-10-preview/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/dotnet-10-preview/</guid>
      <pubDate>Sat, 01 Mar 2025 17:04:43 +0000</pubDate>
      <description>.NET 10 introduces C# 14 and adds major enhancements to the .NET runtime, SDK, libraries, ASP.NET Core, Blazor, and .NET MAUI, aiming for a production release in November.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/a831ecc4-0cc1-4877-8563-5c0275675be6.png" alt="Microsoft’s .NET 10 Arrives in First Preview" /></p>
<p>Microsoft has rolled out the first preview of .NET 10, a major new version of the company’s flagship software development platform. Likely to arrive as a production release in November, .NET 10 introduces C# 14 and adds major enhancements to the .NET runtime, SDK, libraries, ASP.NET Core, Blazor, and .NET MAUI.</p>
<h2>Key Features of .NET 10 Preview 1</h2>
<ul>
<li><strong>C# 14:</strong> First-class support for <code>System.Span&lt;T&gt;</code> and <code>System.ReadOnlySpan&lt;T&gt;</code>, new implicit conversions, and parameter modifiers for lambda expression parameters.</li>
<li><strong>.NET 10 Runtime:</strong> Reducing abstraction overhead, expanding JIT compiler’s ability to de-virtualize method calls, and stack-allocating small arrays.</li>
<li><strong>.NET 10 Libraries:</strong> Introducing APIs that work with spans of characters, improved performance for <code>ZipArchive</code>, and new APIs for transformation matrices.</li>
<li><strong>F#:</strong> Better handling of generic unmanaged structs and a type conversions cache.</li>
<li><strong>.NET 10 SDK:</strong> NuGet Audit feature for pruning unused package references.</li>
<li><strong>Visual Basic:</strong> Adds unmanaged constraint support and respects <code>OverloadResolutionPriorityAttribute</code>.</li>
<li><strong>ASP.NET Core:</strong> Support for generating OpenAPI 3.1 documents, now with YAML format support.</li>
<li><strong>Blazor:</strong> RouteAttribute supports route syntax highlighting.</li>
<li><strong>Entity Framework:</strong> Adds first-class LINQ support for the <code>LeftJoin</code> method.</li>
<li><strong>.NET MAUI:</strong> Ships as a .NET workload and multiple NuGet packages.</li>
</ul>
<h2>Availability</h2>
<p>.NET 10 Preview 1 can be downloaded from the <a href="https://dotnet.microsoft.com/">official site</a>.</p>
<p>Microsoft’s .NET 10 follows last November’s release of .NET 9, continuing improvements across the development platform.</p>]]></content:encoded>
      <category>C#</category>
      <category>Development Libraries</category>
      <category>Frameworks</category>
      <category>Microsoft .NET</category>
    </item>
    <item>
      <title>The $19.6 Billion Pivot: OpenAI's Struggle with GPT-5 and Their New Direction</title>
      <link>https://elijah.mondero.nz/post/open-ais-struggle-with-gpt-5/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/open-ais-struggle-with-gpt-5/</guid>
      <pubDate>Thu, 27 Feb 2025 20:14:36 +0000</pubDate>
      <description>Over the past two years, OpenAI has faced a challenging journey attempting to launch GPT-5. Despite significant investment and effort, the progress was slow and the core AI strategy of OpenAI needed a crucial shift. This post explores the reasons behind this struggle and the company's pivot to a new approach.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/ae75e7bf-6ec0-47c0-a35a-8e75cfc87234.png" alt="The $19.6 Billion Pivot: OpenAI&#x27;s Struggle with GPT-5 and Their New Direction" /></p>
<p>In recent news, it has been revealed that OpenAI, a leading force in the field of artificial intelligence, faced a major roadblock over the past two years in their efforts to launch GPT-5. Despite a hefty investment of $19.6 billion, the organization struggled to realize their ambitious goals, leading to a pivotal shift in their core AI strategy.</p>
<h2>The Struggle with GPT-5</h2>
<p>OpenAI has long been lauded for its advancements in AI through models such as GPT-2, GPT-3, and GPT-4. These models demonstrated unprecedented capabilities in language understanding and generation, setting new benchmarks in AI research. However, when the company embarked on the development of GPT-5, they encountered unforeseen challenges.</p>
<p><strong>Slow Progress and High Expectations</strong></p>
<p>The expectation was that GPT-5 would significantly outperform its predecessors in terms of language understanding, problem-solving, and reasoning abilities. However, the development process exposed several limitations in their existing approach. Despite substantial financial resources and time, the improvements in GPT-5 were incremental rather than transformational.</p>
<p><strong>Resource Intensive Endeavors</strong></p>
<p>The development of these large-scale models is resource-intensive, requiring vast amounts of data, computational power, and human expertise. As investments grew and progress remained slow, questions arose about the sustainability and scalability of OpenAI&#x27;s existing research and development methodology.</p>
<h2>A New Strategic Direction</h2>
<p>In response to the mounting challenges, OpenAI decided to pivot its strategy. Here are the key aspects of their new direction:</p>
<p><strong>1. Refocusing on Core Competencies</strong> OpenAI is now placing greater emphasis on refining and scaling existing models rather than pursuing newer versions. This strategic shift will allow them to maximize the utility of their current technology while addressing the shortcomings encountered with GPT-5.</p>
<p><strong>2. Enhancing Multimodal Capabilities</strong> Another major pivot is towards enhancing multimodal AI capabilities, combining language models with other forms of AI such as visual and auditory processing. This integration aims to create more versatile and holistic AI systems capable of performing a wider range of tasks.</p>
<p><strong>3. Emphasizing Ethical Considerations</strong> The pivot also involves a heightened focus on ethical AI development. OpenAI is committed to ensuring their technologies are developed and deployed responsibly, mitigating potential risks associated with powerful AI systems.</p>
<h2>Conclusion</h2>
<p>The $19.6 billion pivot undertaken by OpenAI underscores the complexities and challenges inherent in advancing AI technology. While the struggle with GPT-5 highlights the difficulties of pushing the boundaries of what is technically feasible, OpenAI&#x27;s new strategy represents a more sustainable and diversified approach to AI research and development. The company remains at the forefront of AI innovation, continuously evolving to meet the demands of this rapidly changing field.</p>]]></content:encoded>
      <category>AI</category>
      <category>OpenAI</category>
      <category>GPT-5</category>
      <category>Technology</category>
      <category>AI Strategy</category>
      <category>Innovation</category>
    </item>
    <item>
      <title>Testing Strategies and Integration with BDD, TDD, ReqNRoll, Playwright, and Test Containers on a ReactJS, .NET 8, and MSSQL Setup</title>
      <link>https://elijah.mondero.nz/post/testing-strategies/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/testing-strategies/</guid>
      <pubDate>Mon, 24 Feb 2025 12:10:34 +0000</pubDate>
      <description>Explore the integration of BDD, TDD, ReqNRoll, Playwright, and Test Containers in your ReactJS, .NET 8, and MSSQL projects to enhance your software quality and streamline development processes.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/52c25484-49a7-487c-9f90-b9205a405e68.png" alt="Testing Strategies and Integration with BDD, TDD, ReqNRoll, Playwright, and Test Containers on a ReactJS, .NET 8, and MSSQL Setup" /></p>
<h2>Introduction</h2>
<p>In the modern era of software development, maintaining high-quality code while ensuring swift delivery can be a challenging task. Fortunately, methodologies like Behavior-Driven Development (BDD) and Test-Driven Development (TDD), along with tools like ReqNRoll, Playwright, and Test Containers, offer structured ways to achieve this. We will delve into these strategies and demonstrate their integration within a ReactJS, .NET 8, and MSSQL setup.</p>
<h2>Understanding BDD and TDD</h2>
<h3>BDD - Behavior-Driven Development</h3>
<p>Behavior-Driven Development (BDD) is an agile software development methodology that encourages collaboration among developers, testers, and non-technical stakeholders. BDD focuses on creating clear, business-centric specifications in the form of user stories and behaviors. This ensures a shared understanding of the project requirements and expected outcomes.</p>
<h3>TDD - Test-Driven Development</h3>
<p>Test-Driven Development (TDD) is a software development technique where tests are written before the actual code. TDD follows a simple cycle: write a test, make it pass, and refactor the code. This iterative process helps in catching issues early, promoting cleaner code, and maintaining a robust suite of automated tests.</p>
<h2>Key Technologies</h2>
<h3>ReqNRoll</h3>
<p>ReqNRoll is an open-source BDD test automation framework for .NET projects. It has a cucumber-style approach and replaces the SpecFlow project, offering advanced features for writing clear and maintainable tests.</p>
<h3>Playwright</h3>
<p>Playwright is a powerful test automation framework developed by Microsoft, enabling reliable end-to-end testing for modern web applications across multiple browsers such as Chromium, Firefox, and WebKit. It supports parallel test execution, automatic waiting, and extensive browser context APIs.</p>
<h3>Test Containers</h3>
<p>Testcontainers is a free, open-source library that enables the management of Docker containers for testing purposes. It simplifies integration testing by allowing real instances of dependencies, such as databases and message brokers, to be spun up in isolated containers directly from the test suite.</p>
<h3>ReactJS</h3>
<p>ReactJS is a popular JavaScript library for building user interfaces. Its component-based architecture and unidirectional data flow make it a go-to choice for developing scalable, robust front-end applications.</p>
<h3>.NET 8</h3>
<p>.NET 8 is the latest iteration of Microsoft&#x27;s cross-platform development framework. It brings numerous improvements, including Native AOT, enhanced Blazor navigation, and expanded runtime optimizations.</p>
<h3>MSSQL</h3>
<p>Microsoft SQL Server (MSSQL) is a powerful, enterprise-grade relational database management system (RDBMS) that serves as the backend for many applications. Its robust features include built-in AI, vector search capabilities, and compliance standards.</p>
<h2>Integration Steps</h2>
<h3>Setting Up the Environment</h3>
<ol>
<li><strong>ReactJS</strong>: Initialize a ReactJS project using <code>create-react-app</code>.</li>
</ol>
<pre>   npx create-react-app my-app
   cd my-app
   npm start
   </pre>
<ol>
<li><strong>.NET 8</strong>: Create a new .NET 8 project.</li>
</ol>
<pre>   dotnet new webapi -n MyApp
   cd MyApp
   dotnet run
   </pre>
<ol>
<li><strong>MSSQL</strong>: Set up MSSQL Server using Docker.</li>
</ol>
<pre>   docker run -e &#x27;ACCEPT_EULA=Y&#x27; -e &#x27;SA_PASSWORD=Your_password123&#x27; \
   -p 1433:1433 --name sql1 -h sql1 \
   -d mcr.microsoft.com/mssql/server:2019-latest
   </pre>
<h3>Installing and Configuring ReqNRoll</h3>
<p>Install ReqNRoll by adding the necessary NuGet packages to your .NET project.</p>
<pre>   dotnet add package Reqnroll
   </pre>
<p>Configure ReqNRoll in your test project to enable BDD-style scenarios.</p>
<h3>Playwright Setup</h3>
<p>Install Playwright in your ReactJS project.</p>
<pre>   npm install @playwright/test
   npx playwright install
   </pre>
<p>Create Playwright test scripts to automate your end-to-end scenarios.</p>
<h3>Utilizing Test Containers</h3>
<p>In your .NET project, install the Testcontainers NuGet package.</p>
<pre>   dotnet add package Testcontainers
   </pre>
<p>Create integration tests that spin up real instances of MSSQL for testing.</p>
<h3>Best Practices</h3>
<ol>
<li><strong>Clear and Maintainable Tests</strong>: Write clear, concise tests that are easy to understand and maintain. BDD frameworks like ReqNRoll help with this by allowing natural language specifications.</li>
</ol>
<ol>
<li><strong>Automate Early and Often</strong>: Continuously integrate and automate tests to catch defects early and ensure consistency throughout the development lifecycle.</li>
</ol>
<ol>
<li><strong>Isolate Dependencies</strong>: Use Testcontainers to isolate dependencies, ensuring your tests are not affected by external factors and providing a more reliable testing environment.</li>
</ol>
<ol>
<li><strong>Parallel Execution</strong>: Leverage the parallel execution capabilities of Playwright to speed up your test suite and make the most of available resources.</li>
</ol>
<ol>
<li><strong>Collaboration and Communication</strong>: Foster collaboration between developers, testers, and stakeholders by using BDD to bridge the communication gap and align on project goals.</li>
</ol>
<h2>Conclusion</h2>
<p>By integrating BDD, TDD, ReqNRoll, Playwright, and Test Containers in your ReactJS, .NET 8, and MSSQL setup, you can significantly enhance your development workflow, catch defects early, and ensure high-quality software. These practices and tools provide a robust framework to manage testing complexities, making your development process more efficient and reliable.</p>]]></content:encoded>
      <category>BDD</category>
      <category>TDD</category>
      <category>ReqNRoll</category>
      <category>Playwright</category>
      <category>Test Containers</category>
      <category>ReactJS</category>
      <category>.NET 8</category>
      <category>MSSQL</category>
    </item>
    <item>
      <title>The Advancements in Training Large Language Models in 2024 and 2025</title>
      <link>https://elijah.mondero.nz/post/llm-advancements-2024-2025/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/llm-advancements-2024-2025/</guid>
      <pubDate>Sat, 22 Feb 2025 06:01:56 +0000</pubDate>
      <description>A comprehensive review of the significant strides made in the training of large language models (LLMs) in 2024 and 2025.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/b06d9198-772f-4e5e-b986-6e65e1a4ab0c.png" alt="The Advancements in Training Large Language Models in 2024 and 2025" /></p>
<h2>Introduction</h2>
<p>The years 2024 and 2025 marked significant advancements in the training process of large language models (LLMs). It was a period of exceptional innovation and progression. The growing interest in models, like ChatGPT which amassed over 200 million monthly users, spurred the development in LLM training.</p>
<h2>Training Trends</h2>
<p>One prime focus of LLM training in these years was the integration of real-time data for fact-checking. This revolutionary trend led to models accessing external sources and providing citations for their responses, thus generating more precise and up-to-date information than before. Implementing this innovation, models such as Microsoft Copilot enhanced their learning capacities by ingesting live internet data.</p>
<p>Another emerging trend that gained prominence was the creation of synthetic training data. It was an exciting development where models generated their own datasets. Google&#x27;s LLM dramatically exhibited this improvement. It had the ability to develop questions and self-fine-tune based on the responses, significantly enhancing its performance.</p>
<h2>Highlighting LLM Models</h2>
<p>ChatGPT and Google’s LLMs stand out as the benchmark for trends and advancements in LLM training. These models integrated innovative techniques like real-time data ingestion and synthetic data generation, paving the path for future LLM training.</p>
<h2>Conclusion</h2>
<p>In retrospect, the years 2024 and 2025 were transformative for LLM training. The shift towards real-time data integration and synthetic data creation indicates an exciting future for LLM training. It will indeed be intriguing to see how these trends evolve and shape the future of LLMs.</p>]]></content:encoded>
      <category>AI</category>
      <category>LLM</category>
      <category>Training</category>
      <category>Future Trends</category>
    </item>
    <item>
      <title>Exploring RAG (Retrieval-Augmented Generation) Techniques with Example Code</title>
      <link>https://elijah.mondero.nz/post/exploring-rag-techniques/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/exploring-rag-techniques/</guid>
      <pubDate>Fri, 21 Feb 2025 06:33:24 +0000</pubDate>
      <description>Discover the power of Retrieval-Augmented Generation (RAG) techniques in enhancing the capabilities of language models. This blog post provides a detailed guide on building a RAG application with LangChain, including example code and practical use cases.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/36d0755b-6e08-4ae1-98d3-397ff1ea5678.png" alt="Exploring RAG (Retrieval-Augmented Generation) Techniques with Example Code" /></p>
<p>Retrieval-Augmented Generation (RAG) is a powerful technique that combines retrieval-based methods with generative models to improve the accuracy and relevance of generated content. By leveraging large datasets, RAG can answer questions more effectively by retrieving pertinent information and generating contextually appropriate responses. In this blog post, we will explore the steps to build a RAG application using LangChain and provide example code to demonstrate its capabilities.</p>
<h3>Prerequisites</h3>
<p>Before diving into the implementation, ensure you have the required libraries installed. Execute the following command to install the necessary packages:</p>
<pre>!pip install langchain langchain_community langchainhub langchain-openai tiktoken chromadb
</pre>
<h3>Setting Up Environment Variables</h3>
<p>LangChain integrates with various APIs to enable tracing and embedding generation. Set up the required environment variables for LangChain and OpenAI:</p>
<pre>import os
os.environ[&#x27;LANGSMITH_TRACING&#x27;] = &#x27;true&#x27;
os.environ[&#x27;LANGSMITH_API_KEY&#x27;] = &#x27;&lt;langsmith-api-key&gt;&#x27;
os.environ[&#x27;OPENAI_API_KEY&#x27;] = &#x27;&lt;openai-api-key&gt;&#x27;
</pre>
<h3>Step 1: Indexing Content</h3>
<p>Indexing is the process of preparing your dataset for retrieval. In this example, we load and process a blog post for indexing.</p>
<h4>Loading the Blog Content</h4>
<p>We use <code>WebBaseLoader</code> to scrape the content from a blog URL. In this case, the content is restricted to certain HTML classes using BeautifulSoup:</p>
<pre>import bs4
from langchain_community.document_loaders import WebBaseLoader

loader = WebBaseLoader(
    web_paths=(&quot;https://lilianweng.github.io/posts/2023-06-23-agent/\&quot;,),
    bs_kwargs=dict(
        parse_only=bs4.SoupStrainer(
            class_=(\&quot;post-content\&quot;, \&quot;post-title\&quot;, \&quot;post-header\&quot;)
        )
    ),
)
blog_docs = loader.load()
</pre>
<h4>Splitting the Content</h4>
<p>Large documents need to be divided into manageable chunks for efficient retrieval. This process ensures that the system can handle queries effectively by focusing on smaller, relevant sections of data:</p>
<pre>from langchain.text_splitter import RecursiveCharacterTextSplitter

text_splitter = RecursiveCharacterTextSplitter.from_tiktoken_encoder(
    chunk_size=300,
    chunk_overlap=50
)
splits = text_splitter.split_documents(blog_docs)
</pre>
<h4>Indexing with Embeddings</h4>
<p>The document chunks are converted into vector embeddings using OpenAI’s embedding model and stored in a vector database (Chroma):</p>
<pre>from langchain_openai import OpenAIEmbeddings
from langchain_community.vectorstores import Chroma

embedding = OpenAIEmbeddings(model=&quot;text-embedding-3-large&quot;)
vectorstore = Chroma.from_documents(documents=splits, embedding=embedding)
retriever = vectorstore.as_retriever()
</pre>
<h3>Step 2: Retrieval</h3>
<p>The retriever enables the search functionality for fetching the most relevant chunks of content based on a query:</p>
<pre>retriever = vectorstore.as_retriever(search_kwargs={&quot;k&quot;: 1})
</pre>
<h3>Step 3: Generating Responses</h3>
<p>With the retriever in place, we now configure a language model to generate responses based on the retrieved content.</p>
<h3>Conclusion</h3>
<p>RAG techniques significantly enhance the capabilities of language models by combining retrieval-based methods with generative models. By following the steps outlined in this blog post, you can build a RAG application using LangChain and explore the potential of this powerful technique.</p>]]></content:encoded>
      <category>RAG</category>
      <category>Retrieval-Augmented Generation</category>
      <category>LangChain</category>
      <category>Example Code</category>
      <category>AI Techniques</category>
    </item>
    <item>
      <title>Top Container Images Every .NET, ReactJS, and Generative AI Developer Must Have</title>
      <link>https://elijah.mondero.nz/post/container-images-for-developers/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/container-images-for-developers/</guid>
      <pubDate>Thu, 20 Feb 2025 19:58:46 +0000</pubDate>
      <description>Discover the essential container images for .NET, ReactJS, and Generative AI developers to streamline your development workflow and enhance productivity.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/e9a04063-9fab-480a-9f0c-74b98e34a0fd.png" alt="Top Container Images Every .NET, ReactJS, and Generative AI Developer Must Have" /></p>
<p>In the ever-evolving world of software development, containerization has become an indispensable tool for developers across various domains. Whether you are working with .NET, ReactJS, or Generative AI, having the right container images can significantly enhance your development experience. Here, we present the top container images that every developer in these fields should consider integrating into their workflow.</p>
<h3>.NET Developers</h3>
<ol>
<li><strong>mcr.microsoft.com/dotnet/aspnet</strong>: This image is essential for running .NET Core and ASP.NET Core applications in a production environment. It includes the ASP.NET Core runtime and libraries.</li>
</ol>
<ol>
<li><strong>mcr.microsoft.com/dotnet/sdk</strong>: Ideal for development and build environments, this image contains the .NET SDK, allowing you to build and test your .NET applications.</li>
</ol>
<ol>
<li><strong>mcr.microsoft.com/dotnet/runtime</strong>: A lightweight image that includes only the .NET runtime, perfect for running console apps and microservices.</li>
</ol>
<ol>
<li><strong>mcr.microsoft.com/dotnet/nightly</strong>: For those who want to stay on the cutting edge, this image provides the latest nightly builds of .NET SDK and runtime.</li>
</ol>
<h3>ReactJS Developers</h3>
<ol>
<li><strong>node</strong>: The official Node.js image is a must-have for React developers. It allows you to run your React applications and use npm or yarn for package management.</li>
</ol>
<ol>
<li><strong>nginx</strong>: Often used as a reverse proxy, the Nginx image can serve your React applications efficiently in production.</li>
</ol>
<ol>
<li><strong>cypress/included</strong>: This image includes Cypress, a popular end-to-end testing framework for JavaScript applications, making it easier to test your React apps.</li>
</ol>
<ol>
<li><strong>browserless/chrome</strong>: Provides a headless Chrome browser for running automated tests or rendering React components server-side.</li>
</ol>
<h3>Generative AI Developers</h3>
<ol>
<li><strong>tensorflow/tensorflow</strong>: The official TensorFlow image is crucial for developing and deploying machine learning models, including those used in generative AI projects.</li>
</ol>
<ol>
<li><strong>pytorch/pytorch</strong>: This image is essential for developers working with PyTorch, another popular deep learning framework.</li>
</ol>
<ol>
<li><strong>jupyter/tensorflow-notebook</strong>: Combines Jupyter Notebook with TensorFlow, providing an interactive environment for developing and testing AI models.</li>
</ol>
<ol>
<li><strong>nvidia/cuda</strong>: For those leveraging GPU acceleration in their AI models, the NVIDIA CUDA image is a must-have.</li>
</ol>
<p>By integrating these container images into your development workflow, you can ensure a consistent and efficient development process across different environments. Whether you are building web applications with React, developing robust .NET applications, or working on cutting-edge AI models, these container images will help you streamline your development efforts and boost productivity.</p>]]></content:encoded>
      <category>Docker</category>
      <category>Containerization</category>
      <category>.NET</category>
      <category>ReactJS</category>
      <category>Generative AI</category>
      <category>Development</category>
    </item>
    <item>
      <title>Top Common Pitfalls in .NET Development and How to Avoid Them</title>
      <link>https://elijah.mondero.nz/post/dotnet-common-pitfalls/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/dotnet-common-pitfalls/</guid>
      <pubDate>Thu, 20 Feb 2025 11:39:13 +0000</pubDate>
      <description>In this blog post, we explore the latest common pitfalls in .NET development and how to avoid them. We also provide practical code examples to help developers improve their coding practices.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/9065429f-4991-4fc8-b23b-4d89f5731552.png" alt="Top Common Pitfalls in .NET Development and How to Avoid Them" /></p>
<p>In the world of modern .NET development, developers often encounter various pitfalls that can lead to bugs, performance issues, and unresponsive applications. In this post, we will explore some of the latest common pitfalls in .NET development and provide practical solutions with code examples to help you avoid them.</p>
<h2>1. Incorrect Usage of Async/Await</h2>
<p>The async/await paradigm is essential for efficient asynchronous programming in .NET. However, improper usage can lead to deadlocks or unresponsive applications.</p>
<h3>Mistake:</h3>
<p>Blocking an asynchronous operation with <code>.Result</code> or <code>.Wait()</code>.</p>
<pre>var result = SomeAsyncMethod().Result; // Potential deadlock
</pre>
<h3>Solution:</h3>
<p>Always <code>await</code> asynchronous methods to avoid blocking.</p>
<pre>var result = await SomeAsyncMethod();
</pre>
<h2>2. Neglecting to Dispose of Resources</h2>
<p>Failing to release unmanaged resources like database connections or file streams can cause memory leaks.</p>
<h3>Mistake:</h3>
<p>Forgetting to call <code>Dispose()</code> or not using <code>using</code> statements.</p>
<pre>var stream = new FileStream(&quot;file.txt&quot;, FileMode.Open);
// Forgetting to dispose of the stream
</pre>
<h3>Solution:</h3>
<p>Use <code>using</code> blocks or <code>IAsyncDisposable</code> in modern C#.</p>
<pre>using (var stream = new FileStream(&quot;file.txt&quot;, FileMode.Open))
{
    // Use the stream
}
</pre>
<h2>3. Inefficient Database Interactions</h2>
<p>Optimizing database interactions is crucial for application performance. Common issues include the N+1 query problem and inefficient queries.</p>
<h3>Mistake:</h3>
<p>Using multiple queries to fetch related data.</p>
<h3>Solution:</h3>
<p>Use JOINs or eager loading to fetch all necessary data in a single query.</p>
<pre>SELECT c.CustomerName, o.OrderID
FROM Customers c
JOIN Orders o ON c.CustomerID = o.CustomerID;
</pre>
<h2>4. Poor Exception Handling in Async/Await</h2>
<p>Effective exception handling in asynchronous methods is key for application stability.</p>
<h3>Mistake:</h3>
<p>Not enclosing async calls in try-catch blocks.</p>
<pre>try
{
    await SomeAsyncMethod();
}
catch (Exception ex)
{
    // Handle the exception
}
</pre>
<h2>5. Ignoring Cancellation Tokens</h2>
<p>Implementing cancellation tokens provides a mechanism to cancel long-running operations, enhancing application responsiveness.</p>
<h3>Solution:</h3>
<p>Use cancellation tokens in asynchronous methods.</p>
<pre>public async Task SomeAsyncMethod(CancellationToken cancellationToken)
{
    // Check for cancellation
    cancellationToken.ThrowIfCancellationRequested();
    await Task.Delay(1000, cancellationToken);
}
</pre>
<p>By being aware of these common pitfalls and following the recommended practices, developers can create more responsive, efficient, and maintainable .NET applications.</p>]]></content:encoded>
      <category>dotnet</category>
      <category>development</category>
      <category>async-await</category>
      <category>database</category>
      <category>csharp</category>
    </item>
    <item>
      <title>Life-Changing AI Tools: Transforming Our World</title>
      <link>https://elijah.mondero.nz/post/life-changing-ai-tools/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/life-changing-ai-tools/</guid>
      <pubDate>Thu, 20 Feb 2025 04:30:27 +0000</pubDate>
      <description>Explore some of the most impactful AI tools that are changing lives and solving real-world problems.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/8116aeb0-677f-4bf0-a2d7-765ed86c384d.png" alt="Life-Changing AI Tools: Transforming Our World" /></p>
<p>Artificial Intelligence (AI) has revolutionized many aspects of our lives, offering solutions to complex problems and making everyday tasks easier. Here are some life-changing AI tools that are making a significant impact:</p>
<ol>
<li><strong>GPT-4 by OpenAI</strong>: A state-of-the-art language model that can generate human-like text, assist in creative writing, translate languages, and even help with coding. It solves the problem of content creation and communication barriers.</li>
</ol>
<ol>
<li><strong>DeepMind&#x27;s AlphaFold</strong>: This AI tool predicts protein structures with high accuracy, which is crucial for understanding diseases and developing new medicines. It addresses the challenge of understanding the complex nature of proteins.</li>
</ol>
<ol>
<li><strong>Tesla&#x27;s Autopilot</strong>: An advanced driver-assistance system that enhances vehicle safety and convenience. It tackles the issues of road safety and driver fatigue.</li>
</ol>
<ol>
<li><strong>Google Assistant</strong>: A virtual assistant powered by AI that helps users with tasks such as setting reminders, answering questions, and controlling smart home devices. It solves the problem of managing daily tasks efficiently.</li>
</ol>
<ol>
<li><strong>IBM Watson</strong>: An AI system that can analyze large amounts of data to provide insights in fields like healthcare, finance, and customer service. It addresses the challenge of data analysis and decision-making.</li>
</ol>
<p>These tools represent just a fraction of what AI is capable of. As technology continues to evolve, we can expect even more innovative solutions that will further transform our world.</p>]]></content:encoded>
      <category>Artificial Intelligence</category>
      <category>AI Tools</category>
      <category>Technology</category>
      <category>Innovation</category>
    </item>
    <item>
      <title>Anti-Patterns</title>
      <link>https://elijah.mondero.nz/post/anti-patterns/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/anti-patterns/</guid>
      <pubDate>Wed, 19 Feb 2025 10:43:49 +0000</pubDate>
      <description>An exploration of anti-patterns in software development, their impacts, and how to avoid them.</description>
      <content:encoded><![CDATA[<p><img src="https://elijah.mondero.nz/posts/images/21b4f94c-dc5c-4864-acab-053952964bc6.png" alt="Anti-Patterns" /></p>
<p>Today, I would like to talk about anti-patterns that everyone uses unconsciously from time to time to solve problems, which can lead to bigger problems than the ones initially had. The software development process is principally based on transferring a real-life situation to the computer environment. Transferring these situations to the computer environment is actually “the problem” we need to solve. For this end, we should design our code by thinking deeply. That is to say, software development primarily tries to solve a problem. Many solutions can be produced for these problems. But sometimes, by focusing too much on the solution, we can miss the problem and produce solutions that do not fit it exactly. Although these solutions seem correct and solve our problem at first glance, they can lead to bigger ones than they can solve.</p>
<p>During this problem-solving process, it is most important to understand the problem in detail and tackle it from every angle. Because not understanding the problem well can create problems that are not entirely correct and lead to higher costs. To put it simply, approaches that seem to solve the problem but do not in reality and cause more costly problems are called anti-patterns. A pattern that is accepted by the software community and known by many developers may not be suitable for the problem at hand and may have more downsides than benefits. So, this pattern becomes an anti-pattern for our problem.</p>
<p>Although anti-patterns are grouped differently in different sources, we can fundamentally divide them into three categories: Software Development Anti-Patterns, Software Architecture Anti-Patterns and Project Management Anti-Patterns. I’m going to discuss anti-patterns more from a software-based perspective, but the logical conclusions that can be drawn from here actually emphasize similar principles on both the project management and software sides.</p>
<p>We’ve covered what an anti-pattern is, so now let’s talk about how to avoid it. In general, there are many anti-patterns and there are different ways to avoid them. But we can draw a general framework and come up with an approach to prevent these issues from occurring.</p>
<p>As I mentioned above, I believe the most important point lies in understanding the problem. When we examine the problem thoroughly in all its aspects, we avoid approaches that will not be good for our problem as much as possible.</p>
<p>When talking about software development anti-patterns, it’s vital to remember the SOLID principles and always act in accordance with them during development.</p>
<p>Another point that we should not ignore while developing our software is that it should be highly cohesive and loosely coupled. If we develop software with these two approaches in mind, we will avoid anti-patterns as much as possible.</p>
<p>The advancement in software is growing day by day; new approaches, concepts and technologies are brought to the software world constantly. In addition to these, our software also must adapt to this process and evolve. For this reason, our software, which we have developed in reference to the conditions of the moment, should be designed to keep up with the innovations that may come tomorrow. Approaching our software development this way will help us avoid anti-patterns.</p>
<p>Now, I am going to briefly touch on a couple of anti-patterns.</p>
<p>Golden Hammer</p>
<p>One of the most widespread anti-patterns in the industry is the golden hammer anti-pattern. One might believe that a solution which worked well for previous problems will also be effective for new challenges we encounter. But this is not always the case. Software structures are often complex and have many aspects. There may be businesses and structures that affect each other. Although the new challenge may resemble previous issues that we’ve resolved using our tools at hand, there may be differences in many parameters, such as conditions and demands, that create the new problem. Therefore, it is important to analyze our problem well. On the other hand, the software world is constantly renewing, developing and evolving. Solutions that seem good according to yesterday’s conditions may not be good solutions for tomorrow’s problems in this developing and evolving world.</p>
<p>Symptoms</p>
<p>The instruments used in the architecture of the system are a set of technologies or belong to a single vendor.</p>
<p>The software development team cannot meet certain requests because they are too dependent on existing tools that cannot meet the needs of the project.</p>
<p>The software development team is failing to research new application development approaches and technologies and is unaware of new technologies.</p>
<p>Developers become isolated from the industry. They show a lack of knowledge and experience with alternative solutions and technologies that could better address the current needs.</p>]]></content:encoded>
      <category>software development</category>
      <category>anti-patterns</category>
      <category>SOLID principles</category>
      <category>software architecture</category>
      <category>project management</category>
    </item>
    <item>
      <title>The Future of Books: Will They Be Written by Generative AI?</title>
      <link>https://elijah.mondero.nz/post/future-of-books-ai-writing/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/future-of-books-ai-writing/</guid>
      <pubDate>Wed, 19 Feb 2025 07:42:19 +0000</pubDate>
      <description>As generative AI technologies advance, the question arises: will the future of literature be penned by algorithms? This blog explores the potential of AI in writing books and highlights viewpoints from a Reddit discussion.</description>
      <content:encoded><![CDATA[<p>The advent of generative AI has raised intriguing possibilities across various fields, including literature. With AI models like GPT-3 and GPT-4 demonstrating the ability to generate coherent and creative text, one can&#x27;t help but wonder if the future of book writing will be dominated by artificial intelligence.</p>
<p>A recent discussion on Reddit&#x27;s r/ArtificialIntelligence subreddit delved into this topic, sparking diverse opinions among users. Here are some highlights from the conversation:</p>
<ol>
<li><strong>User: AI_Enthusiast123</strong></li>
</ol>
<ul>
<li><em>&quot;I believe AI-written books will enhance creativity rather than replace human authors. Imagine a collaboration where AI assists in generating ideas or refining drafts. The human touch will still be essential to infuse emotion and depth.&quot;</em></li>
</ul>
<ol>
<li><strong>User: Skeptic_Sam</strong></li>
</ol>
<ul>
<li><em>&quot;While AI can produce text, it lacks true understanding and empathy. Books are more than just words; they convey human experiences and emotions. I doubt AI can ever match the depth of human-authored literature.&quot;</em></li>
</ul>
<ol>
<li><strong>User: Techy_Tom</strong></li>
</ol>
<ul>
<li><em>&quot;AI-written books could revolutionize the publishing industry by reducing costs and making it easier for new authors to break into the market. However, quality control will be crucial to ensure that the content remains engaging and meaningful.&quot;</em></li>
</ul>
<ol>
<li><strong>User: Future_Fan</strong></li>
</ol>
<ul>
<li><em>&quot;We might see a new genre of AI literature emerge, where readers are aware that the text is AI-generated. This could be fascinating in its own right, offering a unique reading experience distinct from human-authored works.&quot;</em></li>
</ul>
<p>The discussion underscores the mixed sentiments regarding AI&#x27;s role in literature. On one hand, AI&#x27;s ability to generate text quickly and efficiently could democratize the publishing process. On the other hand, the intrinsic value of human creativity and emotional expression remains irreplaceable.</p>
<p>As AI continues to evolve, it is likely that we will see a blend of AI and human collaboration in the literary world. Authors might leverage AI tools to enhance their writing process, while readers will have a broader array of content to choose from, including works that push the boundaries of traditional storytelling.</p>
<p>To read the full Reddit discussion, click <a href="https://www.reddit.com/r/ArtificialInteligence/s/UqjfmwyGl6">here</a>.</p>]]></content:encoded>
      <category>AI</category>
      <category>Literature</category>
      <category>Generative AI</category>
      <category>Future of Books</category>
      <category>Reddit Discussion</category>
    </item>
    <item>
      <title>The Importance of Scalable Architecture in Small Scale Projects: A .NET Community Discussion</title>
      <link>https://elijah.mondero.nz/post/importance-scalable-architecture-small-projects/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/importance-scalable-architecture-small-projects/</guid>
      <pubDate>Tue, 18 Feb 2025 22:38:35 +0000</pubDate>
      <description>In a recent discussion on the .NET subreddit, the community delved into the importance of scalable architecture in small-scale projects. While opinions varied, a common theme emerged: even for smaller projects, considering future scalability is crucial for long-term success.</description>
      <content:encoded><![CDATA[<p>In the fast-paced world of software development, the .NET community often finds itself debating best practices and architectural decisions. One such discussion that recently caught my attention was centered around the importance of implementing scalable architecture in small-scale projects.</p>
<p>At first glance, it might seem like overkill to invest in a robust, scalable architecture for a project that is just starting out or is intended to be small in scope. However, as many experienced developers in the community pointed out, neglecting scalability can lead to significant challenges down the road.</p>
<p><strong>The Case for Scalable Architecture</strong></p>
<p>One of the main arguments in favor of scalable architecture, even for smaller projects, is the unpredictability of future growth. What starts as a small project can quickly evolve into something much larger, particularly if it gains traction among users. A well-thought-out architecture ensures that the system can handle increased load and complexity without requiring a complete overhaul.</p>
<p>Moreover, building with scalability in mind from the outset can save time and resources in the long run. Refactoring a system to scale after it has already been built and deployed can be a daunting task, often resulting in downtime and increased costs.</p>
<p><strong>Balancing Practicality and Future-Proofing</strong></p>
<p>However, this doesn&#x27;t mean that every small project should be built with the same level of complexity as a large-scale enterprise application. The key lies in finding a balance between practicality and future-proofing.</p>
<p>For smaller projects, it might not be practical to implement every aspect of a scalable architecture right away. Instead, developers can focus on creating a flexible and modular design that can be easily extended as the project grows. This approach allows for a lean initial development phase while still keeping an eye on future scalability.</p>
<p><strong>Cloud Engineering Considerations</strong></p>
<p>Cloud engineering plays a pivotal role in achieving scalable architecture. Leveraging cloud services can provide the necessary infrastructure to scale applications seamlessly. Services like Azure or AWS offer a range of tools and services that can help manage and scale applications efficiently.</p>
<p>For smaller projects, starting with a basic cloud setup can be cost-effective and provide a solid foundation for future growth. As the project expands, additional cloud resources can be integrated without significant disruption.</p>
<p><strong>Conclusion</strong></p>
<p>In conclusion, while it might seem like an unnecessary effort to focus on scalable architecture for small-scale projects, the benefits far outweigh the drawbacks. By considering future growth and implementing a flexible, modular design, developers can ensure their projects are prepared for success, no matter how much they grow. Cloud engineering provides the tools and infrastructure needed to support this scalability, making it an essential consideration for any project.</p>
<p>As the .NET community continues to evolve and share insights, discussions like these highlight the importance of thoughtful architectural decisions in ensuring the longevity and success of software projects.</p>]]></content:encoded>
      <category>.NET</category>
      <category>Scalable Architecture</category>
      <category>Cloud Engineering</category>
      <category>Software Development</category>
      <category>Future-Proofing</category>
    </item>
    <item>
      <title>The Evolution and Maturation of Large Language Models</title>
      <link>https://elijah.mondero.nz/post/envolution-maturation-llms/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/envolution-maturation-llms/</guid>
      <pubDate>Tue, 18 Feb 2025 11:07:11 +0000</pubDate>
      <description>Explore the fascinating journey of large language models (LLMs) from their historical roots to their current state of maturity, highlighting key developments along the way.</description>
      <content:encoded><![CDATA[<p>Large language models (LLMs) have undergone a rapid evolution, becoming a cornerstone of modern AI applications. These models, based on artificial neural networks, have their origins rooted in the early study of semantics by Michel Bréal in 1883. Bréal&#x27;s work laid the foundation for understanding how languages are structured and evolve.</p>
<p>The field of natural language processing (NLP) saw significant advancements in the early 20th century, thanks to Ferdinand de Saussure&#x27;s work, which was later compiled and published posthumously by his colleagues. This foundational work in linguistics paved the way for the development of NLP techniques that translate human language for computer understanding.</p>
<p>Post-World War II, the need for language translation spurred further research in NLP. The goal was to create machines capable of translating languages automatically. While initial attempts faced challenges due to the complexity of human languages, this period marked the beginning of significant interest in machine learning and neural networks.</p>
<p>In the 1950s, Arthur Samuel&#x27;s work on machine learning with a checkers-playing program and Frank Rosenblatt&#x27;s creation of the Mark 1 Perceptron, an early neural network, were pivotal. These developments demonstrated the potential of neural networks, despite early limitations in pattern recognition.</p>
<p>The maturation of LLMs accelerated with the advent of deep learning techniques. These models, capable of understanding and generating human-like text, have become integral to AI applications such as chatbots and virtual assistants. The release of ChatGPT and similar models has revolutionized the way we interact with AI, reaching millions of users in a short period.</p>
<p>Today, LLMs are trained using vast datasets and self-supervised learning methods. These techniques allow models to learn from unannotated text, predicting the next word in a sentence and internalizing linguistic patterns. The result is a pre-trained model that can perform a wide range of natural language tasks.</p>
<p>Despite their advancements, LLMs pose challenges, including the risk of generating misinformation or offensive content. Techniques like Reinforcement Learning from Human Feedback (RLHF) are employed to align these models with human values and improve their reliability.</p>
<p>The journey of LLMs from theoretical concepts to practical applications showcases the remarkable progress in AI. As these models continue to evolve, they hold the promise of further transforming our interaction with technology.</p>
<p>For a detailed history and understanding of LLMs, refer to the original articles from <a href="https://www.dataversity.net/a-brief-history-of-large-language-models/">DATAVERSITY</a> and <a href="https://www.assemblyai.com/blog/the-full-story-of-large-language-models-and-rlhf/">AssemblyAI</a>.</p>]]></content:encoded>
      <category>AI</category>
      <category>Machine Learning</category>
      <category>Natural Language Processing</category>
      <category>LLMs</category>
      <category>AI History</category>
      <category>AI Evolution</category>
      <category>AI Maturation</category>
      <category>AI Generated Content</category>
      <category>aigen</category>
    </item>
    <item>
      <title>South Korea's DeepSeek Faces Competition from China's AI Giants</title>
      <link>https://elijah.mondero.nz/post/deepseek-china-ai-competition/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/deepseek-china-ai-competition/</guid>
      <pubDate>Tue, 18 Feb 2025 10:44:26 +0000</pubDate>
      <description>South Korea's leading AI company, DeepSeek, is encountering increasing competition from China's rapidly advancing AI sector.</description>
      <content:encoded><![CDATA[<p>In recent years, South Korea has emerged as a significant player in the field of artificial intelligence (AI). One of its leading companies, DeepSeek, has been at the forefront of AI research and development. However, DeepSeek is now facing stiff competition from China&#x27;s AI giants, who are investing heavily in this technology.</p>
<p>China has made AI a national priority, with substantial resources being poured into research, development, and implementation. This has resulted in rapid advancements and a competitive edge in the global AI market. Companies like Baidu, Tencent, and Alibaba are leading the charge, making significant strides in AI applications ranging from autonomous driving to natural language processing.</p>
<p>DeepSeek, on the other hand, has been a pioneer in AI innovation within South Korea. The company has developed cutting-edge technologies and solutions that have garnered international attention. However, the scale and pace of China&#x27;s AI advancements pose a significant challenge.</p>
<p>The competition between DeepSeek and China&#x27;s AI giants is not just a business rivalry; it has broader implications for technological leadership and economic power. As both countries continue to push the boundaries of AI, the world watches closely to see which will emerge as the leader in this transformative field.</p>
<p>For more information, you can read the full article on <a href="https://www.nytimes.com/2025/02/17/business/south-korea-deepseek-china-ai.html">The New York Times</a>.</p>]]></content:encoded>
      <category>South Korea</category>
      <category>DeepSeek</category>
      <category>China</category>
      <category>AI</category>
      <category>Technology</category>
      <category>Business</category>
    </item>
    <item>
      <title>.NET 9 Release: What's New and Improved</title>
      <link>https://elijah.mondero.nz/post/dotnet-9-release/</link>
      <guid isPermaLink="true">https://elijah.mondero.nz/post/dotnet-9-release/</guid>
      <pubDate>Tue, 18 Feb 2025 10:19:04 +0000</pubDate>
      <description>Discover the latest features, breaking changes, and updates in the .NET 9 release, including new security measures, API changes, and improvements in C# 13.</description>
      <content:encoded><![CDATA[<p>The .NET 9 release brings a host of new features and improvements across various components, enhancing the developer experience and expanding the framework&#x27;s capabilities. Here are some of the major highlights:</p>
<ol>
<li><strong>.NET Security</strong>: The .NET 9 release includes updated articles on cross-platform cryptography, providing enhanced security features to protect your applications.</li>
</ol>
<ol>
<li><strong>Breaking Changes</strong>: Several breaking changes have been introduced, including updates to nullability annotations, modifications to the BindingSource.SortDescriptions, and changes in the behavior of certain API methods. Notably, the In-box BinaryFormatter implementation has been removed and always throws exceptions now.</li>
</ol>
<ol>
<li><strong>.NET Fundamentals</strong>: New articles and updates have been added, such as CA2022: Avoid inexact read with Stream.Read and CA2265: Do not compare Span&lt;T&gt; to null or default. Additionally, configuration source generators and code quality rules have been enhanced.</li>
</ol>
<ol>
<li><strong>SDK and Tooling</strong>: The SDK and tooling for .NET 9 have seen significant updates, improving the overall development workflow and providing better support for modern development practices.</li>
</ol>
<ol>
<li><strong>C# 13</strong>: The latest version of C# introduces new features and improvements, including better conversion from collection expressions, ref struct allowed in interfaces, and enhanced support for async methods and iterators. The language also adds conceptual content for partial properties and better handling of compiler errors and warnings.</li>
</ol>
<p>These updates and many more make the .NET 9 release a significant milestone for developers, offering new capabilities and improvements to build more secure, efficient, and powerful applications.</p>]]></content:encoded>
      <category>dotnet</category>
      <category>.NET 9</category>
      <category>C#</category>
      <category>software development</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
