<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Technical debt metaphors get it so wrong	</title>
	<atom:link href="https://www.robg3d.com/2015/01/technical-debt-metaphors-get-it-so-wrong/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.robg3d.com/2015/01/technical-debt-metaphors-get-it-so-wrong/</link>
	<description>Blog of Rob Galanakis (@robgalanakis)</description>
	<lastBuildDate>Thu, 12 Feb 2015 14:39:04 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.4.2</generator>
	<item>
		<title>
		By: Managing Technical Debt Webinar		</title>
		<link>https://www.robg3d.com/2015/01/technical-debt-metaphors-get-it-so-wrong/#comment-236776</link>

		<dc:creator><![CDATA[Managing Technical Debt Webinar]]></dc:creator>
		<pubDate>Thu, 12 Feb 2015 14:39:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=1783#comment-236776</guid>

					<description><![CDATA[[&#8230;] 50 minute webinar explains what technical debt is and how to manage [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] 50 minute webinar explains what technical debt is and how to manage [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rob Galanakis		</title>
		<link>https://www.robg3d.com/2015/01/technical-debt-metaphors-get-it-so-wrong/#comment-236360</link>

		<dc:creator><![CDATA[Rob Galanakis]]></dc:creator>
		<pubDate>Mon, 26 Jan 2015 16:46:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=1783#comment-236360</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.robg3d.com/2015/01/technical-debt-metaphors-get-it-so-wrong/#comment-236278&quot;&gt;Viktoras Makauskas&lt;/a&gt;.

So I just discovered that, on OSX:
- alt+space to open Spotlight accidentally
- escape to close it
- Your WP comment closes (in admin view at least) and it&#039;s all erased...

I will respond another time, but the gist of it is, your solution there is minor and common and likely what you would have done even without client pressure (would you really want to upgrade an old app)? Everyone does this sort of thing, especially in JS.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.robg3d.com/2015/01/technical-debt-metaphors-get-it-so-wrong/#comment-236278">Viktoras Makauskas</a>.</p>
<p>So I just discovered that, on OSX:<br />
&#8211; alt+space to open Spotlight accidentally<br />
&#8211; escape to close it<br />
&#8211; Your WP comment closes (in admin view at least) and it&#8217;s all erased&#8230;</p>
<p>I will respond another time, but the gist of it is, your solution there is minor and common and likely what you would have done even without client pressure (would you really want to upgrade an old app)? Everyone does this sort of thing, especially in JS.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jse M		</title>
		<link>https://www.robg3d.com/2015/01/technical-debt-metaphors-get-it-so-wrong/#comment-236294</link>

		<dc:creator><![CDATA[Jse M]]></dc:creator>
		<pubDate>Thu, 22 Jan 2015 20:34:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=1783#comment-236294</guid>

					<description><![CDATA[&quot;But what about situations where client only had time/budget for the strap, and are happy because we found a quick solution that works for their needs?&quot;

Your scenario assumes that the customer accepted the responsibility and will not come back to the mechanic if there is fault.

This does not happen for developers, it&#039;s always their fault, it always comes back, they always have to fix it. Under the later assumption (the one I just made), the mechanic should apply a solution he can live with, because he knows the customer will come back with the same issue or a new issue caused by his work.]]></description>
			<content:encoded><![CDATA[<p>&#8220;But what about situations where client only had time/budget for the strap, and are happy because we found a quick solution that works for their needs?&#8221;</p>
<p>Your scenario assumes that the customer accepted the responsibility and will not come back to the mechanic if there is fault.</p>
<p>This does not happen for developers, it&#8217;s always their fault, it always comes back, they always have to fix it. Under the later assumption (the one I just made), the mechanic should apply a solution he can live with, because he knows the customer will come back with the same issue or a new issue caused by his work.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Viktoras Makauskas		</title>
		<link>https://www.robg3d.com/2015/01/technical-debt-metaphors-get-it-so-wrong/#comment-236278</link>

		<dc:creator><![CDATA[Viktoras Makauskas]]></dc:creator>
		<pubDate>Thu, 22 Jan 2015 07:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=1783#comment-236278</guid>

					<description><![CDATA[I guess you can twist the metaphor multiple ways, depending on which fighting side you are:)

Yeah, the tech debt primarily hurts developers. Yeah, it is unpleasant when client insists to &quot;strap the pipe&quot;, then comes back saying that the whole car caught on fire. But what about situations where client only had time/budget for the strap, and are happy because we found a quick solution that works for their needs?

Anyway, a real example. A defect comes in saying that a &quot;submit payment&quot; button of our older web apps does not work on a specific android version. We investigate and discover that the issue is in a third party JS library. The problem is fixed in it&#039;s later release, however, a few dependent libraries will also have to be upgraded in our app, probably not without changes to our own code. This means more dev and testing effort. As the client wanted a solution NOW, as it&#039;s impacting his business in a pretty straightforward way, a workaround was done to actually track down the relevant change in the 3rd party library (boiled down to few JS lines), patch the version we&#039;re using, and deploy. It was ugly but it worked. Yeah it was not pretty, but to team&#039;s decision, safest approach given the situation.]]></description>
			<content:encoded><![CDATA[<p>I guess you can twist the metaphor multiple ways, depending on which fighting side you are:)</p>
<p>Yeah, the tech debt primarily hurts developers. Yeah, it is unpleasant when client insists to &#8220;strap the pipe&#8221;, then comes back saying that the whole car caught on fire. But what about situations where client only had time/budget for the strap, and are happy because we found a quick solution that works for their needs?</p>
<p>Anyway, a real example. A defect comes in saying that a &#8220;submit payment&#8221; button of our older web apps does not work on a specific android version. We investigate and discover that the issue is in a third party JS library. The problem is fixed in it&#8217;s later release, however, a few dependent libraries will also have to be upgraded in our app, probably not without changes to our own code. This means more dev and testing effort. As the client wanted a solution NOW, as it&#8217;s impacting his business in a pretty straightforward way, a workaround was done to actually track down the relevant change in the 3rd party library (boiled down to few JS lines), patch the version we&#8217;re using, and deploy. It was ugly but it worked. Yeah it was not pretty, but to team&#8217;s decision, safest approach given the situation.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
