<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Assessing the cognitive consequences of the object-oriented approach: a survey of empirical research on object-oriented design by individuals and teams · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/cs_0611154/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/cs_0611154/feed.xml" rel="self" type="application/rss+xml" /><item><title>Assessing the cognitive consequences of the object-oriented approach: a survey of empirical research on object-oriented design by individuals and teams — mentioned by chriswarbo</title><link>https://news.ycombinator.com/item?id=8339858</link><guid isPermaLink="false">urn:hackerpapers:mention:cs_0611154:8339858</guid><pubDate>Fri, 19 Sep 2014 11:10:12 GMT</pubDate><description>&lt;p&gt;&amp;gt; The big advantage of OO is that it acts as a distillation of how humans think. Citation needed. Browsing around Google Scholar for variations of &amp;quot;object oriented empirical comparison&amp;quot; shows a huge body of research comparing various OO approaches to each other, but very few comparing OO approaches to anything else. Those which I have been able to find compare OO to procedural code, and find either no significant difference in comprehension levels, or that procedural code is easier to understand (ie. closer to &amp;quot;how humans think&amp;quot;) than OO: An empirical study of novice program comprehension in…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/cs_0611154/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.HC</category></item></channel></rss>
