<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Api Design on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/api-design/</link>
    <description>Recent content in Api Design on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 14 Nov 2019 18:09:19 -0800</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/api-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Library Design Gotchas: Configuration loading</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2019/library-design-gotchas-configuration/</link>
      <pubDate>Thu, 14 Nov 2019 18:09:19 -0800</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2019/library-design-gotchas-configuration/</guid>
      <description>A friend was complaining about this library they were trying to use that was failing to load a configuration from a file. The resulting dive into the code inspired this post about inappropriate choices made when designing how a library is configured.&#xA;It isn&amp;rsquo;t my intention to pick on pyart. I appreciate the hard work the developers did to create it and open source it. It is just the example at hand.</description>
    </item>
  </channel>
</rss>
