<?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: Understanding Table R507.5 from the International Residential Code (IRC): Choosing the Right Deck Beam Size Made Simple	</title>
	<atom:link href="https://kiltedbuilders.com/2025/01/29/understanding-table-r507-5-from-the-2018-international-residential-code-irc-choosing-the-right-deck-beam-size-made-simple/feed/" rel="self" type="application/rss+xml" />
	<link>https://kiltedbuilders.com/2025/01/29/understanding-table-r507-5-from-the-2018-international-residential-code-irc-choosing-the-right-deck-beam-size-made-simple/</link>
	<description>Trust in Tradition, Built for a Lifetime of Memories</description>
	<lastBuildDate>Sat, 09 May 2026 22:00:12 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Justin		</title>
		<link>https://kiltedbuilders.com/2025/01/29/understanding-table-r507-5-from-the-2018-international-residential-code-irc-choosing-the-right-deck-beam-size-made-simple/#comment-39</link>

		<dc:creator><![CDATA[Justin]]></dc:creator>
		<pubDate>Sat, 09 May 2026 22:00:12 +0000</pubDate>
		<guid isPermaLink="false">https://kiltedbuilder.com/?p=1559#comment-39</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://kiltedbuilders.com/2025/01/29/understanding-table-r507-5-from-the-2018-international-residential-code-irc-choosing-the-right-deck-beam-size-made-simple/#comment-38&quot;&gt;Richard Lesenski&lt;/a&gt;.

Hi Rich — good question. For a built-up beam like that, splices should land over posts so each ply has full bearing. Be sure your sizing and spans are based on total design load (live + dead), not just live load. Always worth confirming with your local code requirements and code enforcement for your specific build.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://kiltedbuilders.com/2025/01/29/understanding-table-r507-5-from-the-2018-international-residential-code-irc-choosing-the-right-deck-beam-size-made-simple/#comment-38">Richard Lesenski</a>.</p>
<p>Hi Rich — good question. For a built-up beam like that, splices should land over posts so each ply has full bearing. Be sure your sizing and spans are based on total design load (live + dead), not just live load. Always worth confirming with your local code requirements and code enforcement for your specific build.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Richard Lesenski		</title>
		<link>https://kiltedbuilders.com/2025/01/29/understanding-table-r507-5-from-the-2018-international-residential-code-irc-choosing-the-right-deck-beam-size-made-simple/#comment-38</link>

		<dc:creator><![CDATA[Richard Lesenski]]></dc:creator>
		<pubDate>Sat, 09 May 2026 20:36:53 +0000</pubDate>
		<guid isPermaLink="false">https://kiltedbuilder.com/?p=1559#comment-38</guid>

					<description><![CDATA[I want to build a 27’ 2 ply deck beam with 2x10’s. All butt joints will be offset from one another however do these butt joints need to be over the pillars?  Thanks]]></description>
			<content:encoded><![CDATA[<p>I want to build a 27’ 2 ply deck beam with 2&#215;10’s. All butt joints will be offset from one another however do these butt joints need to be over the pillars?  Thanks</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Khloe4379		</title>
		<link>https://kiltedbuilders.com/2025/01/29/understanding-table-r507-5-from-the-2018-international-residential-code-irc-choosing-the-right-deck-beam-size-made-simple/#comment-6</link>

		<dc:creator><![CDATA[Khloe4379]]></dc:creator>
		<pubDate>Tue, 22 Apr 2025 20:19:46 +0000</pubDate>
		<guid isPermaLink="false">https://kiltedbuilder.com/?p=1559#comment-6</guid>

					<description><![CDATA[Very good ]]></description>
			<content:encoded><![CDATA[<p>Very good </p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
