Add article: Result isomorphism

Author: ploeh

_posts/2017-10-4-from-design-patterns-to-category-theory.html

@@ -272,6 +272,7 @@ <h3 id="a90284d241c4463583401504395a4a8a">
 					<li><a href="/2018/02/19/abstract-class-isomorphism">Abstract class isomorphism</a></li>
 					<li><a href="/2018/02/26/inheritance-composition-isomorphism">Inheritance-composition isomorphism</a></li>
 					<li><a href="/2019/07/15/tester-doer-isomorphisms">Tester-Doer isomorphisms</a></li>
+					<li><a href="/2025/10/15/result-isomorphism">Result isomorphism</a></li>
 					<li><a href="/2020/02/10/builder-isomorphisms">Builder isomorphisms</a></li>
 				</ul>
 			</li>			

_posts/2018-01-08-software-design-isomorphisms.html

@@ -102,6 +102,7 @@ <h3 id="ccf56c166177427785d71baf7cb7158f">
 			<li><a href="/2018/02/19/abstract-class-isomorphism">Abstract class isomorphism</a></li>
 			<li><a href="/2018/02/26/inheritance-composition-isomorphism">Inheritance-composition isomorphism</a></li>
 			<li><a href="/2019/07/15/tester-doer-isomorphisms">Tester-Doer isomorphisms</a></li>
+			<li><a href="/2025/10/15/result-isomorphism">Result isomorphism</a></li>
 			<li><a href="/2020/02/10/builder-isomorphisms">Builder isomorphisms</a></li>
 		</ul>
 		In general, I've tried to name each isomorphism after its canonical representation. For instance, by <em>unit isomorphisms</em>, I mean isomorphisms to the unit value. It is, however, not an entirely consistent naming strategy.

_posts/2019-07-15-tester-doer-isomorphisms.html

@@ -317,6 +317,6 @@ <h3 id="8e3e7b55ac1e49568712675713426e59">
 		While all three designs are equivalent in the sense that you can translate one into another, it doesn't imply that they're equally useful. <em>Maybe</em> is the superior design, and Tester-Doer clearly inferior.
 	</p>
 	<p>
-		<strong>Next:</strong> <a href="/2020/02/10/builder-isomorphisms">Builder isomorphisms</a>.
+		<strong>Next:</strong> <a href="/2025/10/15/result-isomorphism">Result isomorphism</a>.
 	</p>
 </div>