<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Done on The Edge Cases</title>
    <link>https://www.kylestratis.com/tags/done/</link>
    <description>Recent content in Done on The Edge Cases</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© 2025</copyright>
    <lastBuildDate>Fri, 18 Sep 2026 22:38:55 -0400</lastBuildDate>
    <atom:link href="https://www.kylestratis.com/tags/done/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LLM Knowledge Management Agent</title>
      <link>https://www.kylestratis.com/notes/llm-knowledge-management-agent/</link>
      <pubDate>Sat, 06 May 2023 16:47:59 +0000</pubDate>
      <guid>https://www.kylestratis.com/notes/llm-knowledge-management-agent/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;: An agent to research a given topic by doing &lt;a href=&#34;https://fs.blog/how-to-read-a-book/#:~:text=4.-,Syntopical%20Reading,ideas%2C%20vocabulary%2C%20and%20arguments.&#34;&gt;analytical and syntopic reading&lt;/a&gt;, summarizing and extracting main points, connecting them together, and forming new knowledge outputs such as &lt;a href=&#34;https://zettelkasten.de/posts/overview/&#34;&gt;zettels&lt;/a&gt; or &lt;a href=&#34;https://codex.erisianrite.com/Bins/Evergreen&amp;#43;Notes/What&amp;#43;Is&amp;#43;An&amp;#43;Evergreen&amp;#43;Note&amp;#43;Anyways&#34;&gt;evergreen notes&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;lessons-learned&#34;&gt;Lessons Learned&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;~~Document embeddings with transformers don&amp;rsquo;t seem to be too practical. Instead, go with a sentence embedding for the knowledgebase using note titles and search with main idea embeddings.&lt;/li&gt;&#xA;&lt;li&gt;Dispatch table values need to the the function as an object, so without the parentheses. Otherwise they&amp;rsquo;ll be run when instantiated.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;project-notes&#34;&gt;Project Notes&lt;/h3&gt;&#xA;&lt;h3 id=&#34;future-improvements&#34;&gt;Future Improvements&lt;/h3&gt;&#xA;&lt;p&gt;Future improvements to the project should go here for easy reference. They should be a type of project note and link back to a Project page and any tickets that come from it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Personal Site Redesign</title>
      <link>https://www.kylestratis.com/notes/personal-site-redesign/</link>
      <pubDate>Wed, 26 Jan 2022 04:46:05 +0000</pubDate>
      <guid>https://www.kylestratis.com/notes/personal-site-redesign/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;I want to move away from webflow and build a simpler, static site for my articles and stuff.&lt;/p&gt;&#xA;&lt;h2 id=&#34;lessons-learned&#34;&gt;Lessons Learned&lt;/h2&gt;&#xA;&lt;p&gt;Hugo archetypes are templates for different content types. They allow you to configure different frontmatter.&#xA;- &lt;a href=&#34;https://www.kylestratis.com/notes/hugo-archetypes/&#34;&gt;Hugo Archetypes&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Each directory within the &lt;code&gt;content/&lt;/code&gt; directory defines a different content section (like tutorials, articles, etc.), and this is used to determine a content&amp;rsquo;s content type.&#xA;- &lt;a href=&#34;https://www.kylestratis.com/notes/hugo-project-architecture/&#34;&gt;Hugo Project Architecture&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://gohugo.io/content-management/page-bundles/&#34;&gt;Page Bundles&lt;/a&gt; are a way to organize pages. Branch bundles are used for a home page, section page, taxonomy terms, etc. (these are &lt;em&gt;list pages&lt;/em&gt;) and must contain at least an &lt;code&gt;_index.md&lt;/code&gt; file. Leaf bundles contain at least an &lt;code&gt;index.md&lt;/code&gt; file and define a regular page. These aren&amp;rsquo;t required organization methods, however. This all occurs within the &lt;code&gt;content/&lt;/code&gt; directory.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
