<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Templates on The Negation</title><link>https://www.thenegation.com/tags/templates/</link><description>Recent content in Templates on The Negation</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 May 2025 19:11:06 +0000</lastBuildDate><atom:link href="https://www.thenegation.com/tags/templates/index.xml" rel="self" type="application/rss+xml"/><item><title>Nix-Powered Python Development</title><link>https://www.thenegation.com/posts/nix-powered-python-dev/</link><pubDate>Wed, 07 May 2025 19:11:06 +0000</pubDate><guid>https://www.thenegation.com/posts/nix-powered-python-dev/</guid><description>&lt;p&gt;After a few years of floating from one hack to another, this is my practical
guide to setting up a reasonable Python development environment using Nix flakes
with support for testing, linting, formatting, and LSP-based editor integration.&lt;/p&gt;</description></item><item><title>Nix Flake Templates</title><link>https://www.thenegation.com/posts/nix-flake-templates/</link><pubDate>Tue, 06 May 2025 11:36:39 +0000</pubDate><guid>https://www.thenegation.com/posts/nix-flake-templates/</guid><description>&lt;p&gt;Nix is now central to how I structure my workstation setups and manage
development and production environments across my projects. Over time, I found
myself repeating certain setups. This post is a short note on how I started
working with Nix Flake templates to avoid or reduce this repetition.&lt;/p&gt;</description></item></channel></rss>