<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Flask on code.kiwi.com</title><link>https://code.kiwi.com/tag/flask/</link><description>Recent content in Flask on code.kiwi.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Mar 2023 11:44:03 +0000</lastBuildDate><atom:link href="https://code.kiwi.com/tag/flask/index.xml" rel="self" type="application/rss+xml"/><item><title>Testable code: making the (testing) world better</title><link>https://code.kiwi.com/articles/testable-code-making-the-testing-world-better/</link><pubDate>Thu, 23 Aug 2018 11:34:00 +0000</pubDate><guid>https://code.kiwi.com/articles/testable-code-making-the-testing-world-better/</guid><description>&lt;h2 id="testable-code-making-the-testing-world-better"&gt;Testable code: making the (testing) world better&lt;/h2&gt;&lt;p&gt;What does it mean to have testable code? In general, it means, that the code is easy to test and it’s easy to set up a testing environment. Sometimes it’s tough to make code testable, especially in a large, legacy codebase, but I’d like to tell you some approaches and tips, that could help you make your code more maintainable, understandable, and reliable.&lt;/p&gt;</description></item></channel></rss>