<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Economics on Bifurcations</title><link>https://bifurcations.org/en/tags/economics/</link><description>Recent content in Economics on Bifurcations</description><generator>Hugo</generator><language>en-CA</language><lastBuildDate>Sat, 03 Oct 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://bifurcations.org/en/tags/economics/index.xml" rel="self" type="application/rss+xml"/><item><title>The Expensive Intelligence Bubble</title><link>https://bifurcations.org/en/texts/the-expensive-intelligence-bubble/</link><pubDate>Fri, 02 Oct 2026 00:00:00 -0400</pubDate><guid>https://bifurcations.org/en/texts/the-expensive-intelligence-bubble/</guid><description>&lt;p&gt;&lt;em&gt;Revision, October 3, 2026 — This essay has been shortened and reorganized to remove repetition and tangential passages. Its central argument is unchanged.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I am currently developing Équilibre, an accounting application that has become much more ambitious than I initially expected.&lt;/p&gt;
&lt;p&gt;Its core must keep accounting entries consistent, preserve their history and allow corrections without destroying the audit trail. An architectural error can remain invisible for a long time: the software runs, the numbers look plausible, but something is wrong.&lt;/p&gt;</description></item></channel></rss>