<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TDD on ilikeorangutans</title><link>https://kuelzer.ca/tags/tdd/</link><description>Recent content in TDD 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/tdd/index.xml" rel="self" type="application/rss+xml"/><item><title>Notes on Working Effectively With Legacy Code</title><link>https://kuelzer.ca/posts/2018/07/02/notes-on-working-effectively-with-legacy-code/</link><pubDate>Mon, 02 Jul 2018 12:02:03 -0400</pubDate><guid>https://kuelzer.ca/posts/2018/07/02/notes-on-working-effectively-with-legacy-code/</guid><description>&lt;p&gt;I &lt;a href="https://kuelzer.ca/posts/2018/06/18/book-arrival-working-effectivly-with-legacy-code/"&gt;recently received&lt;/a&gt; my copy
of &lt;a href="https://www.goodreads.com/book/show/44919.Working_Effectively_with_Legacy_Code"&gt;Working Effectivly With Legacy Code&lt;/a&gt;
and have been busy reading it. The book, as a product of its time, has examples of not only Java, but also C++, probably
to show concepts and techniques that apply to languages that behave differently in terms of linking and building. But
regardless of its examples not really applying to what I work with, it was full of useful vocabulary and techniques to
work with not only legacy systems, but really, any kind of system.&lt;/p&gt;</description></item></channel></rss>