On October 9, 2026, BatchV1_1 became enabled on the XRP Ledger mainnet. For developers, this creates a practical way to group related ledger actions under one explicit execution policy. For software architects, it also creates a new responsibility: distinguish acceptance of the batch from completion of the business operation. The Read more
A package called orders does not become a bounded context just because its name sounds like the business. And an event called OrderConfirmed does not make an integration reliable just because a listener receives it on your laptop. The interesting direction in Spring Modulith is the connection between these two Read more
Test an AI payment authorization boundary in Java: tenant-scoped Spring AI tools, immutable approvals, fee caps and unsigned xrpl4j transactions.
Build a tested Java settlement boundary with xrpl4j: verify delivered value, issuer and final ledger evidence, then commit an idempotent credit and outbox event together.
Test Spring Framework 7 retries and concurrency limits with real proxies and virtual threads. Protect dependencies, avoid retry amplification, and understand timeout boundaries.
Researched October 7, 2026. A business and architecture perspective for founders who use agents across delivery, sales, support and administration. The numerical scenarios are illustrative; they are not Homann Software operating results or provider quotations. The demo ends when the agent produces a pull request. Your business day does not. Read more
Why Europe should judge AI-assisted publishing by evidence and accountability—and demand a convincing case for mandatory origin marking. A founder’s opinion, informed by sources checked on October 6, 2026. If an article is accurate, well researched and useful, why should its AI origin count against it? That is the question Read more
A solo founder can delegate substantial work to AI agents today. Here is how I would build a company around bounded jobs, overnight execution and evidence.
A worker can disappear after a credit commits. Durable orchestration preserves progress; a tested receiver contract makes repeated deliveries safe.
A blockchain explorer must explain changing history. Build a Java indexing core that handles reorgs, preserves observations and protects finalized checkpoints.