<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Miscs on Amy Lily</title>
    <link>https://amylily1011.github.io/misc/</link>
    <description>Recent content in Miscs on Amy Lily</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
    <lastBuildDate>Tue, 07 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://amylily1011.github.io/misc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From Infra Chaos to a Personal AI Operator: Building with OpenClaw</title>
      <link>https://amylily1011.github.io/misc/openclaw-setup/</link>
      <pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://amylily1011.github.io/misc/openclaw-setup/</guid>
      <description>&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;Built a personal AI operator using OpenClaw + Telegram + Claude.&#xA;Got stuck optimizing too early (local models, networking).&#xA;Reset everything.&#xA;Used OpenClaw onboarding + Anthropic API.&#xA;Connected Telegram.&#xA;System worked instantly.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Biggest lesson: Getting something working &amp;gt; getting everything perfect.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Over the past few days, I set out to build something simple:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;a personal AI operator I could interact with through Telegram.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;What I ended up building was not just a chatbot, but a small system:&lt;/p&gt;</description>
    </item>
    <item>
      <title>AIBadge: A Weekend Experiment about AI Provenance</title>
      <link>https://amylily1011.github.io/misc/aibadge/</link>
      <pubDate>Mon, 09 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://amylily1011.github.io/misc/aibadge/</guid>
      <description>summary: A meeting question about AI disclosure led to a weekend experiment exploring trust, authorship, and verifiable integrity in the age of generative AI.</description>
    </item>
    <item>
      <title>From Confusion to Clarity: Designing `/explain` to Make Concepts Click</title>
      <link>https://amylily1011.github.io/misc/explain/</link>
      <pubDate>Sat, 12 Mar 2022 17:15:51 +0100</pubDate>
      <guid>https://amylily1011.github.io/misc/explain/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Context:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;At Canonical, internal teams often work in highly specialized domains — cloud infrastructure, AI, enterprise support, etc. As a product designer, I frequently saw confusion arise when teams shared updates full of acronyms, assumptions, and product-specific jargon.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h3 id=&#34;why&#34;&gt;Why?&lt;/h3&gt;&#xA;&lt;p&gt;During a design review, I realized that while I thought I had clearly explained the mental model behind LXD integration in MAAS, my colleagues didn’t follow.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://amylily1011.github.io/images/explain/maas-explain.png&#34; alt=&#34;explain lxd in MAAS&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Little did I know, this was how other designers understood my explanation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The new MAAS CLI that changes Ubuntu CLI Guideline</title>
      <link>https://amylily1011.github.io/misc/maas-cli/</link>
      <pubDate>Mon, 28 Sep 2020 17:15:51 +0100</pubDate>
      <guid>https://amylily1011.github.io/misc/maas-cli/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Context:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;MAAS (Metal-as-a-service) is Canonical&amp;rsquo;s bare-metal provisioning tool. The CLI was originally created for machines to interface with machines via the Foundations Cloud Engine (FCE) making it difficult for human to use. Over time, users either abandoned the CLI or built their own wrappers — indicating a breakdown in usability and trust. We set out to reimagine what a CLI could feel like when designed with empathy, efficiency, and accessibility in mind.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
