<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Engineering &amp; Autonomous Systems on Software with Hinome</title><link>https://realhinome.github.io/blog/</link><description>Recent content in Software Engineering &amp; Autonomous Systems on Software with Hinome</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://realhinome.github.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Reproducibility for a fleet, why NixOS?</title><link>https://realhinome.github.io/blog/drone/os/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://realhinome.github.io/blog/drone/os/</guid><description>&lt;p&gt;&lt;em&gt;Selected music:
&lt;a href="https://en.wikipedia.org/wiki/1000_Airplanes_on_the_Roof"&gt;&lt;strong&gt;1000 Airplanes on the Roof&lt;/strong&gt;&lt;/a&gt;
by Philip Glass.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In this post, we explore what is NixOS and how to use it to make a hardened OS.&lt;/p&gt;
&lt;h2 id="nixos-in-deep"&gt;NixOS in deep&lt;/h2&gt;
&lt;p&gt;NixOS is a Linux distribution that treats an operating system like code.
First, NixOS is declarative; we write a configuration that describes exactly
how we want our system to look. NixOS is binary: either the installation
succeeded, or it failed and nothing happened. Because the system is built from
a text file, we can take that one file to a brand-new computer, run the
installer, and get an identical twin of our original machine in minutes.&lt;/p&gt;</description></item><item><title>An introduction to Ringil</title><link>https://realhinome.github.io/blog/drone/init-project/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://realhinome.github.io/blog/drone/init-project/</guid><description>&lt;p&gt;&lt;em&gt;Selected music:
&lt;a href="https://en.wikipedia.org/wiki/Symphony_No._3_(G%C3%B3recki)"&gt;&lt;strong&gt;Symphony No. 3&lt;/strong&gt;&lt;/a&gt; by
Henryk Górecki.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In this post, we explore the architecture of autonomous drones, designed with
the scalability required for swarm operations.&lt;/p&gt;
&lt;h2 id="current-state-of-the-art"&gt;Current State of the Art&lt;/h2&gt;
&lt;p&gt;Since the onset of the conflict in Ukraine, drones have become central to modern
warfare. Yet, for most people, they remain a hobby. In both contexts, building a
resilient system requires a foundation that prioritizes adherence to user
instructions.&lt;/p&gt;
&lt;p&gt;In fact, in a civilian context, we must prevent catastrophic failures&amp;ndash;at high
speeds, a drone&amp;rsquo;s kinetic energy makes it a lethal projectile. From a military
perspective, the system must withstand standard cyberattacks and electronic
warfare. Naturally, we can rule out Windows Server 2016 for our stack&amp;hellip; since
our requirements demand peak performance and extreme energy efficiency.
Unfortunately, macOS Server no longer lives&amp;ndash;a drone may have fallen on it? This
leaves us with the following option: Linux. But to manage a fleet reliably, we
need a declarative paradigm.&lt;/p&gt;</description></item></channel></rss>