Programmer.ie is where I work through AI and software systems from first principles, then turn the useful results into books, experiments, diagnostics and working tools.
Programmer.ie is not only a publishing project. The same research and experiments should eventually become tools, systems or solution paths that can be used outside the page.
A book gives a difficult subject enough room to be understood properly. The next step is to turn that understanding into a capstone, diagnostic, experiment or working system rather than stopping at explanation.
An Experimental Search for Life-Like Organization in Computation
What would it take for a computational system to earn the language of life?
An experimental search for life-like organization in computational systems — through emergence, causality, persistence, material turnover, hidden state and finite computation.
Read the book →
What actually makes an AI system an agent, and what makes that agent reliable?
Build reliable AI agents by understanding the mechanisms underneath them: control loops, actions, validation, planning, state, tools, memory, search, and external verification.
Read the book →The intended shape of the site is simple: start with a problem or question, understand the mechanism, test it, and turn the result into something usable. Books, articles, experiments and solutions are different stages of that loop rather than separate publishing channels.
Over time, each major book should have a practical destination: a capstone, diagnostic, tool, demo or product that makes the ideas concrete.
Work from first principles until the mechanism, trade-offs and evidence are clear.
Use code, experiments and reproducible evidence to find what actually survives contact with reality.
Turn the useful result into a capstone, diagnostic, tool, demo or working system.
Make the result accessible from the problem people are trying to solve, not only from the publication that produced it.
If that is true, AI is not simply another technology category. It changes programming, research, finance, software, knowledge work and increasingly the way people interact with computers at all.
Programmer.ie follows that transition by trying to understand the machinery beneath the claims: what actually works, why it works, what the evidence supports, and how the idea can be used in practice.
The format can change. The method should not.
Separate names from mechanisms. Identify the distinctions that have to be understood before the subject becomes clear.
Use code, notebooks, experiments and working systems where possible instead of relying on description alone.
Ask what a result actually establishes, what it does not establish, and what competing explanation remains.
Make the durable result usable as a diagnostic, tool, demo, system or book-backed application path.
Start from the depth you need, then move between explanation and application.
Go to the solution library if you have a concrete problem, or open a book when you want the full mechanism behind it.