<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Books on Corebaseit — POS · EMV · Payments · AI · Telecommunications</title><link>https://corebaseit.com/books/</link><description>Recent content in Books on Corebaseit — POS · EMV · Payments · AI · Telecommunications</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>contact@corebaseit.com (Vincent Bevia)</managingEditor><webMaster>contact@corebaseit.com (Vincent Bevia)</webMaster><lastBuildDate>Sun, 05 Apr 2026 06:00:00 +0100</lastBuildDate><atom:link href="https://corebaseit.com/books/index.xml" rel="self" type="application/rss+xml"/><item><title>Point-of-Sale Systems Architecture</title><link>https://corebaseit.com/books/point-of-sale-systems-architecture/</link><pubDate>Sun, 05 Apr 2026 06:00:00 +0100</pubDate><author>contact@corebaseit.com (Vincent Bevia)</author><guid>https://corebaseit.com/books/point-of-sale-systems-architecture/</guid><description>&lt;p>Architecting modern payment acceptance is harder than it looks. Between EMV, SoftPOS/MPoC, PCI DSS, HSMs, ISO 8583, Tap to Pay on COTS devices, and backend patterns that must stay idempotent under retries, it is easy to get lost in vendor docs and scheme PDFs.&lt;/p>
&lt;p>This book ties those pieces into one architecture-first guide for engineers who need to &lt;strong>design and ship&lt;/strong> real POS and SoftPOS systems — not just draw scheme diagrams.&lt;/p></description></item><item><title>Prompt as Interface</title><link>https://corebaseit.com/books/prompt-as-interface/</link><pubDate>Sun, 05 Apr 2026 06:00:00 +0100</pubDate><author>contact@corebaseit.com (Vincent Bevia)</author><guid>https://corebaseit.com/books/prompt-as-interface/</guid><description>&lt;p>Most teams still write prompts like search queries. Production systems need &lt;strong>interfaces&lt;/strong>: explicit goals, ordered constraints, schema-bound outputs, and testable behavior.&lt;/p>
&lt;p>&lt;em>Prompt as Interface&lt;/em> is for engineers building real LLM-powered systems — especially where mistakes are expensive, auditable, or regulated.&lt;/p></description></item><item><title>The Obsolescence Paradox</title><link>https://corebaseit.com/books/the-obsolescence-paradox/</link><pubDate>Sun, 05 Apr 2026 06:00:00 +0100</pubDate><author>contact@corebaseit.com (Vincent Bevia)</author><guid>https://corebaseit.com/books/the-obsolescence-paradox/</guid><description>&lt;p>Everyone is asking whether AI will replace engineers. The better question is which engineering work becomes more valuable when models handle the routine — and which mistakes get faster when nobody checks the output.&lt;/p>
&lt;p>&lt;em>The Obsolescence Paradox&lt;/em> is a practical argument for engineering judgment in the age of autonomous-looking AI: verification, accountability, and the craft that survives when implementation speed stops being the bottleneck.&lt;/p></description></item></channel></rss>