Meta tags:
description=Deep dives into Quarkus, AI tooling, and the architecture decisions that actually matter for senior Java engineers. Click to read The Main Thread, by Markus Eisele, a Substack publication with thousands of subscribers.;
author=Markus Eisele;

Headings (most frequently used words):

the, main, thread, recent, quarkus, posts, archive,

Text of the page (most frequently used words):
and (30), markus (26), eisele (26), #quarkus (23), the (22), java (11), jul (11), build (10), agent (10), with (9), jun (8), into (7), that (7), local (7), service (7), your (5), all (5), mcp (5), small (5), deterministic (5), still (5), coding (5), run (4), turn (4), for (4), view (4), use (4), one (4), code (4), not (4), catalog (4), myfear (4), multitenancy (4), tenant (4), plumbing (4), qdrant (4), wanaku (4), router (4), scripts (3), substack (3), app (3), archive (3), see (3), keep (3), ibm (3), bob (3), generated (3), before (3), find (3), you (3), feature (3), both (3), gates (3), from (3), every (3), 2025 (3), developer (3), javascript (2), home (2), recommendations (2), about (2), subscribe (2), main (2), thread (2), josh (2), long (2), data (2), cost (2), api (2), hooks (2), guardrails (2), signals (2), instead (2), ollama (2), what (2), needs (2), memory (2), visible (2), turns (2), inspect (2), real (2), around (2), test (2), tax (2), where (2), why (2), prompts (2), can (2), make (2), agents (2), using (2), skills (2), workflows (2), work (2), better (2), need (2), tests (2), refund (2), flow (2), workflow (2), spdx (2), json (2), checks (2), systems (2), they (2), quarkiverse (2), extension (2), resolve (2), tenants (2), headers (2), jwts (2), custom (2), sources (2), layer (2), free (2), without (2), incidents (2), vectors (2), hashing (2), store (2), them (2), nearest (2), past (2), failures (2), when (2), production (2), breaks (2), similar (2), incident (2), finder (2), import (2), http (2), toolset (2), forward (2), upstream (2), server (2), merge (2), getting (2), started (2), laptop (2), change (2), this, site, requires, correctly, please, unblock, great, culture, get, start, collection, notice, terms, privacy, 2026, sitemap, deep, dives, tooling, architecture, decisions, actually, matter, senior, engineers, javinpaul, javarevisited, newsletter, artur, skowronski, jvm, weekly, jess, ramos, big, energy, bilgin, ibryam, generative, programmer, bobignore, narrower, toolsets, targeted, mentions, fresh, chats, focused, cheaper, control, starts, context, hygiene, document, catch, unsafe, native, queries, semgrep, wire, instructions, repository, runs, two, models, parallel, uses, escalate, disagreement, returns, uncertain, fake, certainty, jury, follow, spec, trap, hard, part, typing, deciding, must, mean, specs, contracts, verification, makes, langchain4j, retained, pressure, call, usage, opentelemetry, eviction, budget, alex, soto, bueno, codebase, spot, dangerous, paths, user, deletion, analysis, clearer, plan, how, regression, risks, write, payload, are, selection, problems, compressing, task, brief, carries, meaning, quality, shorter, worse, practical, guide, repeated, become, controlled, engineering, prompt, just, repositories, checked, hql, managed, updates, stateless, writes, paging, validation, realistic, hibernate, new, path, persistence, keeps, policy, plain, lets, handle, cloudevents, correlation, waiting, state, restart, safe, generate, sbom, graph, exactly, ntia, cisa, fail, sboms, licenses, reliable, llm, put, model, judgment, parsers, schemas, security, scans, approval, islands, probabilistic, linkedin, github, bsky, com, mastodon, online, social, recent, posts, apr, spring, didn, teach, becoming, modern, oct, only, half, hidden, features, everything, sep, versioning, apis, four, strategies, should, know, jan, adult, room, time, move, python, most, popular, arrives, fast, but, teams, shared, design, conventions, budgets, review, output, becomes, software, rockstar, problem, hrs, ago, measure, whether, whole, produces, smaller, wrong, recoveries, clear, evidence, human, trust, evaluation, benchmark, slide, faq, notes, podcast, sign,

Text of the page (random words):
the main thread markus eisele substack subscribe sign in home podcast notes java java ai quarkus faq archive about coding agent evaluation is not a benchmark slide measure whether the whole coding agent workflow produces smaller wrong turns better recoveries clear test evidence and work a human can trust 14 hrs ago markus eisele 2 wanaku mcp router getting started on your laptop run a local wanaku router import an http toolset forward an upstream mcp server and merge both into one agent catalog jul 8 markus eisele 2 1 ai agents and the rockstar developer problem generated code arrives fast but teams still need shared design local conventions change budgets and review gates before output becomes software they jul 7 markus eisele 3 build a similar incident finder with quarkus and qdrant turn java incidents into vectors with deterministic feature hashing store them in qdrant and find the nearest past failures when production breaks jul 6 markus eisele 2 1 quarkus multitenancy without tenant plumbing in every service use the quarkiverse multitenancy extension to resolve tenants from headers jwts or custom sources and keep your service layer free of tenant plumbing jul 5 markus eisele 4 1 1 most popular view all the adult in the room why it s time to move ai from python scripts to java systems jan 1 markus eisele 16 7 3 versioning apis in quarkus four strategies every java developer should know sep 4 2025 markus eisele 15 2 you re only using half of quarkus 10 hidden features that change everything oct 25 2025 markus eisele 16 4 what spring didn t teach you becoming a modern java developer with quarkus apr 27 2025 markus eisele 14 1 1 recent quarkus posts view all wanaku mcp router getting started on your laptop run a local wanaku router import an http toolset forward an upstream mcp server and merge both into one agent catalog jul 8 markus eisele 2 1 build a similar incident finder with quarkus and qdrant turn java incidents into vectors with deterministic feature hashing store them in qdrant and find the nearest past failures when production breaks jul 6 markus eisele 2 1 quarkus multitenancy without tenant plumbing in every service use the quarkiverse multitenancy extension to resolve tenants from headers jwts or custom sources and keep your service layer free of tenant plumbing jul 5 markus eisele 4 1 1 social myfear mastodon online bsky myfear com x myfear github myfear linkedin archive view all deterministic islands in probabilistic workflows reliable agent systems do not make the llm deterministic they put model judgment around parsers schemas tests ci gates security scans and approval jul 4 markus eisele 3 quarkus spdx sboms json ld licenses real checks build a small quarkus service generate an spdx 3 0 1 sbom inspect the json ld graph and see exactly where ntia and cisa checks still fail jul 3 markus eisele 1 1 build a refund workflow with quarkus flow 0 11 build a small refund service that keeps policy in plain java and lets quarkus flow handle cloudevents correlation waiting state and restart safe jul 2 markus eisele 5 2 quarkus data hibernate a new path for java persistence build a small catalog api to see generated repositories checked hql managed updates stateless writes paging validation and tests in one realistic jul 1 markus eisele 6 1 agent skills need guardrails not just prompts a practical guide to using skills hooks scripts and qa gates so repeated agent workflows become controlled engineering work instead of better prompt jun 30 markus eisele 6 1 2 why shorter prompts can make coding agents worse catalog tax and payload tax are selection problems compressing the task brief that still carries meaning is where coding agent cost and quality both jun 29 markus eisele 2 1 5 05 how to find regression risks in a quarkus app before you write the feature use ibm bob to inspect a real quarkus codebase spot the dangerous paths around user deletion and turn that analysis into a clearer test plan jun 28 markus eisele and alex soto bueno 1 local ai in quarkus needs a visible memory budget build a small quarkus app that makes langchain4j retained memory pressure ollama call usage and opentelemetry signals visible before eviction turns jun 27 markus eisele 3 1 ai coding still needs specs contracts and verification a follow up to the spec trap the hard part still is not typing code it is deciding what the code must mean jun 26 markus eisele 5 2 build a local ai jury in quarkus with ollama build a quarkus service that runs two local models in parallel uses signals to escalate disagreement and returns uncertain instead of fake certainty jun 25 markus eisele 1 1 quarkus repository guardrails for agent generated java code build a small quarkus document api catch unsafe native queries with semgrep and wire local hooks agent instructions and ci into one deterministic jun 24 markus eisele 2 2 ibm bob cost control starts with context hygiene use bobignore narrower mcp toolsets targeted mentions and fresh chats to keep ibm bob focused and cheaper to run jun 23 markus eisele 1 1 see all recommendations view all 11 the generative programmer bilgin ibryam big data energy ️ jess ramos josh long josh long jvm weekly artur skowronski javarevisited newsletter javinpaul the main thread deep dives into quarkus ai tooling and the architecture decisions that actually matter for senior java engineers subscribe about archive recommendations sitemap 2026 markus eisele privacy terms collection notice start your substack get the app substack is the home for great culture this site requires javascript to run correctly please turn on javascript or unblock scripts