<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>MechanicalRuby</title>
        <link>https://mechanicalruby.com</link>
        <description>Posts from MechanicalRuby's blog</description>
        <copyright>MechanicalRuby (c) 2025, CC BY-SA 4.0</copyright>
        <language>en-us</language>
        <lastBuildDate>Sat, 21 Mar 2026 17:24:08 </lastBuildDate>
        <atom:link href="https://mechanicalruby.com/rss.xml" rel="self" type="application/rss+xml" />
        <image>
            <link>https://mechanicalruby.com</link>
            <title>MechanicalRuby</title>
            <url>https://mechanicalruby.com/favicon.png</url>
            <height>32</height>
            <width>32</width>
        </image>
        <item>
            <title>Hello, world!</title>
            <pubDate>Tue, 29 Apr 2025 00:00:00 PST</pubDate>
            <link>https://mechanicalruby.com/blog/a-new-path/</link>
            <guid>https://mechanicalruby.com/blog/a-new-path/</guid>
            <description>&lt;p&gt;Hello, world! I finally have my own website! And there's so much to do.&lt;/p&gt;
&lt;h1&gt;My own site!&lt;/h1&gt;
&lt;p&gt;I started working on this a while ago. I saw so many other people with awesome blogs, writing
about things they cared about- and I've always craved some sort of semi-public outlet for that type of thing, but I never took the time to make one. Now I have one!&lt;/p&gt;
&lt;p&gt;I don't really know what I should discuss in my first blog post, so I'll just talk about myself and this website generally:&lt;/p&gt;
&lt;h2&gt;Programming&lt;/h2&gt;
&lt;p&gt;I used &lt;a href="https://svelte.dev/docs/kit/introduction"&gt;SvelteKit&lt;/a&gt; for this project. It's great for static sites, and I've really enjoyed how effective
Svelte is through its simplicity. I started working on a similar web project using Astro, but I quickly
found myself using Svelte exclusively for all the components and ... I just ended up switching
to SvelteKit because of some weird problems I had with Astro.&lt;/p&gt;
&lt;p&gt;Programming the site was fairly straightforward, but I struggled with project management. I never realized how difficult it could be to get important tasks done without planning. So it took a couple of weeks for me to make time, and actually get everything to an acceptable state.&lt;/p&gt;
&lt;p&gt;It's not perfect- there's some rough edges and some things I can improve. For example: I'll have to manually update every page when I author a new blog post. I know how to fix this, but I'm quickly learning it's best not to overcomplicate things until it's absolutely necessary.&lt;/p&gt;
&lt;p&gt;I'm exploring project management systems in my free time, so that'll probably be what my next post is about. And the site should look a little different by then.&lt;/p&gt;
&lt;h2&gt;Design&lt;/h2&gt;
&lt;p&gt;I think my visual design skills need some work...&lt;/p&gt;
&lt;p&gt;I always thought I was &lt;em&gt;okay&lt;/em&gt; as a graphic designer but apparently not. There's something wrong about the heirarchy or whatever. It feels a little off, despite being fairly minimal.&lt;/p&gt;
&lt;p&gt;I'd love to give this site a more creative, asymmetric design with lots of stickers and a spacey background. But I'm not going to waste any more of my time editing the site. I'll do that LATER!&lt;/p&gt;
&lt;p&gt;So ... I like the design for what it is. But it doesn't look &lt;em&gt;exactly&lt;/em&gt; how I'd love it to look, so I'll take some time to personalize it in the future. I really don't want my &lt;em&gt;personal&lt;/em&gt; website to end up looking soulless and basic for too long.&lt;/p&gt;
&lt;h1&gt;Conclusion&lt;/h1&gt;
&lt;p&gt;So yeah, things are still pretty empty and unfinished around here right now. I made dark mode styles, but there's no button or autodetection yet. I have projects I want to show off, but they're not exactly in a state to &lt;em&gt;be&lt;/em&gt; shown off yet.&lt;/p&gt;
&lt;p&gt;I'm hoping this is the beginning of a productive and creative era for me. I spend so much time working on things that never blossom into tangible, finished products. And I can't wait to finally share more!&lt;/p&gt;
&lt;p&gt;&lt;em&gt;(Next on the list: add an art section.)&lt;/em&gt;&lt;/p&gt;
</description>
        </item>
        <item>
            <title>The first redesign</title>
            <pubDate>Mon, 25 Aug 2025 00:00:00 PST</pubDate>
            <link>https://mechanicalruby.com/blog/the-first-redesign/</link>
            <guid>https://mechanicalruby.com/blog/the-first-redesign/</guid>
            <description>&lt;p&gt;I finally spent the time I needed to bring my website up to my basic personal standards.
I wrote some stuff about myself here and there, added outbound links to some other
sites I like, and removed a lot of junk code!&lt;/p&gt;
&lt;p&gt;Partially because I read &lt;a href="https://thoughts.melonking.net/thoughts/every-site-needs-a-links-page-why-linking-matters"&gt;this&lt;/a&gt;
and I felt a little guilty about leaving my site in the state it was. But it still took a while.&lt;/p&gt;
&lt;p&gt;The theming continues to be the hardest part for me. As a programmer, I highly value
simple, utilitarian design. But as a creative I also feel like my personal site shouldn't
be so cold and plain. At least now I have a clean base to build off of! Instead of junk!&lt;/p&gt;
&lt;p&gt;Everything got a lot easier after I stopped trying to make everything huge for fat fingering on your phone.
Phones are pretty big these days, and even if they're small ... touching what you want is generally
pretty accurate. So I reverted to plain bullet lists, and more plain HTML in general.&lt;/p&gt;
&lt;p&gt;I also took the time to read the PS Vita &lt;a href="https://www.sie.com/content/dam/corporate/jp/guideline/PS_Vita_Web_Content-Guidelines_e.pdf"&gt;browser spec&lt;/a&gt;,
so hopefully my site renders properly there. It's &lt;a href="https://www.w3.org/TR/CSS2/propidx.html"&gt;CSS2&lt;/a&gt;
compliant, but I don't know if things like &lt;code&gt;flexbox&lt;/code&gt; are added as the 'partial CSS3' support it mentions? So I'm avoiding that for now. I hope it works!&lt;/p&gt;
</description>
        </item>
        <item>
            <title>A dubious Switch modchip install</title>
            <pubDate>Fri, 13 Mar 2026 00:00:00 PST</pubDate>
            <link>https://mechanicalruby.com/blog/dubious-switch-modchip-install/</link>
            <guid>https://mechanicalruby.com/blog/dubious-switch-modchip-install/</guid>
            <description>&lt;p&gt;I finished the Switch modchip installation at the end of January,
but I guess I'll tell the story of how it went before I update
this page with other stuff. It went alright?&lt;/p&gt;
&lt;p&gt;I collected all the materials and went through the literally
painful process of disassembling the Switch, which involved slowly
wrenching two of the soft, easily stripped tri-wing screws away from the
backplate before being forced to pry open and destroy it. My right thumb
had a blister from trying to remove those devil screws.&lt;/p&gt;
&lt;p&gt;In the end, I did a respectable solder job, but I decided it was slightly ugly-
one of the joints (top of SP1) was pointy and I had to clip it flat. So I tried to
reflow that joint!&lt;/p&gt;
&lt;p&gt;The solder stuck to the other side.&lt;/p&gt;
&lt;p&gt;I panicked and tried to swipe a gap between the two capicitor pads and ...
in the end, it was hot enough to have two of the SP1 caps come off the APU.&lt;/p&gt;
&lt;p&gt;After I cleaned up the mess, I was rather upset at the fact that I had
turned a working solder job into a disaster. I would have to purchase and
install new capacitors and that could take weeks, the Switch would have
to stay disassembled while I wait for parts, I don't have the requisite skills,
super stressful.&lt;/p&gt;
&lt;p&gt;Then I read on Reddit that some people had one or two caps missing and it
worked perfectly fine. I tested continuity and SOMEHOW the solder was
making solid, seperated connections to the bare pads. So screw it. I'll just
reassemble the console.&lt;/p&gt;
&lt;p&gt;And it worked. It still works.&lt;/p&gt;
&lt;p&gt;I don't know how good this is long-term but I don't care anymore. Now I can develop
and run homebrew for this thing! Yay!&lt;/p&gt;
</description>
        </item>
        <item>
            <title>Python for static site building</title>
            <pubDate>Mon, 29 Dec 2025 00:00:00 PST</pubDate>
            <link>https://mechanicalruby.com/blog/python-for-static-site-building/</link>
            <guid>https://mechanicalruby.com/blog/python-for-static-site-building/</guid>
            <description>&lt;blockquote&gt;
&lt;p&gt;I wish my posts would stop being meta commentary about developing the
site... but I think this is at least slightly better than being a glorified
changelog.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I hate needless complexity.&lt;/p&gt;
&lt;p&gt;I started my blog using Svelte / SvelteKit and found it to be easy to start
with! But over time, I found it somewhat unwieldly for my use case.
I don't want to rely on a JavaScript runtime like Node.js to build my site,
since all I'm doing is serving JS-free text-only content.&lt;/p&gt;
&lt;p&gt;Once I examined what my needs were, I realized that all I need is a
script that glues HTML files. Header to content, content to footer. That's it.&lt;/p&gt;
&lt;p&gt;So I wrote that. I used Python, both for its excellent package ecosystem and
its (relative) portability. I could easily edit and build my site on my Android
phone! I considered C since I've been writing a lot of that lately, but besides
the ugly implementation I'd probably end up writing, things like Markdown parsing
and code highlighting would be a massive burden for me.&lt;/p&gt;
&lt;p&gt;Python has tons of ways to make it easy to compile simple sites like mine. I
use:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;mistune&lt;/code&gt; for Markdown content parsing&lt;/li&gt;
&lt;li&gt;&lt;code&gt;python-frontmatter&lt;/code&gt; for Markdown frontmatter parsing&lt;/li&gt;
&lt;li&gt;and sooon enough, &lt;code&gt;pygments&lt;/code&gt; for code highlighting&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Far from the 100~ Node modules that get imported as soon as you initialize
even a more lightweight static site generator like 11ty. My site repository shrunk
from 180 megabytes to &lt;strong&gt;78 kilobytes&lt;/strong&gt;!&lt;/p&gt;
</description>
        </item>
    </channel>
</rss>