<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ray Tracer on ilikeorangutans</title><link>https://kuelzer.ca/tags/ray-tracer/</link><description>Recent content in Ray Tracer on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 12 Apr 2026 14:27:24 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/ray-tracer/index.xml" rel="self" type="application/rss+xml"/><item><title>Book Arrival: The Ray Tracer Challenge</title><link>https://kuelzer.ca/posts/2019/03/24/book-arrival-the-ray-tracer-challenge/</link><pubDate>Sun, 24 Mar 2019 09:58:18 -0400</pubDate><guid>https://kuelzer.ca/posts/2019/03/24/book-arrival-the-ray-tracer-challenge/</guid><description>&lt;p&gt;I was browsing the Pragmatic Bookshelf and this book caught my eye: &lt;a href="https://pragprog.com/book/jbtracer/the-ray-tracer-challenge"&gt;writing a ray tracer from ground up with a test
driven approach&lt;/a&gt;? This sounds like a fantastic challenge
to me. I always was interested in ray tracers but always
thought it too complicated a topic to do it myself. However, test driven development has helped me work on some
complex and terrible code bases, so this feels reassuring to me.&lt;/p&gt;</description></item></channel></rss>