<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Ukraine on BonesMoses.org</title>
		<link>https://bonesmoses.org/tags/ukraine/</link>
		<description>Recent content in Ukraine on BonesMoses.org</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 26 Mar 2022 14:13:33 -0500</lastBuildDate>
		
			<atom:link href="https://bonesmoses.org/tags/ukraine/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Harmonic Seating</title>
				<link>https://bonesmoses.org/2022/harmonic-seating/</link>
				<pubDate>Sat, 26 Mar 2022 14:13:33 -0500</pubDate>
				<guid>https://bonesmoses.org/2022/harmonic-seating/</guid>
				<description>&lt;blockquote&gt;&#xA;  &lt;p&gt;We are living on the brink of the apocalypse, but the world is asleep.&lt;/p&gt;&#xA;  &lt;footer&gt;&#xA;    &lt;strong&gt; &amp;ndash; Joel C. Rosenberg&lt;/strong&gt;&#xA;      &#xA;  &lt;/footer&gt;&#xA;&lt;/blockquote&gt;&#xA;&#xA;&#xA;&lt;p&gt;I&amp;rsquo;m one of the most pessimistic people I know. Yet it&amp;rsquo;s this same unique trait I exploit while designing High Availability architectures. I expect things to fail, and plan for the worst almost constantly. I&amp;rsquo;ve &lt;a href=&#34;https://www.packtpub.com/product/postgresql-12-high-availability-cookbook-third-edition/9781838984854&#34;&gt;based my career&lt;/a&gt; on it. Granted, worst case scenarios rarely come to pass, but my motto is and always will be to &amp;ldquo;Hope for the best, but prepare for the worst.&amp;rdquo;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
