<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Programming on The Negation</title><link>https://www.thenegation.com/tags/programming/</link><description>Recent content in Programming on The Negation</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 24 May 2025 23:43:58 +0000</lastBuildDate><atom:link href="https://www.thenegation.com/tags/programming/index.xml" rel="self" type="application/rss+xml"/><item><title>Data Definitions, Not Flowcharts</title><link>https://www.thenegation.com/posts/flowcharts-vs-tables/</link><pubDate>Sat, 24 May 2025 23:43:58 +0000</pubDate><guid>https://www.thenegation.com/posts/flowcharts-vs-tables/</guid><description>&lt;p&gt;Computer programs are best understood in terms of the data they consume, process
and produce. Flowcharts are useful for visualizing control flow, but not for
understanding complexity.&lt;/p&gt;</description></item><item><title>Choosing A Template Engine: The More Powerful Problem</title><link>https://www.thenegation.com/posts/choosing-template-engine/</link><pubDate>Sat, 17 May 2025 21:49:05 +0000</pubDate><guid>https://www.thenegation.com/posts/choosing-template-engine/</guid><description>&lt;p&gt;Continuing on the topic of template engines, I would like to share my thoughts
on the &lt;em&gt;power&lt;/em&gt; of template engines, and how it relates to the &lt;em&gt;power&lt;/em&gt; of
abstractions in programming.&lt;/p&gt;</description></item><item><title>Thinking in Templates</title><link>https://www.thenegation.com/posts/thinking-in-templates/</link><pubDate>Fri, 16 May 2025 22:30:13 +0000</pubDate><guid>https://www.thenegation.com/posts/thinking-in-templates/</guid><description>&lt;p&gt;I believe that there is value in thinking in templates when it comes to
programming. I will try to explore the concept of templating in general, how it
reveals important patterns in programming, and how it appears in the wild often
in the form of &lt;em&gt;template engines&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Code is Liability</title><link>https://www.thenegation.com/posts/code-is-liability/</link><pubDate>Tue, 13 May 2025 23:55:27 +0000</pubDate><guid>https://www.thenegation.com/posts/code-is-liability/</guid><description>&lt;p&gt;While programming, we often aim to avoid repetition. Repetition is boring, and
ironically, much of programming exists to automate boring tasks in the first
place. But repetition is just one symptom of a much deeper problem: Code itself
is a liability.&lt;/p&gt;</description></item></channel></rss>