<?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>Tutorials on Dave Hogan</title>
    <link>https://davehogan.co.uk/tags/tutorials/</link>
    <description>Recent content in Tutorials on Dave Hogan</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 24 Jan 2025 20:55:21 +0100</lastBuildDate>
    <atom:link href="https://davehogan.co.uk/tags/tutorials/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reflecting on the need for Abstracting DateTime.Now</title>
      <link>https://davehogan.co.uk/posts/development/reflecting-on-the-need-for-abstracting-datetime-now/</link>
      <pubDate>Fri, 24 Jan 2025 20:55:21 +0100</pubDate>
      <guid>https://davehogan.co.uk/posts/development/reflecting-on-the-need-for-abstracting-datetime-now/</guid>
      <description>&lt;h2 id=&#34;unit-testing-newbie&#34;&gt;Unit Testing Newbie&lt;/h2&gt;
&lt;p&gt;When I first started taking unit testing more seriously (it was 13+ years ago, don&amp;rsquo;t fight me!) I didn&amp;rsquo;t understand how to test something when I was using &lt;code&gt;DateTime.UtcNow&lt;/code&gt;. My tests worked then failed a while later.&lt;/p&gt;
&lt;p&gt;I asked, on reflection, an embarrassing question on &lt;a href=&#34;https://stackoverflow.com/questions/7661953/how-to-write-unit-test-for-time-sensitive-constant&#34;&gt;Stack Overflow&lt;/a&gt;. What made it embarrassing was that it showed my lack of understanding of non-deterministic values and testing code that used them. As I mentioned in this case it was usage of &lt;code&gt;DateTime&lt;/code&gt; in &lt;code&gt;C#&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Rewriting Entire Git Branch into a Single Commit</title>
      <link>https://davehogan.co.uk/posts/development/rewriting-entire-git-repo-into-single-commit/</link>
      <pubDate>Wed, 21 Aug 2024 23:44:22 +0100</pubDate>
      <guid>https://davehogan.co.uk/posts/development/rewriting-entire-git-repo-into-single-commit/</guid>
      <description>&lt;h2 id=&#34;squishing-everything-back-to-a-single-commit-in-git&#34;&gt;Squishing Everything Back to a Single Commit in Git&lt;/h2&gt;
&lt;p&gt;Ever wanted your Git history to go back to the initial commit while preserving the content you have today? For example, maybe you&amp;rsquo;re making a private repository public and want to remove the commit history but keep the current state. While a better option might be to create a new repository and commit everything fresh, if you really need to do this, here are the steps I took recently.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Gitflow Branching Strategy</title>
      <link>https://davehogan.co.uk/posts/development/gitflow-branching-strategy/</link>
      <pubDate>Thu, 15 Aug 2024 16:41:46 +0100</pubDate>
      <guid>https://davehogan.co.uk/posts/development/gitflow-branching-strategy/</guid>
      <description>&lt;p&gt;&lt;em&gt;This post was taken from a rough &lt;a href=&#34;https://gist.githubusercontent.com/DaveHogan/77052a4bcd902d4242d5ccf86daa1ddd/&#34;&gt;gist&lt;/a&gt; I created whilst strategising a GitFlow branching strategy in a new team setting. Views may have likely changed since then and no on-size fits all.&lt;/em&gt;&lt;/p&gt;
&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;p&gt;However you and your team manages branches; it&amp;rsquo;s important to have at least some kind of strategy that everyone adheres to. Rules and process should be designed to keep things consistent within the team and changes flowing to avoid complex merges and other such issues with multiple work steams on a single code repository.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bundling and Minification in ASP.NET Web Pages</title>
      <link>https://davehogan.co.uk/posts/development/bundling-and-minification/</link>
      <pubDate>Thu, 15 Aug 2024 13:07:57 +0100</pubDate>
      <guid>https://davehogan.co.uk/posts/development/bundling-and-minification/</guid>
      <description>&lt;p&gt;&lt;em&gt;This post was taken from a rough &lt;a href=&#34;https://gist.github.com/DaveHogan/ab74b72593c7cdd62ee8ce87c042641f&#34;&gt;gist&lt;/a&gt; I created whilst battling bundling and minification back in Nov &amp;lsquo;23. Things have likely changed since then.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;what-is-it&#34;&gt;What is it?&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Bundling and minification are optimisation techniques used to improve the performance of web applications.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Mainly by reducing the number of HTTP requests and decreasing the overall payload transmitted over the wite. We would typically do this for as many of our site-wide CSS and JavaScript files.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
