<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Techniques on Hillel Wayne</title>
    <link>https://www.hillelwayne.com/tags/techniques/</link>
    <description>Recent content in Techniques on Hillel Wayne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 17 Jun 2024 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.hillelwayne.com/tags/techniques/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Composing TLA&#43; Specifications with State Machines</title>
      <link>https://www.hillelwayne.com/post/composing-tla/</link>
      <pubDate>Mon, 17 Jun 2024 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/composing-tla/</guid>
      <description>Last year a client asked me to solve a problem: they wanted to be able to compose two large TLA+ specs as part of a larger system. Normally you&amp;rsquo;re not supposed to do this and instead write one large spec with both systems hardcoded in, but these specs were enormous and had many internal invariants of their own. They needed a way to develop the two specs independently and then integrate them with minimal overhead.</description>
    </item>
    
  </channel>
</rss>