<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Uncategorized on Michael Kent</title><link>https://michaelkent.me/category/uncategorized/</link><description>Recent content in Uncategorized on Michael Kent</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 Michael Kent</copyright><lastBuildDate>Sun, 19 Mar 2023 16:26:19 +0000</lastBuildDate><atom:link href="https://michaelkent.me/category/uncategorized/index.xml" rel="self" type="application/rss+xml"/><item><title>Steps To Figuring Out Performance Issues</title><link>https://michaelkent.me/steps-to-figuring-out-performance-issues/</link><pubDate>Sun, 19 Mar 2023 16:26:19 +0000</pubDate><guid>https://michaelkent.me/steps-to-figuring-out-performance-issues/</guid><description>&lt;p&gt;Programming performance issues can be a frustrating and time-consuming problem for developers. However, tracking down these issues is a crucial step in creating software. Here are some steps that developers can take to track down programming performance issues:&lt;/p&gt;
&lt;p&gt;The first thing to do is &lt;strong&gt;ALWAYS&lt;/strong&gt; hook up a profiler to your code, reproducing your issue, and measuring what is causing it. Performance issues are often not obvious and if you don’t profile you’ll waste a bunch of time speeding up things that don’t matter(or just hide the base issue).&lt;/p&gt;</description></item><item><title>YAGNI – You Ain’t Gonna Need It</title><link>https://michaelkent.me/yagni-you-aint-gonna-need-it/</link><pubDate>Fri, 07 Apr 2017 02:18:53 +0000</pubDate><guid>https://michaelkent.me/yagni-you-aint-gonna-need-it/</guid><description>&lt;p&gt;YAGNI and Agile&lt;/p&gt;
&lt;p&gt;One of the hardest things to do in software development is to respect “you ain’t gonna need it” and “keep it simple stupid”. Every time I go to implement a feature, I can think of 50 extra things I should do to make it ‘complete’ and exactly what I want. It is so helpful to hit things with an Agile and iterative frame of reference. Build an MVP(minimum viable product) and publish! Extra features can come later as they are actually needed.&lt;/p&gt;</description></item><item><title>Hello!</title><link>https://michaelkent.me/hello-world/</link><pubDate>Mon, 19 Jan 2015 17:49:06 +0000</pubDate><guid>https://michaelkent.me/hello-world/</guid><description>&lt;p&gt;First post!&lt;/p&gt;
&lt;div class="highlight-wrapper"&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-csharp" data-lang="csharp"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="kd"&gt;public&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;HelloWorld&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="kd"&gt;public&lt;/span&gt; &lt;span class="kd"&gt;static&lt;/span&gt; &lt;span class="k"&gt;void&lt;/span&gt; &lt;span class="n"&gt;Main&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="p"&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;System&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;Console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;WriteLine&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;Hello, World!&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;</description></item></channel></rss>