<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Haskell on paedubucher.ch</title><link>https://www.paedubucher.ch/tags/haskell/</link><description>Recent content in Haskell on paedubucher.ch</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 26 Apr 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://www.paedubucher.ch/tags/haskell/index.xml" rel="self" type="application/rss+xml"/><item><title>Soccer Table in Haskell: Problem and Setup</title><link>https://www.paedubucher.ch/articles/haskell-soccer-table-1-problem-setup/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0200</pubDate><guid>https://www.paedubucher.ch/articles/haskell-soccer-table-1-problem-setup/</guid><description>&lt;p&gt;I have been looking into the &lt;em&gt;Haskell&lt;/em&gt; programming language time and again since 2020. However, I never managed to write a complete non-trivial program in Haskell using proper software engineering techniques, e.g. using a proper build tool and writing unit tests. When I have been learning Haskell, I was mostly dealing with functional techniques and the type system.&lt;/p&gt;
&lt;p&gt;Whereas the &lt;em&gt;Hello, World!&lt;/em&gt; program is the first one you write when learning any other programming language, in Haskell you have to be more patient. Input and output involve &lt;em&gt;effects&lt;/em&gt;, and &lt;em&gt;effectful programming&lt;/em&gt; is strongly separated from the &lt;em&gt;pure&lt;/em&gt; code in Haskell. However, a real-world program uses both.&lt;/p&gt;</description></item></channel></rss>