<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Tools - Tag - In a past life…</title>
        <link>https://archive.jtimothyking.com/tags/tools/</link>
        <description>Tools - Tag - In a past life…</description>
        <generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 29 Apr 2020 17:15:38 &#43;0000</lastBuildDate><atom:link href="https://archive.jtimothyking.com/tags/tools/" rel="self" type="application/rss+xml" /><item>
    <title>Musings about Version Control (and other development tools)</title>
    <link>https://archive.jtimothyking.com/2020/04/29/musings-about-version-control-and-other-development-tools/</link>
    <pubDate>Wed, 29 Apr 2020 17:15:38 &#43;0000</pubDate>
    <author>J. Timothy King</author>
    <guid>https://archive.jtimothyking.com/2020/04/29/musings-about-version-control-and-other-development-tools/</guid>
    <description><![CDATA[<!-- wp:paragraph -->
<p>Today, I had a conversation with a small company that doesn't use version control.</p>
<!-- /wp:paragraph -->
<!-- wp:paragraph -->
<p>It's hard to remember what it was like before version control. I know I <em>did</em> get started in a world without it. When I started in embedded development, we didn't have version control. </p>
<!-- /wp:paragraph -->
<!-- wp:paragraph -->
<p>Before there was version control, I made versioned backups of my entire working directory.</p>
<!-- /wp:paragraph -->
<!-- wp:paragraph -->
<p>Yikes. Dark ages.</p>
<!-- /wp:paragraph -->
<!-- wp:more -->]]></description>
</item>
<item>
    <title>More Reasons to Avoid SourceSafe</title>
    <link>https://archive.jtimothyking.com/2009/01/02/more-reasons-to-avoid-sourcesafe/</link>
    <pubDate>Fri, 02 Jan 2009 22:23:15 &#43;0000</pubDate>
    <author>J. Timothy King</author>
    <guid>https://archive.jtimothyking.com/2009/01/02/more-reasons-to-avoid-sourcesafe/</guid>
    <description><![CDATA[<p>I&rsquo;m helping out with a project I used to work on, one in an organization that uses SourceSafe to manage its source code. Fortunately, this time, I don&rsquo;t have to deal with SourceSafe this time. All I have to do is to submit my diffs against a baseline, and someone else will have to deal with merging them into the repository.</p>
<p>On a more recent project, we&rsquo;ve been using <a href="http://git.or.cz/">git</a>. There&rsquo;s no comparison. It&rsquo;s pretty cool how git effortlessly handles situations that SourceSafe can&rsquo;t even fathom. (Another good alternative is svn, but using svnmerge on all branches.)</p>]]></description>
</item>
<item>
    <title>Top Eight Reasons to Abandon SourceSafe</title>
    <link>https://archive.jtimothyking.com/2006/08/09/top-eight-reasons-to-abandon-sourcesafe/</link>
    <pubDate>Wed, 09 Aug 2006 16:03:59 &#43;0000</pubDate>
    <author>J. Timothy King</author>
    <guid>https://archive.jtimothyking.com/2006/08/09/top-eight-reasons-to-abandon-sourcesafe/</guid>
    <description><![CDATA[<p>How many of us work in Microsoft shops? I&rsquo;m ashamed to admit that I do. When I took the job, I thought the benefits of working in a new domain with new technologies would outweigh the fact that I had to use Microsoft tools and program for Windows. Well, the benefits are real. The costs are also real. And one of these costs is SourceSafe.</p>
<p>The worst part about it is that there&rsquo;s no particularly good reason why we have to use SourceSafe.</p>]]></description>
</item>
<item>
    <title>When the Best Tool Isn&#39;t, and Why a Growing Team Doesn&#39;t Care</title>
    <link>https://archive.jtimothyking.com/2006/08/02/when-the-best-tool-isnt-and-why-a-growing-team-doesnt-care/</link>
    <pubDate>Wed, 02 Aug 2006 16:00:55 &#43;0000</pubDate>
    <author>J. Timothy King</author>
    <guid>https://archive.jtimothyking.com/2006/08/02/when-the-best-tool-isnt-and-why-a-growing-team-doesnt-care/</guid>
    <description><![CDATA[<p>Kathy Sierra excellent post on <a href="http://headrush.typepad.com/creating_passionate_users/2006/08/when_the_best_t.html">When the &ldquo;best tool for the job&rdquo;&hellip; isn&rsquo;t</a> misses an important point. It&rsquo;s not that she missed the point so much as she just didn&rsquo;t go into it. But I think it deserves going into.</p>
<p>Many software developers become very attached to their favorite programming languages, methodologies, practices, and so forth. Checking the link-backs for my post <a href="http://sd.jtimothyking.com/2006/07/11/twelve-benefits-of-writing-unit-tests-first/" title="Twelve Benefits of Writing Unit Tests First">&ldquo;Twelve Benefits of Writing Unit Tests First&rdquo;</a> demonstrates this. One commenter on another blog even said he saw no value in reading the whole post, since it was specious and had no redeeming value. I took great joy in that comment, because it means I must be doing something right to push someone&rsquo;s righteous buttons so accurately. Regardless, would test-first be the right tool for that programmer?</p>]]></description>
</item>
</channel>
</rss>
