<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Software-Design on nyadgar.com</title>
		<link>https://nyadgar.com/tags/software-design/</link>
		<description>Recent content in Software-Design on nyadgar.com</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 12 Jan 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://nyadgar.com/tags/software-design/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Go Interfaces: Why, How and When</title>
				<link>https://nyadgar.com/posts/go-interfaces-why-how-and-when/</link>
				<pubDate>Sun, 12 Jan 2025 00:00:00 +0000</pubDate>
				<guid>https://nyadgar.com/posts/go-interfaces-why-how-and-when/</guid>
				<description>&lt;p&gt;In programming, interfaces are a powerful concept that lets us express&#xA;our code more abstractly. Interfaces allow us to reason about the&#xA;higher-level logic of our processes without getting down to the small details.&#xA;Go has arguably one of the best interface implementations. With great features&#xA;like implicit implementations, assertion, and more.&lt;/p&gt;&#xA;&lt;p&gt;Interfaces must be used cautiously since they introduce more abstraction to our code,&#xA;making it susceptible to unnecessary wrappers, misuse of definitions, and sometimes,&#xA;even memory issues. In this article, I will discuss cases where interfaces can positively impact your code.&#xA;But first, let&amp;rsquo;s talk about what an interface is not.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
