<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tutorial on Rok Garbas</title><link>https://garbas.si/tags/tutorial/</link><description>Recent content in Tutorial on Rok Garbas</description><generator>Hugo</generator><language>en-us</language><copyright>© Rok Garbas</copyright><lastBuildDate>Fri, 13 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://garbas.si/tags/tutorial/feeds/all.rss.xml" rel="self" type="application/rss+xml"/><item><title>Learn the Nix Language in 15 Minutes</title><link>https://garbas.si/posts/learn-nix-language/</link><pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate><guid>https://garbas.si/posts/learn-nix-language/</guid><description>&lt;p&gt;I keep watching people copy-paste NixOS configurations without understanding them. They grab a snippet from someone&amp;rsquo;s dotfiles, tweak it until it works, and move on. Then something breaks and they&amp;rsquo;re stuck because they don&amp;rsquo;t know what &lt;code&gt;inherit&lt;/code&gt; does, why &lt;code&gt;rec&lt;/code&gt; exists, or how functions with curly braces differ from functions with a colon. The fix: learn the language. Not nixpkgs, not the ecosystem. Just the language. About 15 minutes.&lt;/p&gt;
&lt;p&gt;This post covers only Nix syntax and constructs. After reading it, &lt;code&gt;.nix&lt;/code&gt; files should stop looking like alien hieroglyphs. What about nixpkgs, the module system, all those helper functions in &lt;code&gt;lib&lt;/code&gt;? Different topic. Later posts.&lt;/p&gt;</description></item></channel></rss>