<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Food_for_thought on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/food_for_thought/</link><description>Recent content in Food_for_thought on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 25 Feb 2018 18:56:00 +0000</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/food_for_thought/index.xml" rel="self" type="application/rss+xml"/><item><title>Testable modules</title><link>https://blog.sodawa.com/blog/testable_modules/</link><pubDate>Sun, 25 Feb 2018 18:56:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/testable_modules/</guid><description>We should write our code in a Test Driven style. I agree. Yet I find myself working on small side projects quite frequently, where I just want to hack something and make it work.
Now, lets say I actually want to keep growing my codebase, but it is all untested
I could easily look at every file, mirror it into a test directory and then write my tests there, while switching between files constantly.</description></item></channel></rss>