<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Dependency Injection - Tag - Nuno Sousa&#39;s Corner</title>
        <link>https://www.nunomtsousa.com/tags/dependency-injection/</link>
        <description>Dependency Injection - Tag - Nuno Sousa&#39;s Corner</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>nuno.mt.sousa@gmail.com (Nuno Sousa)</managingEditor>
            <webMaster>nuno.mt.sousa@gmail.com (Nuno Sousa)</webMaster><lastBuildDate>Sun, 14 Apr 2024 18:33:39 &#43;0000</lastBuildDate><atom:link href="https://www.nunomtsousa.com/tags/dependency-injection/" rel="self" type="application/rss+xml" /><item>
    <title>The Device Driver Abstraction</title>
    <link>https://www.nunomtsousa.com/posts/2024-04-14-devicedriverabstraction/</link>
    <pubDate>Sun, 14 Apr 2024 18:33:39 &#43;0000</pubDate>
    <author>nuno.mt.sousa@gmail.com (Nuno Sousa)</author>
    <guid>https://www.nunomtsousa.com/posts/2024-04-14-devicedriverabstraction/</guid>
    <description><![CDATA[<h2 id="how-a-simple-idea-changed-software-design-forever">How a simple idea changed software design forever</h2>
<p>It was the dawn of computers and software. Operating systems were being developed, and there were still no agreed-upon abstractions. Then came a simple abstraction: the device driver. The device driver enabled the development of software that was not locked to a specific hardware; it allowed developers to write code that worked with any hardware. This seemingly simple change made software development a lot simpler. It is something we take for granted today, but that we forget when we develop software. Why do we keep on forgetting this simple idea? In this article, I’ll explain what the driver abstraction is, how it came to be, and the problems it tried to solve. I will also show why we keep forgetting about it, and the costs we pay every day for not learning from our past.</p>]]></description>
</item>
</channel>
</rss>
