<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Structural-Engineering on Evgeny Ramenskiy</title>
		<link>https://ramenskiy.com/tags/structural-engineering/</link>
		<description>Recent content in Structural-Engineering on Evgeny Ramenskiy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC 4.0&lt;/a&gt;</copyright>
		
		
			<lastBuildDate>Wed, 01 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://ramenskiy.com/tags/structural-engineering/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The Solver Was Never the Moat</title>
				<link>https://ramenskiy.com/posts/posts/the-solver-was-never-the-moat/</link>
				<pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://ramenskiy.com/posts/posts/the-solver-was-never-the-moat/</guid>
				<description>&lt;p&gt;Sometime in the last year, the standalone structural solver quietly became a tool call.&lt;/p&gt;&#xA;&lt;p&gt;As of mid-2026: Bentley shipped an open-source MCP server for STAAD. Dlubal built one into RFEM 6. Autodesk shipped one for Revit. Type &amp;ldquo;reduce the steel weight,&amp;rdquo; and an agent iterates the solver and code-checks every pass. The work that used to require a trained specialist at a desktop now runs behind a natural-language prompt.&lt;/p&gt;&#xA;&lt;p&gt;The obvious reading is that the vertical startups are finished. If the incumbent&amp;rsquo;s engine now answers to an agent, why pay a point-solution company that automated one slice of it? I think that reading is wrong, and it is wrong in a way worth being precise about, because the precise version is more useful than the punchy one.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
