<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sql on ilikeorangutans</title><link>https://kuelzer.ca/tags/sql/</link><description>Recent content in Sql on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 02 Aug 2026 23:30:10 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/sql/index.xml" rel="self" type="application/rss+xml"/><item><title>Code Generation in Go as an Accelerator</title><link>https://kuelzer.ca/posts/2026/08/02/code-generation-in-go-as-an-accelerator/</link><pubDate>Sun, 02 Aug 2026 22:05:05 -0400</pubDate><guid>https://kuelzer.ca/posts/2026/08/02/code-generation-in-go-as-an-accelerator/</guid><description>&lt;p&gt;So recently, against my best judgement, I&amp;rsquo;ve started working on a new project. The classic &amp;ldquo;&lt;em&gt;how hard can it be?&lt;/em&gt;&amp;rdquo; kind of thing. What that actually is is not important right now. More important are the tech choices and how I shifted my opinion on generated code.&lt;/p&gt;
&lt;p&gt;The tech stack I went with is what I usually pick; go for backend, pgx and sqlc for database access, htmx for frontend matters. I found managing Go&amp;rsquo;s template/html always a bit fiddly and wanted a better way of dealing with nested components and being able to render them individually. I have seen templ recommended many times and because it was a new project, I gave it a try. Initially I felt having yet another tool that generates go was weird, but after a few components I was sold.&lt;/p&gt;</description></item></channel></rss>