fix: updated publichDate dailydevops/website@5ecb809

authors/martin/feed.rss

@@ -5,9 +5,20 @@
     <link>https://daily-devops.net/authors/martin/</link>
     <description>Recent content from Martin Stühmer on Daily DevOps &amp; .NET</description>
     <language>en-US</language>
-    <lastBuildDate>Fri, 22 Nov 2024 15:50:07 +0000</lastBuildDate>
+    <lastBuildDate>Fri, 22 Nov 2024 15:53:18 +0000</lastBuildDate>
     <atom:link type="application/rss+xml" href="https://daily-devops.net/authors/martin/feed.rss" hreflang="en-US" rel="self"/>
     <atom:link type="text/html" href="https://daily-devops.net/authors/martin/" hreflang="en-US" rel="alternate"/>
+    <item>
+      <guid isPermaLink="true">https://daily-devops.net/posts/tale-of-forgotten-pennies-and-lost-dollars/</guid>
+      <link>https://daily-devops.net/posts/tale-of-forgotten-pennies-and-lost-dollars/</link>
+      <title>A Tale of Forgotten Pennies and Lost Dollars</title>
+      <pubDate>Fri, 22 Nov 2024 16:45:00 +0100</pubDate>
+      <description>In software development, there’s a silent debt that accrues interest over time, often hidden beneath layers of code and decisions made in haste or ignorance. This debt is aptly termed technical debt. Much like the german proverb, “Wer den Pfennig nicht ehrt, ist den Taler nicht wert”, (or the english equivalent, “A penny saved is a penny earned”) technical debt reminds us that small oversights or compromises in the present can snowball into significant challenges down the road. This article critically examines the parallels between financial principles and technical debt, emphasizing the importance of addressing both direct and indirect debt while understanding its distinction from external risks such as hacking or abuse.
+</description>
+      <category>dependency-management</category>
+      <category>rcda</category>
+      <category>technicaldebt</category>
+    </item>
     <item>
       <guid isPermaLink="true">https://daily-devops.net/posts/dependamerge-action/</guid>
       <link>https://daily-devops.net/posts/dependamerge-action/</link>

feed.rss

@@ -5,14 +5,14 @@
     <link>https://daily-devops.net/</link>
     <description>Recent content on Daily DevOps &amp; .NET</description>
     <language>en-US</language>
-    <lastBuildDate>Fri, 22 Nov 2024 15:50:07 +0000</lastBuildDate>
+    <lastBuildDate>Fri, 22 Nov 2024 15:53:18 +0000</lastBuildDate>
     <atom:link type="application/rss+xml" href="https://daily-devops.net/feed.rss" hreflang="en-US" rel="self"/>
     <atom:link type="text/html" href="https://daily-devops.net/" hreflang="en-US" rel="alternate"/>
     <item>
       <guid isPermaLink="true">https://daily-devops.net/posts/tale-of-forgotten-pennies-and-lost-dollars/</guid>
       <link>https://daily-devops.net/posts/tale-of-forgotten-pennies-and-lost-dollars/</link>
       <title>A Tale of Forgotten Pennies and Lost Dollars</title>
-      <pubDate>Fri, 22 Nov 2024 14:00:00 +0100</pubDate>
+      <pubDate>Fri, 22 Nov 2024 16:45:00 +0100</pubDate>
       <description>In software development, there’s a silent debt that accrues interest over time, often hidden beneath layers of code and decisions made in haste or ignorance. This debt is aptly termed technical debt. Much like the german proverb, “Wer den Pfennig nicht ehrt, ist den Taler nicht wert”, (or the english equivalent, “A penny saved is a penny earned”) technical debt reminds us that small oversights or compromises in the present can snowball into significant challenges down the road. This article critically examines the parallels between financial principles and technical debt, emphasizing the importance of addressing both direct and indirect debt while understanding its distinction from external risks such as hacking or abuse.
 </description>
       <category>dependency-management</category>

posts/buildinginsidevisualstudio/index.html

@@ -39,7 +39,7 @@
 <a class="icon reddit" href="https://reddit.com/submit/?url=https%3a%2f%2fdaily-devops.net%2fposts%2fbuildinginsidevisualstudio%2f&resubmit=true&title=%26lt%3bp%26gt%3bIn%20the%20ever-evolving%20world%20of%20.NET%20development%2c%20managing%20project%20configurations%20effectively%20is%20crucial%20for%20maintaining%20a%20clean%20and%20efficient%20build%20process.%20%e2%80%a6" target="_blank" rel="noopener external" aria-label="Share on Reddit" title="Share on Reddit" target="_blank"><i class="fa-brands fa-fw fa-reddit-alien fa-2x"></i></a></section><section class="sidecar tags"><header><h1>Tags</h1></header><ul><li class="tag"><a href="/tags/dotnet/" hreflang="en" rel="tag" title=".NET"><i class="fas fa-tag"></i>&nbsp;.NET</a></li><li class="tag"><a href="/tags/csharp/" hreflang="en" rel="tag" title="C#"><i class="fas fa-tag"></i>&nbsp;C#</a></li><li class="tag"><a href="/tags/visualstudio/" hreflang="en" rel="tag" title="Visual Studio"><i class="fas fa-tag"></i>&nbsp;Visual Studio</a></li></ul></section><section class="sidecar links"><header><h1>Additional links</h1></header><a href="https://learn.microsoft.com/en-us/visualstudio/msbuild/visual-studio-integration-msbuild#build-solutions" title="Visual Studio integration (MSBuild) - Build solutions" target="_blank" rel="noopener external noreferrer"><i class="fas fa-angles-right"></i>&nbsp;
 Visual Studio integration (MSBuild) - Build solutions
 </a><a href="https://learn.microsoft.com/en-us/visualstudio/msbuild/build-process-overview#visual-studio-builds-vs-msbuildexe-builds" title="How MSBuild builds projects - Visual Studio builds vs. MSBuild.exe builds" target="_blank" rel="noopener external noreferrer"><i class="fas fa-angles-right"></i>&nbsp;
-How MSBuild builds projects - Visual Studio builds vs. MSBuild.exe builds</a></section><section class="sidecar related"><header><h1>Related content</h1></header><article class="post"><figure class="square"><picture><source srcset="/images/csharp-80x80.webp?v=7a55697aaf0677ae54a6785e810b1d12" type="image/webp"><source srcset="/images/csharp-80x80.png?v=4b0a1c9d72436262a5c4509e8b5cbd28" type="image/png"><img src="/images/csharp.png?v=21ff9dcf5d1da7bfa80141c972c117da" alt="Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#" title="Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#"></picture></figure><header><h2><a href="/posts/introducing-nullability-in-legacy-code/" rel="bookmark">Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#</a></h2></header><section class="content"><p>As developers, we’re often tasked with maintaining and modernizing legacy codebases that were written long before some of the best practices of today—such as nullability annotations—were available. While modern C# now supports nullable reference types, enabling us to avoid the dreaded <code>NullReferenceException</code>, introducing this feature to existing, large codebases can be a challenge.</p><p>In this article, I’ll share my step-by-step approach for introducing nullability into a legacy .NET and C# project. You’ll learn how to apply nullability in a controlled, incremental manner using project-level settings, scoped annotations, and file/method-level directives, all while maintaining the integrity of your legacy codebase. After all, modernizing your code doesn’t have to be an all-or-nothing endeavor—gradual change is key to a successful transition. Let’s get started!</p></section></article><article class="post"><figure class="square"><picture><source srcset="/images/package-manager-80x80.webp?v=997ad22a223dfbf875b9aefce45f77b8" type="image/webp"><source srcset="/images/package-manager-80x80.png?v=250e6f700a513be4194dcb9ae43beb00" type="image/png"><img src="/images/package-manager.png?v=19ac8eda9b0cc3394a0da24151d44079" alt="Manage Nuget Packages Centrally" title="Manage Nuget Packages Centrally"></picture></figure><header><h2><a href="/posts/manage-nuget-packages-centrally/" rel="bookmark">Manage Nuget Packages Centrally</a></h2></header><section class="content"><p>For over 12 years, NuGet package management has been part of the .NET ecosystem with direct integrations to various IDEs, CLIs and build systems. But a feature took 12 years before it appeared and certainly needs some more maintenance until it is mature!</p></section></article><article class="post"><figure class="square"><picture><source srcset="/images/technical-debt-80x80.webp?v=09573c9c0923ee75b4bc0dc043a765dd" type="image/webp"><source srcset="/images/technical-debt-80x80.png?v=826e53a10b2c75b7306e3bc80d372dd9" type="image/png"><img src="/images/technical-debt.png?v=a263065307ca20c6f0419772b79bdef3" alt="Master dependency management with automation: story behind `dependamerge`" title="Master dependency management with automation: story behind `dependamerge`"></picture></figure><header><h2><a href="/posts/dependamerge-action/" rel="bookmark">Master dependency management with automation: story behind `dependamerge`</a></h2></header><section class="content"><p>In software development, dependencies are inevitable - any project worth its salt relies on various libraries, frameworks, or packages. However, as I found in my own work, managing these dependencies can be an onerous task. Constant updates, new vulnerabilities, and endless manual approvals were draining my time and focus. What if, I thought, these processes could be automated? This thought led to the creation of <code>dependamerge</code>, a GitHub Action designed to free developers from the drudgery of manual dependency maintenance and let us get back to what we do best: building great software.</p></section></article></section></aside><nav class="pager"><a class="next" href="/posts/introducing-nullability-in-legacy-code/" title="Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#" rel="next"><span class="sub"><i class="fas fa-backward"></i>&emsp;Next</span><p class="title">Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#</p></a><a class="prev" href="/posts/reimagining-the-microsoft-certification-exam-ui/" title="Reimagining the Microsoft Certification Exam UI Experience" rel="prev"><span class="sub">Previous&emsp;<i class="fas fa-forward"></i></span><p class="title">Reimagining the Microsoft Certification Exam UI Experience</p></a></nav></main><footer class="footer"><div class="divider"></div><nav><ul class="navigation"><li><a href="/tags/">Tags</a></li></ul></nav><div class="copyright">&copy; 2023 - 2024 Daily DevOps & .NET</div></footer><script async defer src="/js/below.min.a6ce9164454b6077f17ae856f280442d9f3a1e21f06189f71c21f75144b22a0c8cf32bafd61d440e9d90ca02bf738b6a8ef19f5ec20285d8ca574f98c91ebaf2.js" integrity="sha512-ps6RZEVLYHfxeuhW8oBELZ86HiHwYYn3HCH3UUSyKgyM8yuv1h1EDp2QygK/c4tqjvGfXsIChdjKV0+YyR668g==" crossorigin="anonymous"></script><img class="vgwort" src="https://vg06.met.vgwort.de/na/946fa404ad144b49a13808439e7df426" width="1" height="1" alt="VG Wort" title="VG Wort">
+How MSBuild builds projects - Visual Studio builds vs. MSBuild.exe builds</a></section><section class="sidecar related"><header><h1>Related content</h1></header><article class="post"><figure class="square"><picture><source srcset="/images/csharp-80x80.webp?v=7a55697aaf0677ae54a6785e810b1d12" type="image/webp"><source srcset="/images/csharp-80x80.png?v=4b0a1c9d72436262a5c4509e8b5cbd28" type="image/png"><img src="/images/csharp.png?v=21ff9dcf5d1da7bfa80141c972c117da" alt="Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#" title="Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#"></picture></figure><header><h2><a href="/posts/introducing-nullability-in-legacy-code/" rel="bookmark">Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#</a></h2></header><section class="content"><p>As developers, we’re often tasked with maintaining and modernizing legacy codebases that were written long before some of the best practices of today—such as nullability annotations—were available. While modern C# now supports nullable reference types, enabling us to avoid the dreaded <code>NullReferenceException</code>, introducing this feature to existing, large codebases can be a challenge.</p><p>In this article, I’ll share my step-by-step approach for introducing nullability into a legacy .NET and C# project. You’ll learn how to apply nullability in a controlled, incremental manner using project-level settings, scoped annotations, and file/method-level directives, all while maintaining the integrity of your legacy codebase. After all, modernizing your code doesn’t have to be an all-or-nothing endeavor—gradual change is key to a successful transition. Let’s get started!</p></section></article><article class="post"><figure class="square"><picture><source srcset="/images/package-manager-80x80.webp?v=997ad22a223dfbf875b9aefce45f77b8" type="image/webp"><source srcset="/images/package-manager-80x80.png?v=250e6f700a513be4194dcb9ae43beb00" type="image/png"><img src="/images/package-manager.png?v=19ac8eda9b0cc3394a0da24151d44079" alt="Manage Nuget Packages Centrally" title="Manage Nuget Packages Centrally"></picture></figure><header><h2><a href="/posts/manage-nuget-packages-centrally/" rel="bookmark">Manage Nuget Packages Centrally</a></h2></header><section class="content"><p>For over 12 years, NuGet package management has been part of the .NET ecosystem with direct integrations to various IDEs, CLIs and build systems. But a feature took 12 years before it appeared and certainly needs some more maintenance until it is mature!</p></section></article><article class="post"><figure class="square"><picture><source srcset="/images/technical-debt-80x80.webp?v=09573c9c0923ee75b4bc0dc043a765dd" type="image/webp"><source srcset="/images/technical-debt-80x80.png?v=826e53a10b2c75b7306e3bc80d372dd9" type="image/png"><img src="/images/technical-debt.png?v=a263065307ca20c6f0419772b79bdef3" alt="A Tale of Forgotten Pennies and Lost Dollars" title="A Tale of Forgotten Pennies and Lost Dollars"></picture></figure><header><h2><a href="/posts/tale-of-forgotten-pennies-and-lost-dollars/" rel="bookmark">A Tale of Forgotten Pennies and Lost Dollars</a></h2></header><section class="content"><p>In software development, there’s a silent debt that accrues interest over time, often hidden beneath layers of code and decisions made in haste or ignorance. This debt is aptly termed <em>technical debt</em>. Much like the german proverb, <em>&ldquo;Wer den Pfennig nicht ehrt, ist den Taler nicht wert&rdquo;,</em> (or the english equivalent, <em>&ldquo;A penny saved is a penny earned&rdquo;</em>) technical debt reminds us that small oversights or compromises in the present can snowball into significant challenges down the road. This article critically examines the parallels between financial principles and technical debt, emphasizing the importance of addressing both direct and indirect debt while understanding its distinction from external risks such as hacking or abuse.</p></section></article></section></aside><nav class="pager"><a class="next" href="/posts/introducing-nullability-in-legacy-code/" title="Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#" rel="next"><span class="sub"><i class="fas fa-backward"></i>&emsp;Next</span><p class="title">Gradually Introducing Nullability in Legacy Code: A Practical Guide for .NET and C#</p></a><a class="prev" href="/posts/reimagining-the-microsoft-certification-exam-ui/" title="Reimagining the Microsoft Certification Exam UI Experience" rel="prev"><span class="sub">Previous&emsp;<i class="fas fa-forward"></i></span><p class="title">Reimagining the Microsoft Certification Exam UI Experience</p></a></nav></main><footer class="footer"><div class="divider"></div><nav><ul class="navigation"><li><a href="/tags/">Tags</a></li></ul></nav><div class="copyright">&copy; 2023 - 2024 Daily DevOps & .NET</div></footer><script async defer src="/js/below.min.a6ce9164454b6077f17ae856f280442d9f3a1e21f06189f71c21f75144b22a0c8cf32bafd61d440e9d90ca02bf738b6a8ef19f5ec20285d8ca574f98c91ebaf2.js" integrity="sha512-ps6RZEVLYHfxeuhW8oBELZ86HiHwYYn3HCH3UUSyKgyM8yuv1h1EDp2QygK/c4tqjvGfXsIChdjKV0+YyR668g==" crossorigin="anonymous"></script><img class="vgwort" src="https://vg06.met.vgwort.de/na/946fa404ad144b49a13808439e7df426" width="1" height="1" alt="VG Wort" title="VG Wort">
 <script type="text/javascript">!function(e,t,n){var s,o=e.location,f="script",m="instrumentationKey",a="ingestionendpoint",d="disableExceptionTracking",l="ai.device.",c="toLowerCase",r="crossOrigin",u="POST",h="appInsightsSDK",i=n.name||"appInsights";(n.name||e[h])&&(e[h]=i),s=e[i]||function(s){var p,g,v,j,C,k=!1,b=!1,i={initialize:!0,queue:[],sv:"5",version:2,config:s};function y(e,t){var n={},s="Browser";return n[l+"id"]=s[c](),n[l+"type"]=s,n["ai.operation.name"]=o&&o.pathname||"_unknown_",n["ai.internal.sdkVersion"]="javascript:snippet_"+(i.sv||i.version),{time:function(){var e=new Date;function t(e){var t=""+e;return 1===t.length&&(t="0"+t),t}return e.getUTCFullYear()+"-"+t(1+e.getUTCMonth())+"-"+t(e.getUTCDate())+"T"+t(e.getUTCHours())+":"+t(e.getUTCMinutes())+":"+t(e.getUTCSeconds())+"."+((e.getUTCMilliseconds()/1e3).toFixed(3)+"").slice(2,5)+"Z"}(),iKey:e,name:"Microsoft.ApplicationInsights."+e.replace(/-/g,"")+"."+t,sampleRate:100,tags:n,data:{baseData:{ver:2}}}}if(g=s.url||n.src,g){function E(){var r,l,d,h,f,p,v,j,_,w,O;k=!0,i.queue=[],b||(b=!0,l=g,h=function(){var t,n,o,i,r,e={},l=s.connectionString;if(l)for(o=l.split(";"),t=0;t<o.length;t++)n=o[t].split("="),2===n.length&&(e[n[0][c]()]=n[1]);return e[a]||(i=e.endpointsuffix,r=i?e.location:null,e[a]="https://"+(r?r+".":"")+"dc."+(i||"services.visualstudio.com")),e}(),f=h[m]||s[m]||"",p=h[a],r=p?p+"/v2/track":s.endpointUrl,(v=[]).push((d="SDK LOAD Failure: Failed to load Application Insights SDK script (See stack for details)",j=l,_=r,(O=(w=y(f,"Exception")).data).baseType="ExceptionData",O.baseData.exceptions=[{typeName:"SDKLoadFailed",message:d.replace(/\./g,"-"),hasFullStack:!1,stack:d+`
 Snippet failed to load [`+j+`] -- Telemetry is disabled
 Help Link: https://go.microsoft.com/fwlink/?linkid=2128109