<?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/"
	>
<channel>
	<title>Comments on: The myth of "software engineering"</title>
	<atom:link href="http://thetarpit.org/2015/the-myth-of-software-engineering/feed" rel="self" type="application/rss+xml" />
	<link>http://thetarpit.org/2015/the-myth-of-software-engineering</link>
	<description>"Now I feel like I know less about what that blog is about than I did before."</description>
	<pubDate>Sat, 12 Sep 2026 13:46:15 +0000</pubDate>
	<generator>http://thetarpit.org</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: spyked</title>
		<link>http://thetarpit.org/2015/the-myth-of-software-engineering#comment-7799</link>
		<dc:creator>spyked</dc:creator>
		<pubDate>Mon, 07 Sep 2026 16:57:22 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2015/the-myth-of-software-engineering#comment-7799</guid>
		<description>&gt; Motivations for replacing make range from a desire to replace make's very Unix-philosophy inspired domain-specific language for describing build rules (Unix-philosophy in the sense that it often works by coincidence, but falls over if you do something exotic, like have filenames with spaces in, or have an environment variable with the “wrong” name),

By that definition of "Unix-philosophy inspired", the more naïve software engineer would be led to believe that every piece of software on this earth lies in the same category -- for example, did you ever try accessing a path containing the backslash character under Windows? That yielded some pretty lulzy results last time I tried.

So at the end of the day, whether "engineering" is a null concept or not is entirely besides the point. The point is rather, that attempting to specify things and matters exhaustively, especially of the "general-purpose" kind, is an exercise in madness. And since the sane approach is to work on partial specifications, at some point you'll necessarily run into a hole somewhere which will break your machine -- yes, this discussion can be extended to bridges or whatever have you, this is also besides the point.

So once you run into the proverbial hole, the cheapest approach is to work around it, which is how you get today's mess, and that's pretty much the whole story.</description>
		<content:encoded><![CDATA[<p>> Motivations for replacing make range from a desire to replace make's very Unix-philosophy inspired domain-specific language for describing build rules (Unix-philosophy in the sense that it often works by coincidence, but falls over if you do something exotic, like have filenames with spaces in, or have an environment variable with the “wrong” name),</p>
<p>By that definition of "Unix-philosophy inspired", the more naïve software engineer would be led to believe that every piece of software on this earth lies in the same category -- for example, did you ever try accessing a path containing the backslash character under Windows? That yielded some pretty lulzy results last time I tried.</p>
<p>So at the end of the day, whether "engineering" is a null concept or not is entirely besides the point. The point is rather, that attempting to specify things and matters exhaustively, especially of the "general-purpose" kind, is an exercise in madness. And since the sane approach is to work on partial specifications, at some point you'll necessarily run into a hole somewhere which will break your machine -- yes, this discussion can be extended to bridges or whatever have you, this is also besides the point.</p>
<p>So once you run into the proverbial hole, the cheapest approach is to work around it, which is how you get today's mess, and that's pretty much the whole story.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On open sores supply chainz &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2015/the-myth-of-software-engineering#comment-4073</link>
		<dc:creator>On open sores supply chainz &#171; The Tar Pit</dc:creator>
		<pubDate>Thu, 20 Apr 2023 18:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2015/the-myth-of-software-engineering#comment-4073</guid>
		<description>[...] trigger-happy development is a bad idea regardless of the code distribution model. Engineering, [...]</description>
		<content:encoded><![CDATA[<p>[...] trigger-happy development is a bad idea regardless of the code distribution model. Engineering, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spyked</title>
		<link>http://thetarpit.org/2015/the-myth-of-software-engineering#comment-3123</link>
		<dc:creator>spyked</dc:creator>
		<pubDate>Thu, 29 Sep 2022 17:53:29 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2015/the-myth-of-software-engineering#comment-3123</guid>
		<description>Meh. I'll readily admit (as I've in fact &lt;a href="http://thetarpit.org/2020/on-the-hellpits-of-abstraction#comment-313" rel="nofollow"&gt;done before&lt;/a&gt;, to little effect) there's very little sense to be made here, since indeed, there's nothing to be found on the basis of Wikipedia. The &lt;a href="http://thetarpit.org/2016/the-myth-of-software-engineering-ii" rel="nofollow"&gt;following&lt;/a&gt; &lt;a href="http://thetarpit.org/2016/the-myth-of-software-engineering-iii" rel="nofollow"&gt;pieces&lt;/a&gt; also have very little to offer, unfortunately, since they're no replacement for the raw experience one requires with the subject matter, an experience which can indeed be put into words, although I have my doubts anyone except myself could understand the words were I to write them down.

Let it be known that I don't think much of the so-called rebuke either (and yes, you can attribute that to "dunning-kruger" or whatever, for all I care), but on that I shall not speak further, for its author is dead as far as I know.

Who knows, maybe I'll sit down and do a full rewrite sometime.</description>
		<content:encoded><![CDATA[<p>Meh. I'll readily admit (as I've in fact <a href="http://thetarpit.org/2020/on-the-hellpits-of-abstraction#comment-313" rel="nofollow">done before</a>, to little effect) there's very little sense to be made here, since indeed, there's nothing to be found on the basis of Wikipedia. The <a href="http://thetarpit.org/2016/the-myth-of-software-engineering-ii" rel="nofollow">following</a> <a href="http://thetarpit.org/2016/the-myth-of-software-engineering-iii" rel="nofollow">pieces</a> also have very little to offer, unfortunately, since they're no replacement for the raw experience one requires with the subject matter, an experience which can indeed be put into words, although I have my doubts anyone except myself could understand the words were I to write them down.</p>
<p>Let it be known that I don't think much of the so-called rebuke either (and yes, you can attribute that to "dunning-kruger" or whatever, for all I care), but on that I shall not speak further, for its author is dead as far as I know.</p>
<p>Who knows, maybe I'll sit down and do a full rewrite sometime.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spyked</title>
		<link>http://thetarpit.org/2015/the-myth-of-software-engineering#comment-280</link>
		<dc:creator>spyked</dc:creator>
		<pubDate>Mon, 23 Mar 2020 15:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2015/the-myth-of-software-engineering#comment-280</guid>
		<description>Although the Trilema article "&lt;a href="http://trilema.com/2019/the-alleged-crisis-of-the-supposed-engineering-or-mistaken-identities-pantomiming-a-comedy-of-manners/" rel="nofollow"&gt;The alleged crisis of the supposed engineering, or mistaken identities pantomiming a comedy of manners.&lt;/a&gt;" mentions this one, for some reason my MP-WP did not see any pingbacks coming its way, thus leaving me with no other option but to mention the former explicitly.

My apologies to those interested for the long delay.</description>
		<content:encoded><![CDATA[<p>Although the Trilema article "<a href="http://trilema.com/2019/the-alleged-crisis-of-the-supposed-engineering-or-mistaken-identities-pantomiming-a-comedy-of-manners/" rel="nofollow">The alleged crisis of the supposed engineering, or mistaken identities pantomiming a comedy of manners.</a>" mentions this one, for some reason my MP-WP did not see any pingbacks coming its way, thus leaving me with no other option but to mention the former explicitly.</p>
<p>My apologies to those interested for the long delay.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: An early Lisp scriptlang prototype in Ada &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2015/the-myth-of-software-engineering#comment-74</link>
		<dc:creator>An early Lisp scriptlang prototype in Ada &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 11:36:12 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2015/the-myth-of-software-engineering#comment-74</guid>
		<description>[...] This document describes the result of my attempts at implementing a Lisp (more precisely a Scheme) scripting language in Ada. The effort spawned from numerous discussions in the logs1 and used a few important references2. In short, the goal is to have a Lisp interpreter that is a. small, easy to read, i.e. fits-in-head; and b. written in a sane language, sans pointers and other cockroaches inhabiting today's broken computing machines. [...]</description>
		<content:encoded><![CDATA[<p>[...] This document describes the result of my attempts at implementing a Lisp (more precisely a Scheme) scripting language in Ada. The effort spawned from numerous discussions in the logs1 and used a few important references2. In short, the goal is to have a Lisp interpreter that is a. small, easy to read, i.e. fits-in-head; and b. written in a sane language, sans pointers and other cockroaches inhabiting today's broken computing machines. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The generative model of computing &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2015/the-myth-of-software-engineering#comment-56</link>
		<dc:creator>The generative model of computing &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 11:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2015/the-myth-of-software-engineering#comment-56</guid>
		<description>[...] See "The myth of software engineering".&#160;&#8617; [...]</description>
		<content:encoded><![CDATA[<p>[...] See "The myth of software engineering".&#160;&#8617; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On the unambiguous usefulness of tools (in software and elsewhere) &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2015/the-myth-of-software-engineering#comment-45</link>
		<dc:creator>On the unambiguous usefulness of tools (in software and elsewhere) &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 10:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2015/the-myth-of-software-engineering#comment-45</guid>
		<description>[...] one of my previous essays I mentioned this rare property of software, of being "unambiguously [...]</description>
		<content:encoded><![CDATA[<p>[...] one of my previous essays I mentioned this rare property of software, of being "unambiguously [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
