<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Programming on Oscar&#39;s Notebook</title>
    <link>https://oscarchou.com/tags/programming/</link>
    <description>Recent content in Programming on Oscar&#39;s Notebook</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 07 Feb 2026 20:00:00 +1300</lastBuildDate><atom:link href="https://oscarchou.com/tags/programming/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>[Golang] Stop Returning `(nil, nil)` in Go: A Small API Design Choice That Prevents Big Bugs</title>
      <link>https://oscarchou.com/posts/golang/stop-return-nil-object-in-golang/</link>
      <pubDate>Sat, 07 Feb 2026 20:00:00 +1300</pubDate>
      
      <guid>https://oscarchou.com/posts/golang/stop-return-nil-object-in-golang/</guid>
      <description>In Go API design, returning `(nil, nil)` for a not found object may seem harmless, but it can lead to runtime crashes and broken expectations. This article discusses the pitfalls of this practice and offers solutions such as returning a predefined error or using an explicit existence flag. Improve your API design by adopting safer patterns for better maintainability.</description>
    </item>
    
  </channel>
</rss>
