<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: neitherGalax</title>
    <description>The latest articles on DEV Community by neitherGalax (@neithergalax).</description>
    <link>https://dev.to/neithergalax</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3936929%2F251db066-c66f-405c-aafe-019e9dbc9862.png</url>
      <title>DEV Community: neitherGalax</title>
      <link>https://dev.to/neithergalax</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/neithergalax"/>
    <language>en</language>
    <item>
      <title>📓Meet devReflections: Always Moving Forward, But When Do We Pause and Reflect?</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Tue, 10 Nov 2026 18:27:58 +0000</pubDate>
      <link>https://dev.to/neithergalax/always-moving-forward-but-when-do-we-pause-and-reflect-3e8c</link>
      <guid>https://dev.to/neithergalax/always-moving-forward-but-when-do-we-pause-and-reflect-3e8c</guid>
      <description>&lt;p&gt;Technology moves so fast. New AI models, frameworks, tools, workflows appear almost every day. As developers, we are constantly encouraged to keep up, learn something new, and build more. &lt;/p&gt;

&lt;p&gt;BUT in this fast-moving environment, it's easy to forget something important: taking time to reflect on what we've actually learned.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pressure to keep up
&lt;/h2&gt;

&lt;p&gt;With AI accelerating how we write code and build things, the pressure to stay current can feel greater than ever. There's always another tool to explore, another skill to learn, or another project to start.&lt;/p&gt;

&lt;p&gt;Sometimes, we move from one task to the next without giving ourselves time to process what we've experienced. Over time, this constant cycle can leave us overwhelmed, disconnected, or simply less motivated.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Reflection Matters
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Reflection&lt;/strong&gt; gives us an opportunity to slow down and recognize the value of our experiences, even the small ones.&lt;/p&gt;

&lt;p&gt;It's also an important part of &lt;strong&gt;intentional learning&lt;/strong&gt;. In an age when AI can generate code, explain concepts, and provide quick solutions, actively engaging with what we learn matters more than ever. We need to understand not just what works, but why it works and what we can take away from the experience.&lt;/p&gt;

&lt;p&gt;Growth isn't just about how much we build or how quickly we learn. It's also about understanding our progress, recognizing our challenges, and making sense of the journey along the way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Introducing &lt;code&gt;devReflections&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;I wanted to explore a simple way to make reflection part of the developer experience, without turning it into another productivity task.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;During Hacktoberfest&lt;/strong&gt;, I decided to turn this idea into a small project and built &lt;code&gt;devReflections&lt;/code&gt;, a lightweight, local-first journaling tool for developers and open-source contributors.&lt;/p&gt;


&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" class="crayons-story__hidden-navigation-link"&gt;📖Open-Source Field Journal: Reflect on What You Learn, Not Just What You Ship&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
      &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" class="crayons-article__context-note crayons-article__context-note__feed"&gt;&lt;p&gt;Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle Submission 💸&lt;/p&gt;

&lt;/a&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/neithergalax" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3936929%2F251db066-c66f-405c-aafe-019e9dbc9862.png" alt="neithergalax profile" class="crayons-avatar__image" width="800" height="800"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/neithergalax" class="crayons-story__secondary fw-medium m:hidden"&gt;
              neitherGalax
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                neitherGalax
                
                
              
              &lt;div id="story-author-preview-content-4846784" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/neithergalax" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3936929%2F251db066-c66f-405c-aafe-019e9dbc9862.png" class="crayons-avatar__image" alt="" width="800" height="800"&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;neitherGalax&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Oct 18&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" id="article-link-4846784"&gt;
          📖Open-Source Field Journal: Reflect on What You Learn, Not Just What You Ship
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/devchallenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;devchallenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/hf26challenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;hf26challenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/gemma"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;gemma&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/opensource"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;opensource&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/multi-unicorn-b44d6f8c23cdd00964192bedc38af3e82463978aa611b4365bd33a0f1f4f3e97.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;2&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              &lt;span class="hidden s:inline"&gt;Add&amp;nbsp;Comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            3 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;


&lt;/div&gt;


&lt;p&gt;It combines personal journaling with a locally running AI model that asks a follow-up question based on your entry, helping you explore your thoughts a little further.&lt;/p&gt;

&lt;h2&gt;
  
  
  How It Works
&lt;/h2&gt;

&lt;p&gt;The workflow is intentionally simple:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Write → Reflect → Record&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Write&lt;/strong&gt;: Choose a starter prompt or write freely about your day, challenge, or learning experiences&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Reflect&lt;/strong&gt;: A local AI model generates one follow-up question based on what you've written.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Record&lt;/strong&gt;: Add your response and save everything as a Markdown journal entry.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fao11v3u4j29nrq14zmif.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fao11v3u4j29nrq14zmif.png" alt="Sample Entry Screenshot" width="800" height="565"&gt;&lt;/a&gt;&lt;br&gt;
[Sample Entry in md file]&lt;/p&gt;

&lt;p&gt;The goal isn't to have AI tell you what to think or do. It's simply to offer another perspective and encourage a little deeper reflection.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Local-First AI?
&lt;/h2&gt;

&lt;p&gt;I wanted personal reflections to stay personal.&lt;/p&gt;

&lt;p&gt;That's why &lt;code&gt;devReflections&lt;/code&gt; uses Ollama and Gemma to run AI locally, without relying on external AI APIs. Journal entries are saved as Markdown files on your own machine. You can read, edit, back up, and keep them under your control.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI doesn't always need to give answers
&lt;/h2&gt;

&lt;p&gt;Most AI tools are designed to provide answers, solve problems, or help us get things done quickly. &lt;strong&gt;But what if AI could simply help us think?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For &lt;code&gt;devReflections&lt;/code&gt;, I wanted its questions to feel caring, approachable, reflective, grounded, and gentle. They aren't meant to give advice or judge your experience, but to encourage you to look a little deeper.&lt;/p&gt;

&lt;p&gt;Sometimes, one thoughtful question is enough. &lt;/p&gt;

&lt;h2&gt;
  
  
  Give It a Try!
&lt;/h2&gt;

&lt;p&gt;If this resonates with you, I'd like to invite you to explore &lt;code&gt;devReflections&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;You can check out the source code, visit, the demo website, or try it locally on your own machine.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://yuka-with-data.github.io/devReflections/" rel="noopener noreferrer"&gt;Demo Website&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/yuka-with-data/devReflections" rel="noopener noreferrer"&gt;GitHub Repo&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Keep learning, keep growing, and don't forget to reflect along the way.&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;How do you make time for reflection in your own developer journey? I'd like to hear your thoughts!&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>devjournal</category>
      <category>productivity</category>
      <category>python</category>
    </item>
    <item>
      <title>🎃October OSS Recap: Hacktoberfest-full of Building, Experimenting, and Shipping</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Tue, 03 Nov 2026 21:42:16 +0000</pubDate>
      <link>https://dev.to/neithergalax/october-oss-recap-hacktoberfest-full-of-building-experimenting-and-shipping-56ea</link>
      <guid>https://dev.to/neithergalax/october-oss-recap-hacktoberfest-full-of-building-experimenting-and-shipping-56ea</guid>
      <description>&lt;p&gt;October was a busy month, largely dedicated to Hacktoberfest. I spent much of it turning ideas into small, working projects while continuing to contribute to existing open-source repositories.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three Projects, Three Experiments
&lt;/h2&gt;

&lt;p&gt;During Hacktoberfest, I built three projects, each exploring a different aspect of something I'm particularly interested in: communication, reflection, and documentation.&lt;/p&gt;

&lt;h3&gt;
  
  
  GhostDocs
&lt;/h3&gt;


&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/neithergalax/ghostdocs-bringing-forgotten-knowledge-back-to-life-4nk8" class="crayons-story__hidden-navigation-link"&gt;👻 GhostDocs: Bringing Forgotten Knowledge Back to Life&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
      &lt;a href="https://dev.to/neithergalax/ghostdocs-bringing-forgotten-knowledge-back-to-life-4nk8" class="crayons-article__context-note crayons-article__context-note__feed"&gt;&lt;p&gt;Hacktoberfest Open-Source AI Challenge: Ghost in the Machine Submission 👻🌼&lt;/p&gt;

&lt;/a&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/neithergalax" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3936929%2F251db066-c66f-405c-aafe-019e9dbc9862.png" alt="neithergalax profile" class="crayons-avatar__image" width="800" height="800"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/neithergalax" class="crayons-story__secondary fw-medium m:hidden"&gt;
              neitherGalax
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                neitherGalax
                
                
              
              &lt;div id="story-author-preview-content-4959616" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/neithergalax" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3936929%2F251db066-c66f-405c-aafe-019e9dbc9862.png" class="crayons-avatar__image" alt="" width="800" height="800"&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;neitherGalax&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/neithergalax/ghostdocs-bringing-forgotten-knowledge-back-to-life-4nk8" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Nov 2&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/neithergalax/ghostdocs-bringing-forgotten-knowledge-back-to-life-4nk8" id="article-link-4959616"&gt;
          👻 GhostDocs: Bringing Forgotten Knowledge Back to Life
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/devchallenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;devchallenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/hf26challenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;hf26challenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/documentation"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;documentation&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/python"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;python&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/neithergalax/ghostdocs-bringing-forgotten-knowledge-back-to-life-4nk8" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/exploding-head-daceb38d627e6ae9b730f36a1e390fca556a4289d5a41abb2c35068ad3e2c4b5.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;2&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/neithergalax/ghostdocs-bringing-forgotten-knowledge-back-to-life-4nk8#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              &lt;span class="hidden s:inline"&gt;Add&amp;nbsp;Comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            3 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;


&lt;/div&gt;


&lt;h3&gt;
  
  
  ToneTune
&lt;/h3&gt;


&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/neithergalax/tonetune-stop-overthinking-start-expressing-28bd" class="crayons-story__hidden-navigation-link"&gt;🪶ToneTune: Stop Overthinking, Start Expressing&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
      &lt;a href="https://dev.to/neithergalax/tonetune-stop-overthinking-start-expressing-28bd" class="crayons-article__context-note crayons-article__context-note__feed"&gt;&lt;p&gt;Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady Submission 🦥&lt;/p&gt;

&lt;/a&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/neithergalax" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3936929%2F251db066-c66f-405c-aafe-019e9dbc9862.png" alt="neithergalax profile" class="crayons-avatar__image" width="800" height="800"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/neithergalax" class="crayons-story__secondary fw-medium m:hidden"&gt;
              neitherGalax
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                neitherGalax
                
                
              
              &lt;div id="story-author-preview-content-4912628" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/neithergalax" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3936929%2F251db066-c66f-405c-aafe-019e9dbc9862.png" class="crayons-avatar__image" alt="" width="800" height="800"&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;neitherGalax&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/neithergalax/tonetune-stop-overthinking-start-expressing-28bd" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Oct 25&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/neithergalax/tonetune-stop-overthinking-start-expressing-28bd" id="article-link-4912628"&gt;
          🪶ToneTune: Stop Overthinking, Start Expressing
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/devchallenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;devchallenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/hf26challenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;hf26challenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/opensource"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;opensource&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/python"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;python&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/neithergalax/tonetune-stop-overthinking-start-expressing-28bd" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/multi-unicorn-b44d6f8c23cdd00964192bedc38af3e82463978aa611b4365bd33a0f1f4f3e97.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;2&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/neithergalax/tonetune-stop-overthinking-start-expressing-28bd#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              &lt;span class="hidden s:inline"&gt;Add&amp;nbsp;Comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            4 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;


&lt;/div&gt;


&lt;h3&gt;
  
  
  devReflections
&lt;/h3&gt;


&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" class="crayons-story__hidden-navigation-link"&gt;📖Open-Source Field Journal: Reflect on What You Learn, Not Just What You Ship&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
      &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" class="crayons-article__context-note crayons-article__context-note__feed"&gt;&lt;p&gt;Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle Submission 💸&lt;/p&gt;

&lt;/a&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/neithergalax" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3936929%2F251db066-c66f-405c-aafe-019e9dbc9862.png" alt="neithergalax profile" class="crayons-avatar__image" width="800" height="800"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/neithergalax" class="crayons-story__secondary fw-medium m:hidden"&gt;
              neitherGalax
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                neitherGalax
                
                
              
              &lt;div id="story-author-preview-content-4846784" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/neithergalax" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3936929%2F251db066-c66f-405c-aafe-019e9dbc9862.png" class="crayons-avatar__image" alt="" width="800" height="800"&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;neitherGalax&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Oct 18&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" id="article-link-4846784"&gt;
          📖Open-Source Field Journal: Reflect on What You Learn, Not Just What You Ship
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/devchallenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;devchallenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/hf26challenge"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;hf26challenge&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/gemma"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;gemma&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/opensource"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;opensource&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/multi-unicorn-b44d6f8c23cdd00964192bedc38af3e82463978aa611b4365bd33a0f1f4f3e97.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;2&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              &lt;span class="hidden s:inline"&gt;Add&amp;nbsp;Comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            3 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;


&lt;/div&gt;


&lt;p&gt;Although they serve different purposes, they share a common idea: exploring how technology, particularly local AI, can help people express ideas, reflect on experiences, and preserve knowledge.&lt;/p&gt;

&lt;p&gt;Each project gave me opportunity to experiment with Python, local AI using Ollama, prompt engineering, CLI development, testing, and documentation.&lt;/p&gt;

&lt;p&gt;More importantly, I got to experience the full development cycle: from an initial idea to implementation, testing, documenting and release.&lt;/p&gt;

&lt;h2&gt;
  
  
  Beyond Hacktoberfest
&lt;/h2&gt;

&lt;p&gt;I also contributed to existing project, OSeMOSYS, submitted a PR, and worked on repository maintenance.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Learned
&lt;/h2&gt;

&lt;p&gt;One takeaway from October was that keeping a project focused makes it easier to turn an idea into something usable.&lt;/p&gt;

&lt;p&gt;I also became more comfortable managing the entire development workflow independently. Not everything needs to be complicated or feature-rich to be useful.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7ecbd3et4l3ooj3vyenv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7ecbd3et4l3ooj3vyenv.png" alt="Github Contribution Graph" width="800" height="132"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Looking Ahead: November
&lt;/h2&gt;

&lt;p&gt;For November, I want to shift my focus from creating new projects to improving what I've already built.&lt;/p&gt;

&lt;p&gt;I plan to continue developing two of the Hacktoberfest projects, exploring ways to make them more user-friendly, reliable, and closer to production-ready.&lt;/p&gt;

&lt;p&gt;I also want to spend more time contributing to established open-source projects, particularly in documentation and developer tooling.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;October was about exploring and building. November will be about refining and maturing.&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;What are you currently building or contributing to? I would like to hear about your projects and what you are exploring in open source!&lt;/em&gt;&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>hacktoberfest</category>
      <category>opensource</category>
      <category>softwaredevelopment</category>
    </item>
    <item>
      <title>👻 GhostDocs: Bringing Forgotten Knowledge Back to Life</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Mon, 02 Nov 2026 18:53:04 +0000</pubDate>
      <link>https://dev.to/neithergalax/ghostdocs-bringing-forgotten-knowledge-back-to-life-4nk8</link>
      <guid>https://dev.to/neithergalax/ghostdocs-bringing-forgotten-knowledge-back-to-life-4nk8</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week4-2026-10-26"&gt;Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GhostDocs&lt;/strong&gt; is a local-first documentation analysis tool that uncovers forgotten knowledge in software repositories using open-weight AI models.&lt;/p&gt;

&lt;p&gt;I interpreted the &lt;em&gt;Ghost in the Machine&lt;/em&gt; theme as a problem that exists in many software projects: &lt;strong&gt;over time, important knowledge gets lost, forgotten, or never properly documented.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A repository might contain code that nobody remembers how to use, decisions that were never recorded or functionality that has become difficult to understand because its documentation no longer tells the whole story.&lt;/p&gt;

&lt;p&gt;I wanted to explore whether AI could help uncover these hidden pieces of knowledge.&lt;/p&gt;

&lt;p&gt;Instead of building another documentation linter or broken-link checker, I created &lt;strong&gt;GhostDocs&lt;/strong&gt; to investigate a different question:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What important knowledge has this repository lost, forgotten, or failed to document?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GhostDocs&lt;/strong&gt; scans a project, analyzes its documentation and repository context using a local AI model, and generates a report with three main sections:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Lost Knowledge: Important information that appears to be missing or undocumented.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Ghost Sightings: Potential inconsistencies, forgotten context, and documentation gaps.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Resurrection Plan: Suggested actions to bring that knowledge back into the documentation.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal is not to automatically rewrite documentation, but to help developers recognize what might be missing and decide what deserves attention.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;GhostDocs currently runs locally through a command-line interface (CLI).&lt;/p&gt;

&lt;p&gt;You can try it with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Scan the current repository&lt;/span&gt;
ghostdocs .

&lt;span class="c"&gt;# Scan a project and save the report&lt;/span&gt;
ghostdocs examples/haunted-project --output report.md
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/yuka-with-data/GhostDocs/tree/main" rel="noopener noreferrer"&gt;GitHub Repo Link&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;I built &lt;strong&gt;GhostDocs&lt;/strong&gt; with Python and Ollama, using open-weight &lt;code&gt;gemma4:e4b&lt;/code&gt; model for local inference.&lt;/p&gt;

&lt;p&gt;The project follows a simple architecture:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Repository Scanner&lt;/li&gt;
&lt;li&gt;AI Analyzer&lt;/li&gt;
&lt;li&gt;Report Generator&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I deliberately kept the implementation lightweight. &lt;strong&gt;GhostDocs&lt;/strong&gt; does not modify the original repository files, and the analysis runs locally rather than relying on a hosted AI API.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;Open innovation made it possible to build &lt;strong&gt;GhostDocs&lt;/strong&gt; around local AI inference rather than depending on a closed, hosted API.&lt;/p&gt;

&lt;p&gt;Using Ollama and an open-weight model gave me more control over how the model runs, which model to use, and where repository content is processed.&lt;/p&gt;

&lt;p&gt;This matters for a documentation analysis tool because &lt;strong&gt;software repositories can contain internal implementation details and project knowledge that developers may not want to send to external services&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It also makes experimentation more accessible. Developers can explore the project, inspect its prompts and implementation, change the model, and adapt it to their own workflows.&lt;/p&gt;

&lt;p&gt;For me, open innovation is not just about making the source code available. It is also about giving people the freedom to understand, experiment with, and build upon the technology.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Spirit of It
&lt;/h2&gt;

&lt;p&gt;Every repository has a history.&lt;/p&gt;

&lt;p&gt;Some knowledge survives in documentation, some remains buried in code, and some eventually disappears as the people who created it move on.&lt;/p&gt;

&lt;p&gt;GhostDocs is a small experiment in using AI to help recover some of that forgotten knowledge.&lt;/p&gt;

&lt;p&gt;Sometimes, the most interesting things in a repository are not the things that are documented, but the things that are missing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Best use of Gemma&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>documentation</category>
      <category>python</category>
    </item>
    <item>
      <title>🪶ToneTune: Stop Overthinking, Start Expressing</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Sun, 25 Oct 2026 18:16:07 +0000</pubDate>
      <link>https://dev.to/neithergalax/tonetune-stop-overthinking-start-expressing-28bd</link>
      <guid>https://dev.to/neithergalax/tonetune-stop-overthinking-start-expressing-28bd</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week3-2026-10-19"&gt;Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;Have you ever sat in front of your computer, knowing what you wanted to express but struggling to find the right words?&lt;/p&gt;

&lt;p&gt;Maybe it's a message to a teammate, feedback for an open-source contributor, or a simple email you've been putting off. The thought is there. Expressing it is the hard part.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;ToneTune&lt;/code&gt; is a &lt;strong&gt;local AI writing companion&lt;/strong&gt; that helps turn rough thoughts into messages that feel like &lt;strong&gt;you&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Give it a few fragments, choose a communication type and tone, and let it help shape your words into a draft. Instead of starting from a blank page, you start with something you can review, edit, and make your own.&lt;/p&gt;

&lt;p&gt;I built &lt;code&gt;ToneTune&lt;/code&gt; with a simple goal: &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;reduce the effort of expressing yourself without taking away your control over what you say.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because sometimes, the hardest part of writing isn't knowing what you mean. It's getting those thoughts onto the page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://yuka-with-data.github.io/ToneTune/" rel="noopener noreferrer"&gt;Demo link&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 1: Welcome Screen &amp;amp; Share your thoughts
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fywv8469yl4u1xcsq5snt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fywv8469yl4u1xcsq5snt.png" alt="Startup" width="672" height="175"&gt;&lt;/a&gt;&lt;br&gt;
Type rough ideas or fragments. No need to get the wording right yet.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2: Choose a communication type
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3qgpcn3hrjgz5fdilr98.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3qgpcn3hrjgz5fdilr98.png" alt="Choose a tone" width="591" height="418"&gt;&lt;/a&gt;&lt;br&gt;
Select the kind of message you want to write.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3: Choose a tone
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuu54a5m9i1h9za0z5kn1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuu54a5m9i1h9za0z5kn1.png" alt="Choose a tone" width="567" height="427"&gt;&lt;/a&gt;&lt;br&gt;
Pick the tone that best fits your intended message.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4: Get your draft
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcma5adoi393dxa9akeq4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcma5adoi393dxa9akeq4.png" alt="Get your draft" width="800" height="60"&gt;&lt;/a&gt;&lt;br&gt;
&lt;code&gt;ToneTune&lt;/code&gt; turns your input into a draft you can review, edit, and make your own.&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/yuka-with-data/ToneTune" rel="noopener noreferrer"&gt;GitHub Repo Link&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;I built &lt;code&gt;ToneTune&lt;/code&gt; with Python, Ollama, and Google's open-weight Gemma 4 model. The goal was to keep the experience simple: a lightweight CLI that runs locally and helps people communicate more easily.&lt;/p&gt;

&lt;p&gt;Under the hood, I kept the project modular:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Python CLI&lt;/strong&gt;: Guides users through choosing a communication type, selecting a tone, and entering their thoughts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ollama + Gemma 4&lt;/strong&gt;: Runs the model locally to transform rough input into a readable draft.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prompt templates&lt;/strong&gt;: Separate the core writing instructions from the Python logic, making it easier to refine the model's behavior without complicating the codebase.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tests and GitHub Actions&lt;/strong&gt;: Pytest, Pylint, and Markdown linting help keep the project maintainable as it evolves.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Once design priority was preserving the user's intent. &lt;code&gt;ToneTune&lt;/code&gt; should improve how a message is expressed, not invent details or change what the person wants to say.&lt;/p&gt;

&lt;p&gt;I'm starting with a CLI rather than a full application so I can focus on the core experience first: making it easier to go from rough thoughts to words that feel right.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Writing is personal.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The messages we struggle to express can contain unfinished thoughts, work conversations, or ideas we're not ready to share. I wanted &lt;code&gt;ToneTune&lt;/code&gt; to offer help without making a remote AI service a requirement.&lt;/p&gt;

&lt;p&gt;Using &lt;strong&gt;Ollama&lt;/strong&gt; and an &lt;strong&gt;open-weight Gemma model&lt;/strong&gt; lets me run &lt;code&gt;ToneTune&lt;/code&gt; locally, keeping the core experience on my own machine rather than depending on a hosted AI API. This gives me more control over how the model runs and how the project evolves.&lt;/p&gt;

&lt;p&gt;Open innovation also makes experimentation more accessible. I can inspect and refine prompts, test different models, and build on existing open-source tools without starting from scratch or locking the project into a single provider.&lt;/p&gt;

&lt;p&gt;For me, that's the real value: open technology makes it possible to build useful tools on your own terms. &lt;code&gt;ToneTune&lt;/code&gt; is a small project, but it reflects a bigger idea: AI should help people do more while giving them meaningful control over the tools they use.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Lazy Payoff
&lt;/h2&gt;

&lt;p&gt;Sometimes, the hardest part of writing isn't typing. It's sitting in front of a screen, turning the same thoughts over and over, trying to figure out what to say and how to say it.&lt;/p&gt;

&lt;p&gt;I've experienced this many times. I know what I want to express, but getting those thoughts into the right words takes more time and mental energy than it should.&lt;/p&gt;

&lt;p&gt;That's the friction I wanted &lt;code&gt;ToneTune&lt;/code&gt; to reduce.&lt;/p&gt;

&lt;p&gt;Instead of struggling to produce a polished message from scratch, I can start with rough thoughts, not even rough drafts, let &lt;code&gt;ToneTune&lt;/code&gt; shape them into a draft, and focus on reviewing what matters: whether it says what I actually mean.&lt;/p&gt;

&lt;p&gt;The payoff isn't just fewer minutes spent writing. It's less overthinking, less frustration, and a lower barrier to getting started.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Best Use of Gemma&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>opensource</category>
      <category>python</category>
    </item>
    <item>
      <title>📖Open-Source Field Journal: Reflect on What You Learn, Not Just What You Ship</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Sun, 18 Oct 2026 19:10:28 +0000</pubDate>
      <link>https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h</link>
      <guid>https://dev.to/neithergalax/open-source-field-journal-reflect-on-what-you-learn-not-just-what-you-ship-4p7h</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week2-2026-10-12"&gt;Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;Open-source development isn't just about writing code. It's also about debugging, reading documentation, exploring unfamiliar projects, and learning from mistakes.&lt;/p&gt;

&lt;p&gt;But it's easy to forget what we've learned along the way.&lt;/p&gt;

&lt;p&gt;I built Open-Source Field Journal called &lt;code&gt;devReflections&lt;/code&gt;, a lightweight journaling app for developers to capture their technical experiences and reflect on them with help from AI.&lt;/p&gt;

&lt;p&gt;Users can write a free-form entry or start with a prompt. The AI responds with a reflective question to help them explore what they learned. Entries can be saved as Markdown, keeping the journal portable and under the user's control.&lt;/p&gt;

&lt;p&gt;The goal is not to track productivity or judge how much someone accomplished. It's to make space for reflection, helping people recognize what they've learned, understand their experiences, and consider what matters to them.&lt;/p&gt;

&lt;p&gt;Whether you're an independent developer, an open-source contributor, a full-time tech worker, or someone learning new skills, taking a moment to reflect can help you see beyond the daily to-do list.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Run it locally.
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;devReflections&lt;/code&gt; runs on your machine using Python and Ollama, with Gemma as the default AI model. No hosted web app is required.&lt;/p&gt;

&lt;p&gt;Here are few steps showing the core workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Welcome Screen&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fx7nlsmb88k4wje562t30.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fx7nlsmb88k4wje562t30.png" alt="Welcome screen" width="799" height="368"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;(Optional) Select Prompt&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgybo2r2u2yjj3o01mn76.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgybo2r2u2yjj3o01mn76.png" alt="Select prompt" width="800" height="288"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Write Journal Entry &amp;amp; Follow-Up Question Generation&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjggxg2tyc43tdxy6wriq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjggxg2tyc43tdxy6wriq.png" alt="Journal entry" width="798" height="159"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Answer the Follow-Up Question&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F15tpaolzbqfobzpnwkwx.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F15tpaolzbqfobzpnwkwx.png" alt="Generate Follow-up" width="798" height="129"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Save file &amp;amp; Exit&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fui6lnknxr8rsj5glv3e1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fui6lnknxr8rsj5glv3e1.png" alt="Save and exit" width="727" height="145"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;🔗&lt;a href="https://github.com/yuka-with-data/devReflections" rel="noopener noreferrer"&gt;GitHub Repo Link&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Built with Python, Ollama, and Gemma, with Markdown for portable journal entries.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;I built &lt;code&gt;devReflections&lt;/code&gt; in Python, keeping the application lightweight and focused on the reflection experience rather than adding a complex interface or relying on a cloud-based AI service.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;User
  |
  v
Choose a starter prompt or write freely
  |
  v
Describe today's work or learning
  |
  v
Ollama runs Gemma locally
  |
  v
AI generates one reflective question
  |
  v
User writes their reflection
  |
  v
Save entry as a Markdown file
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Local AI with Ollama and Gemma
&lt;/h3&gt;

&lt;p&gt;The application connects to Ollama's local API to generate reflective questions. Gemma (gemma4:e4b) is the default model, but the model is configurable so users can experiment with other models supported by their local Ollama setup.&lt;/p&gt;

&lt;p&gt;I wrote a dedicated system prompt to guide the AI's behavior. Instead of giving advice, judging productivity, or writing entries on the user's behalf, the model acts as a reflection companion. It generates one concise, context-aware question to help users explore their experiences, decisions, and lessons learned.&lt;/p&gt;

&lt;h3&gt;
  
  
  A Simple Journaling Workflow
&lt;/h3&gt;

&lt;p&gt;The application runs through a Python command-line interface. Users describe what they worked on or learned, receive a reflective question from the model, and can record their thoughts in response.&lt;/p&gt;

&lt;p&gt;Journal entries are saved as Markdown files, organized by year and month. This keeps the content human-readable, portable, and easy to use outside the application.&lt;/p&gt;

&lt;h3&gt;
  
  
  Built For Maintainability
&lt;/h3&gt;

&lt;p&gt;I separated the journaling logic from the command-line entry point, making the code easier to test and extend. I also added automated tests and GitHub Actions workflows for Python code quality and Markdown linting.&lt;/p&gt;

&lt;p&gt;My goal was to keep the core experience small and dependable: local AI to encourage reflection, plain-text files to preserve the user's writing, and a simple workflow that doesn't turn reflection into another productivity system.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;Personal reflections can include unfinished ideas, mistakes, and thoughts people may not want to send to a third-party service.&lt;/p&gt;

&lt;p&gt;Using an open-weight model locally gives users more control over where their journal entries are processed. It also lets developers experiment with different models instead of depending on a single proprietary AI provider.&lt;/p&gt;

&lt;p&gt;For me, open innovation isn't just about accessing a model. It's about having a freedom to explore how AI can support everyday human activities in ways that remain personal and meaningful.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Best Use of Gemma&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>gemma</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Dear Dev, What Are You Coming Back To? one-commit-a-day</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Mon, 12 Oct 2026 18:26:52 +0000</pubDate>
      <link>https://dev.to/neithergalax/dear-dev-what-are-you-coming-back-to-4lma</link>
      <guid>https://dev.to/neithergalax/dear-dev-what-are-you-coming-back-to-4lma</guid>
      <description>&lt;p&gt;I've been noticing more conversations lately about burnout, losing motivation, and starting over in tech.&lt;/p&gt;

&lt;p&gt;It's not just about being tired.&lt;/p&gt;

&lt;p&gt;Sometimes people still want to code. They still want to build things. They still want to be part of technology. But somehow, they don't know how to get back to it, or even what they are trying to get back to.&lt;/p&gt;

&lt;p&gt;And I think that's an important distinction.&lt;/p&gt;

&lt;p&gt;The usual advice for burnout is familiar:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Take a break&lt;/li&gt;
&lt;li&gt;Go for a walk&lt;/li&gt;
&lt;li&gt;Do some stretching and yoga&lt;/li&gt;
&lt;li&gt;Eat well and get enough sleep&lt;/li&gt;
&lt;li&gt;Spend time away from the computer&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqsvtlt72v17ac6r5gp08.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqsvtlt72v17ac6r5gp08.gif" alt="Logging Off" width="480" height="480"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;These things can absolutely help in the short term. Sometimes you really do need to step away and recover.&lt;/p&gt;

&lt;p&gt;But they don't necessary always resolve that deeper, unsettling feeling.&lt;br&gt;
You can rest and still feel restless.&lt;/p&gt;

&lt;p&gt;You can take time away and still wonder:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Why don't I feel motivated anymore?&lt;br&gt;
What am I actually coming back to?&lt;br&gt;
What do I want to do next?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Maybe the problem isn't always that we need another productivity system or another break. &lt;/p&gt;

&lt;p&gt;Maybe sometimes we need to reconnect with &lt;strong&gt;why we wanted to be here in the first place.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Consistency Isn't Enough
&lt;/h2&gt;

&lt;p&gt;This made me think about my own approach to staying involved in tech.&lt;/p&gt;

&lt;p&gt;When I started &lt;a href="https://yuka-with-data.github.io/one-commit-a-day/" rel="noopener noreferrer"&gt;One Commit a Day&lt;/a&gt; project, the idea was simple: Show up every day, Make a small contribution, and Keep moving forward.&lt;/p&gt;

&lt;p&gt;That helped me build consistency.&lt;/p&gt;

&lt;p&gt;But over time, I started asking a different question:&lt;/p&gt;

&lt;h3&gt;
  
  
  What am I actually showing up for?
&lt;/h3&gt;

&lt;p&gt;Because you can have a daily goal, a GitHub contribution, a learning plan, and a list of things to build, and still feel like you are moving without really knowing where you are going.&lt;/p&gt;

&lt;p&gt;Maybe the goal isn't always to find the next job, learn the next framework, or complete the next project.&lt;/p&gt;

&lt;p&gt;Sometimes we need to step back and ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Why am I in tech?&lt;/li&gt;
&lt;li&gt;What still interests me?&lt;/li&gt;
&lt;li&gt;What kind of problems do I want to solve?&lt;/li&gt;
&lt;li&gt;What do I want my technical work to mean?&lt;/li&gt;
&lt;li&gt;What kind of technical person do I want to become?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's what led me to add &lt;strong&gt;journaling and reflection to&lt;/strong&gt; &lt;code&gt;One Commit a Day v2.&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;The project is still about showing up and making meaningful contributions. But now there's another side to it: &lt;strong&gt;thinking about the direction behind those contributions.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not a perfect career plan.&lt;/p&gt;

&lt;p&gt;Not another productivity system.&lt;/p&gt;

&lt;p&gt;Just a space to pause, reflect, and reconnect with what matters.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0eygxjga7a5nx2438xao.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0eygxjga7a5nx2438xao.gif" alt="jounaling" width="480" height="270"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  From TO-DO to TO-BE
&lt;/h2&gt;

&lt;p&gt;This is where the idea of TO-BE came in for me.&lt;/p&gt;

&lt;p&gt;I was inspired by Japanese journaling approaches that focus on &lt;strong&gt;how you want to be&lt;/strong&gt;, not just what you want to accomplish.&lt;/p&gt;

&lt;p&gt;We spend a lot of time thinking about To-Do:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What do I need to get done today?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Learn this. Build this. Fix this issue. Apply for that job.&lt;/p&gt;

&lt;p&gt;Those things matter. But there is another layer of question that is easy to forget:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What kind of technical person do I want to become while doing all of these tasks?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That's the difference between TO-DO and TO-BE.&lt;/p&gt;

&lt;p&gt;To-Do is about what you need to accomplish.&lt;br&gt;
To-Be is about your direction, your values, and the kind of person you want to become.&lt;/p&gt;

&lt;p&gt;And I don't think To-Be needs to be perfect five-year career plan. It can simply be a way to pause and ask what still matters to you, especially when your circumstances change.&lt;/p&gt;

&lt;p&gt;That's one of the biggest changes in &lt;code&gt;One Commit a Day v2&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The project started as a simple framework for showing up and making small contributions. In v2, I added journals and reflections to give that consistency another dimension.&lt;/p&gt;

&lt;p&gt;There is now a Technical TO-BE Journal, along with journals for AI and Technology, and technical practice.&lt;/p&gt;

&lt;p&gt;The goal isn't to tell you what career path to choose.&lt;/p&gt;

&lt;p&gt;It is to give you a small space to step back and ask:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Why am I here? What matters to me? What do I want to move toward?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a href="https://yuka-with-data.github.io/one-commit-a-day/" rel="noopener noreferrer"&gt;One Commit a Day v2.&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Consistency helps us keep moving. But reflection can help us make sure we are moving in a direction that still feels like ours.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Are You Coming Back To?
&lt;/h2&gt;

&lt;p&gt;I don't have a perfect answer to these questions myself. That's part of why I build this.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;One Commit a Day v2&lt;/code&gt; is my attempt to create a little more space for that reflection alongside the act of showing up.&lt;/p&gt;

&lt;p&gt;If this idea resonates with you, take a look at &lt;code&gt;One Commit a Day&lt;/code&gt; and the new journaling features in v2. Maybe some of the questions will be useful for your own journey.&lt;/p&gt;

&lt;p&gt;And I'd love to hear from you:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What do you want to come back to?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fai09i332pkqihjmnxc2p.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fai09i332pkqihjmnxc2p.gif" alt="good morning" width="480" height="480"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>mentalhealth</category>
      <category>discuss</category>
      <category>devjournal</category>
      <category>motivation</category>
    </item>
    <item>
      <title>🎑September OSS Recap: 6 Months of "One Commit A Day"</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Wed, 30 Sep 2026 21:12:28 +0000</pubDate>
      <link>https://dev.to/neithergalax/september-oss-recap-6-months-of-one-commit-a-day-42fn</link>
      <guid>https://dev.to/neithergalax/september-oss-recap-6-months-of-one-commit-a-day-42fn</guid>
      <description>&lt;p&gt;September was a busy month, but I continued showing up and contributing at my own pace. &lt;strong&gt;It also marked 6 months of One Commit a Day!&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I've Worked On
&lt;/h2&gt;

&lt;p&gt;This month, I spent a lot of time working on One Commit a Day v2, including restructuring the repository, expanding the journal and templates, and releasing both v2.0 and v2.0.1.&lt;/p&gt;

&lt;p&gt;I also worked on Doc MCP Server, including restructuring and refactoring the project, and handled some Dependabot and MCP SDK maintenance in another OSS project.&lt;/p&gt;

&lt;p&gt;Outside of my own repositories, I participated in OSS discussions and started looking for a larger, active project where I can contribute more consistently.&lt;/p&gt;

&lt;p&gt;I also received &lt;strong&gt;recognition from GitHub&lt;/strong&gt; for one of my contributions, which was a nice milestone along the way.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I've Learned
&lt;/h2&gt;

&lt;p&gt;One thing that has become clearer over 6 months is that consistency doesn't necessarily mean working every day at the same intensity.&lt;/p&gt;

&lt;p&gt;September had plenty of Recovery Mode days. Life gets busy, and that's ok. The important part for me is continuing to show up without turning the commitment into another burden.&lt;/p&gt;

&lt;p&gt;Over the past six months, I've also learned a lot about open source by contributing to projects of different sizes and building my own projects, including MCP servers and an OSS contribution toolkit.&lt;/p&gt;

&lt;p&gt;I've become more comfortable with GitHub Actions, workflows, Dependabot, repository maintenance, and release processes.&lt;/p&gt;

&lt;p&gt;And most importantly, I've gained a stronger appreciation for documentation quality. It's easy to underestimate documentation, but good documentation is an important part of making a project understandable and usable.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fii1jo3s2w70v25nhpb26.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fii1jo3s2w70v25nhpb26.png" alt="6 months of github contribution" width="800" height="160"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  6 Months In
&lt;/h2&gt;

&lt;p&gt;6 months ago, I started &lt;strong&gt;&lt;a href="https://github.com/yuka-with-data/one-commit-a-day" rel="noopener noreferrer"&gt;One Commit a Day&lt;/a&gt;&lt;/strong&gt; simply to keep showing up. Since then, I've learned, contributed, built, experimented, and slowly become more involved in open source. Nothing necessarily feels easier yet, but &lt;strong&gt;showing up and staying consistent does seem to get easier over time&lt;/strong&gt;. That's the progress I am happy with.&lt;/p&gt;

&lt;h2&gt;
  
  
  Looking Ahead
&lt;/h2&gt;

&lt;p&gt;For the next 6 months, I want to get a foothold in a larger, active open source project that I can hopefully contribute to for the long term. At the same time, I want to keep developing my own projects toward something production-ready, whether that's a system, service, or application.&lt;/p&gt;

&lt;p&gt;I think I know what kind of technical person I want to become: someone who creates, contributes, and solves.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Transparency Note: I used AI as an editor—not as the author. For this article, it helped refine the structure and improve the English grammar. The technical content, experiments, opinions, and conclusions are my own and were reviewed by me before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>devjournal</category>
      <category>beginners</category>
      <category>github</category>
    </item>
    <item>
      <title>Smashing the MCP + Skill Tradeoff: More Guidance, Better Agents?</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Sat, 22 Aug 2026 22:41:43 +0000</pubDate>
      <link>https://dev.to/neithergalax/smashing-the-mcp-skill-tradeoff-more-guidance-better-agents-2g21</link>
      <guid>https://dev.to/neithergalax/smashing-the-mcp-skill-tradeoff-more-guidance-better-agents-2g21</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for &lt;a href="https://dev.to/bugsmash"&gt;DEV's Summer Bug Smash: Clear the Lineup&lt;/a&gt; powered by &lt;a href="https://sentry.io/" rel="noopener noreferrer"&gt;Sentry&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Overview
&lt;/h2&gt;

&lt;p&gt;I've been working on a Tokyo public transit MCP server for a while (see the previous posts in the series). Recently, I started experimenting with adding a &lt;code&gt;SKILL.md&lt;/code&gt; to see whether giving the agent more structured guidance would improve its behavior and output. &lt;/p&gt;

&lt;p&gt;Instead of treating this as simply another feature, I turned the project into a small debugging and experimentation exercise of &lt;strong&gt;How MCP tools and Skills work together, and adding another layer of guidance actually makes an agent better (or worse)&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;At a high level, MCP provides the agent with capabilities and tools, while a Skill provides task-specific guidance for when and how those capabilities should be used.&lt;/p&gt;

&lt;p&gt;The goal was simple: produce more accurate, consistent, and useful real-time transit answers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;The MCP tools themselves worked correctly, but introducing the Skill layer caused unexpected changes in agent behavior. In some cases, the agent even started preferring web search over the MCP tools.&lt;/p&gt;

&lt;p&gt;Nothing crashed down to the ground, but the problem was a silent change in the agent's decision path.&lt;/p&gt;

&lt;h2&gt;
  
  
  Experimenting and Evaluating
&lt;/h2&gt;

&lt;p&gt;I tested the same transit requests &lt;strong&gt;With Skill&lt;/strong&gt; and &lt;strong&gt;Without Skill&lt;/strong&gt;, then compared the outputs.&lt;/p&gt;

&lt;p&gt;I looked at tool usage, route selection, transfers, travel time, fares, and overall output quality across 6 progressively more complex evaluations.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Evaluation Results
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Eval&lt;/th&gt;
&lt;th&gt;Query Type&lt;/th&gt;
&lt;th&gt;With Skill vs Without Skill&lt;/th&gt;
&lt;th&gt;Current Finding&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Simple station-to-station route&lt;/td&gt;
&lt;td&gt;Nearly identical&lt;/td&gt;
&lt;td&gt;Little measurable Skill impact&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Station → attraction route&lt;/td&gt;
&lt;td&gt;Very similar&lt;/td&gt;
&lt;td&gt;MCP already handles the task well&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Station → landmark route&lt;/td&gt;
&lt;td&gt;Identical&lt;/td&gt;
&lt;td&gt;Little measurable Skill impact&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Natural-language, more complex route request&lt;/td&gt;
&lt;td&gt;Different routes&lt;/td&gt;
&lt;td&gt;Skill changed behavior, but selected a less optimal route&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Route request with explicit transfer preference&lt;/td&gt;
&lt;td&gt;Different routes&lt;/td&gt;
&lt;td&gt;Skill better aligned the route with the user's preference&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Time-sensitive route planning&lt;/td&gt;
&lt;td&gt;Identical&lt;/td&gt;
&lt;td&gt;MCP handled the task well; Skill had no measurable impact&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What the Evaluations Revealed
&lt;/h2&gt;

&lt;p&gt;The results challenged my initial assumption that adding a Skill layer would automatically produce better or more optimized outputs.&lt;/p&gt;

&lt;p&gt;For simple tasks, Eval 1-3 showed little difference between With and Without Skill. The MCP tools were already capable of handling these requests well. &lt;/p&gt;

&lt;p&gt;Eval 4 was the first surprise. The Skill changed the route selection, but the result was actually less optimal.&lt;/p&gt;

&lt;p&gt;Eval 5 showed the opposite. When the user explicitly asked to minimize transfers, the Skill helped align the agent's route selection with that preference.&lt;/p&gt;

&lt;p&gt;Eval 6 added another interesting result. For time-sensitive arrival planning, both versions produced the same result using the same MCP capability. In this case, the Skill did not provide a measurable benefit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Takeaway: What I Learned
&lt;/h2&gt;

&lt;p&gt;The good news is that the MCP tools were already capable of handling station-to-station routing, attraction and landmark routing, and time-sensitive arrival planning without an additional guidance layer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Adding guidance is not automatically an improvement.&lt;/strong&gt; Its value depends on the task, the underlying tools, and how the Skill itself is defined.&lt;/p&gt;

&lt;p&gt;More instructions don't necessarily mean better agent behavior. Sometimes the best improvement might be knowing when not to add another layer.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next
&lt;/h2&gt;

&lt;p&gt;This experiment is not finished yet.&lt;/p&gt;

&lt;p&gt;Next, I want to expand the eval suite with more complex requests that combine time constraints, transfer preferences, and fare limitations. The goal is to identify where the Skill can actually improve route optimization rather than simply change agent behavior.&lt;/p&gt;

&lt;p&gt;Once I understand where the Skill adds value, I'll refine &lt;code&gt;SKILL.md&lt;/code&gt; and rerun the evaluations against the baseline.&lt;/p&gt;

&lt;p&gt;I also plan to introduce Google ADK-based evaluation and tracing to look deeper into tool selection and agent behavior beyond final-output comparison.&lt;/p&gt;

&lt;h2&gt;
  
  
  Closing Thoughts
&lt;/h2&gt;

&lt;p&gt;The "Bug" wasn't a broken MCP tool. The tools were working.&lt;/p&gt;

&lt;p&gt;The unexpected behavior came from adding another layer of guidance and changing the agent's decision path.&lt;/p&gt;

&lt;p&gt;That turned out to be a more interesting problem to investigate than simply fixing a broken tool. &lt;/p&gt;

&lt;p&gt;In agent systems, adding more intelligence doesn't necessarily mean getting better results. Sometimes the real challenge is making sure the layers work together.&lt;/p&gt;

&lt;h2&gt;
  
  
  Project Link
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/yuka-with-data/tokyo-transportation-mcp-server" rel="noopener noreferrer"&gt;Repo Link&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;Transparency Note: I used AI as an editor, not as the author. For this article, it helped refine the structure and improve the English grammar. The technical content, experiments, opinions, and conclusions are my own and were reviewed by me before publishing.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>bugsmash</category>
      <category>devjournal</category>
      <category>agentskills</category>
    </item>
    <item>
      <title>🚤OS July 2026 Recap: From Being Intimidated by GitHub Actions to Building My Own CI Workflows</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Fri, 31 Jul 2026 00:29:02 +0000</pubDate>
      <link>https://dev.to/neithergalax/os-july-2026-recap-from-being-intimidated-by-github-actions-to-building-my-own-ci-workflows-1bdp</link>
      <guid>https://dev.to/neithergalax/os-july-2026-recap-from-being-intimidated-by-github-actions-to-building-my-own-ci-workflows-1bdp</guid>
      <description>&lt;p&gt;When I first started contributing to open source, &lt;code&gt;GitHub Actions&lt;/code&gt; felt like a black box. &lt;/p&gt;

&lt;p&gt;Seeing a failed workflow on my pull requests was intimidating because I didn't really understand what was happening behind the scenes.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Well, this month, I decided to change that.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Worked On
&lt;/h2&gt;

&lt;p&gt;I implemented GitHub Actions across three of my project repos.&lt;/p&gt;

&lt;p&gt;My main focus was:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Adding &lt;code&gt;Markdownlint&lt;/code&gt; for Markdown quality&lt;/li&gt;
&lt;li&gt;Adding &lt;code&gt;Pylint&lt;/code&gt; for Python linting.&lt;/li&gt;
&lt;li&gt;Updating documentation while integrating CI.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I Learned
&lt;/h2&gt;

&lt;p&gt;The biggest lesson wasn't technical — it was changing my mindset.&lt;/p&gt;

&lt;p&gt;A failed workflow isn't something to fear.&lt;br&gt;
It's simple feedback.&lt;br&gt;
Whether it's markdownlint warning or a pylint error, each failure helps improve the project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Looking Ahead
&lt;/h2&gt;

&lt;p&gt;Most of this month was spent improving my own projects, so I didn't contribute much to external repositories.&lt;/p&gt;

&lt;p&gt;Next month, I want to build on this foundation by contributing to more open source projects and applying what I've learned.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sometimes, learning the tools behind open source is just as valuable as making another pull request.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn0z8caci4e8dz4p2vm30.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn0z8caci4e8dz4p2vm30.png" alt="July 2026 Contribution Graph" width="800" height="128"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  I'm curious
&lt;/h3&gt;

&lt;p&gt;What part of GitHub Actions or CI/CD was the most challenging when you first started?&lt;/p&gt;

&lt;p&gt;Or&lt;/p&gt;

&lt;p&gt;If you are just getting started, what's the biggest thing that's still a mystery to you?&lt;/p&gt;

&lt;p&gt;I'd love to hear your experience and tips in the comments.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Transparency Note: I used AI as an editor—not as the author. For this article, it helped refine the structure and improve the English grammar. The technical content, experiments, opinions, and conclusions are my own and were reviewed by me before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>devjournal</category>
      <category>githubactions</category>
      <category>beginners</category>
    </item>
    <item>
      <title>I Contributed To a TypeScript Project Without Being a TS Dev</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Wed, 29 Jul 2026 07:46:31 +0000</pubDate>
      <link>https://dev.to/neithergalax/i-contributed-to-a-typescript-project-without-being-a-ts-dev-428k</link>
      <guid>https://dev.to/neithergalax/i-contributed-to-a-typescript-project-without-being-a-ts-dev-428k</guid>
      <description>&lt;p&gt;I have contributed to open source projects before, mostly in Python and in environments and languages I am familiar with.&lt;/p&gt;

&lt;p&gt;This time was different.&lt;/p&gt;

&lt;p&gt;The repository was written in &lt;strong&gt;TypeScript&lt;/strong&gt;, a language I had only limited experience with. I could understand the general structure, follow the logic, and get a rough picture of how things worked—but I was definitely not a TypeScript developer.&lt;/p&gt;

&lt;p&gt;That made this contribution interesting.&lt;/p&gt;

&lt;p&gt;Could I still make a meaningful contribution to a project when I did not fully know the language?&lt;/p&gt;

&lt;h2&gt;
  
  
  It started with a small bug, not a big feature
&lt;/h2&gt;

&lt;p&gt;The reason I looked into this repository was actually pretty simple.&lt;/p&gt;

&lt;p&gt;I noticed a small bug in a typing animation generator project. The generated animation was not printing as smoothly as expected, and I thought it would be a nice improvement to fix that experience.&lt;/p&gt;

&lt;p&gt;It was not a major architectural change or a large feature request.&lt;/p&gt;

&lt;p&gt;It was just a small issue that bothered me as a user.&lt;/p&gt;

&lt;p&gt;That is one of the things I enjoy about open source: sometimes a contribution starts from a simple thought:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Could this work a little better?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;So I opened an issue, described the problem, and shared my thoughts.&lt;/p&gt;

&lt;p&gt;I expected the discussion to stay at the issue level.&lt;/p&gt;

&lt;p&gt;Instead, the maintainer asked:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Would you like to fix this issue?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;My reaction was simple:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;"Why not?"&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;So I started working on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Learning a new codebase with AI as a companion
&lt;/h2&gt;

&lt;p&gt;I used Codex throughout the process.&lt;/p&gt;

&lt;p&gt;But the goal was not to ask AI to generate code and blindly submit it.&lt;/p&gt;

&lt;p&gt;I used it as a learning partner:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Understanding unfamiliar TypeScript patterns&lt;/li&gt;
&lt;li&gt;Exploring the repository structure&lt;/li&gt;
&lt;li&gt;Discussing possible implementation approaches&lt;/li&gt;
&lt;li&gt;Reviewing my own assumptions&lt;/li&gt;
&lt;li&gt;Helping translate my existing engineering knowledge into a new ecosystem&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;AI helped reduce the friction of entering an unfamiliar codebase, but I still needed to understand the problem, make decisions, and validate the final implementation.&lt;/p&gt;

&lt;p&gt;The contribution was not:&lt;/p&gt;

&lt;p&gt;"I know TypeScript now."&lt;/p&gt;

&lt;p&gt;It was:&lt;/p&gt;

&lt;p&gt;"I understand this problem well enough to improve this project."&lt;/p&gt;

&lt;h2&gt;
  
  
  When AI reviewers disagreed with my implementation
&lt;/h2&gt;

&lt;p&gt;After submitting the PR, I received feedback from several AI-powered code reviewers.&lt;/p&gt;

&lt;p&gt;One suggestion caught my attention. The checker recommended changing my implementation slightly.&lt;/p&gt;

&lt;p&gt;At first glance, the suggestion looked reasonable.&lt;/p&gt;

&lt;p&gt;But instead of immediately accepting it, I investigated.&lt;/p&gt;

&lt;p&gt;I discussed the feedback with Codex, reviewed the surrounding code, checked the existing tests, and looked deeper into the design intention behind the change.&lt;/p&gt;

&lt;p&gt;After that investigation, I decided not to make the suggested change.&lt;/p&gt;

&lt;p&gt;I explained my reasoning in the PR:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Why the original implementation matched the existing project structure&lt;/li&gt;
&lt;li&gt;Why the suggested change was not necessary&lt;/li&gt;
&lt;li&gt;How the tests supported the current approach&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This was a small but meaningful moment.&lt;/p&gt;

&lt;p&gt;AI review is valuable, but it is still feedback—not an automatic decision.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The responsibility of engineering judgment remains with the contributor.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The result surprised me
&lt;/h2&gt;

&lt;p&gt;Eventually, the AI review passed, the maintainer approved my original implementation, and the PR was merged.&lt;/p&gt;

&lt;p&gt;The interesting part was not that AI wrote code for me.&lt;/p&gt;

&lt;p&gt;The interesting part was that AI helped me participate in a project where I previously would have hesitated because of the language barrier.&lt;/p&gt;

&lt;p&gt;This experience also changed how I viewed TypeScript.&lt;/p&gt;

&lt;p&gt;Instead of seeing it as an unfamiliar language that was "not mine," &lt;strong&gt;I became more interested in learning it further.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Sometimes the best way to learn a technology is not through tutorials.&lt;/p&gt;

&lt;p&gt;Sometimes it is by trying to contribute something meaningful with it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Open source contribution is evolving
&lt;/h2&gt;

&lt;p&gt;Traditionally, contributing to a project often felt like:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I need to already know this technology before I can help."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;But that barrier is starting to change.&lt;/p&gt;

&lt;p&gt;The important skills are becoming:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Understanding problems&lt;/li&gt;
&lt;li&gt;Reading unfamiliar systems&lt;/li&gt;
&lt;li&gt;Asking good questions&lt;/li&gt;
&lt;li&gt;Validating ideas&lt;/li&gt;
&lt;li&gt;Communicating clearly with maintainers&lt;/li&gt;
&lt;li&gt;Knowing when to trust or challenge suggestions—including AI suggestions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The fundamentals of engineering have not changed.&lt;/p&gt;

&lt;p&gt;We still need curiosity, judgment, and the ability to adapt.&lt;/p&gt;

&lt;p&gt;But the tools available to us have changed.&lt;/p&gt;

&lt;p&gt;Maybe the future open source contributor is not someone who knows every language.&lt;/p&gt;

&lt;p&gt;Maybe it is someone who can continuously learn, collaborate, and contribute—even when stepping into unfamiliar territory.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Have you ever contributed to a project outside your main programming language or comfort zone?&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;Transparency Note: I used AI as an editor—not as the author. For this article, it helped refine the structure and improve the English grammar. The technical content, experiments, opinions, and conclusions are my own and were reviewed by me before publishing.&lt;/p&gt;

</description>
      <category>typescript</category>
      <category>opensource</category>
      <category>devjournal</category>
      <category>codenewbie</category>
    </item>
    <item>
      <title>The OSS Toolkit: How Will We Become Open Source Contributors In an AI-Assisted World?</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Fri, 17 Jul 2026 20:53:00 +0000</pubDate>
      <link>https://dev.to/neithergalax/how-will-we-become-open-source-contributors-in-an-ai-assisted-world-the-oss-toolkit-1m01</link>
      <guid>https://dev.to/neithergalax/how-will-we-become-open-source-contributors-in-an-ai-assisted-world-the-oss-toolkit-1m01</guid>
      <description>&lt;p&gt;Open source contribution has never been just about writing code.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;As AI changes how we build software, how will contribution change too?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I've been thinking about this question a lot recently. The pull request I opened to add AI-assisted contribution guidance to &lt;a href="https://opensource.guide/" rel="noopener noreferrer"&gt;GitHub's open source guides&lt;/a&gt; was &lt;strong&gt;recently merged&lt;/strong&gt;😆, and around the same time, I was building my own OSS Contribution Toolkit on GitHub.&lt;/p&gt;

&lt;p&gt;Both experiences made me reflect on how quickly open source contribution is evolving.&lt;/p&gt;

&lt;h2&gt;
  
  
  My First Open Source Contribution Experience
&lt;/h2&gt;

&lt;p&gt;When I first started exploring open source, I often felt intimidated by the contribution process.&lt;/p&gt;

&lt;p&gt;The challenge wasn't always writing the code. It was understanding how each project worked.&lt;/p&gt;

&lt;p&gt;Every repository seemed to have its own workflows, expectations, and unwritten rules. On top of that, I had a bit of &lt;/p&gt;

&lt;h3&gt;
  
  
  Git Anxiety
&lt;/h3&gt;

&lt;h4&gt;
  
  
  the fear of making a mistake with branches, commits, or pull requests in someone else's project.
&lt;/h4&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmnxd54pkztba32nu2rq8.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmnxd54pkztba32nu2rq8.gif" alt="Awkward Git Pull" width="480" height="480"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Even today, that feeling hasn't completely disappeared. Every open source project is different, and there's always a learning curve before making a meaningful contribution.&lt;/p&gt;

&lt;p&gt;Looking back, I realized that contributing to open source has never been just about writing code.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Current State of Open Source Contribution
&lt;/h2&gt;

&lt;p&gt;As I contributed to more projects, I realized this wasn't unique to my experience.&lt;/p&gt;

&lt;p&gt;Open source projects naturally evolve their own contribution workflows over time. Guidance is often spread across &lt;code&gt;README&lt;/code&gt; files, &lt;code&gt;CONTRIBUTING&lt;/code&gt; guides, issue and pull request templates, GitHub Actions, and other automation tools. These expectations continue to evolve as projects grow and maintainers refine their processes.&lt;/p&gt;

&lt;p&gt;As a result, every project has its own conventions and contribution patterns. &lt;/p&gt;

&lt;p&gt;For contributors—especially those just getting started—understanding the contribution process can sometimes take more effort than understanding the code itself.&lt;/p&gt;

&lt;p&gt;In many ways, contributing to open source is about learning the project's context before writing the first line of code.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I Built an OSS Contribution Toolkit
&lt;/h2&gt;

&lt;p&gt;This realization motivated me to build an &lt;a href="https://github.com/yuka-with-data/oss-contribution-toolkit" rel="noopener noreferrer"&gt;&lt;em&gt;OSS Contribution Toolkit&lt;/em&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The goal isn't to replace project-specific documentation or workflows. Every open source project is unique and diverse, and contributors should always follow each project's own guidelines.&lt;/p&gt;

&lt;p&gt;Instead, I wanted to collect common contribution patterns, workflows, and lessons learned from real-world contributions into a practical resource.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My hope is that contributors can spend less time figuring out &lt;em&gt;how&lt;/em&gt; to contribute and more time making meaningful contributions.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Like open source itself, this toolkit will continue to evolve. As projects adopt new practices and AI-assisted workflows become more common, I plan to keep it updated to reflect how open source contribution continues to change.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8ioosdbfe1g2b41z36p7.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8ioosdbfe1g2b41z36p7.gif" alt="it's open source" width="480" height="480"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Looking Ahead
&lt;/h2&gt;

&lt;p&gt;As AI-assisted development continues to evolve, I can't help but wonder how open source contribution will evolve alongside it.&lt;/p&gt;

&lt;p&gt;Today, AI can already help us write code, explain unfamiliar repositories, generate tests, draft documentations, and even create pull requests.&lt;/p&gt;

&lt;p&gt;Perhaps the next step isn't just helping us write better code, but helping us become &lt;strong&gt;better contributors&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Understanding:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a project's context&lt;/li&gt;
&lt;li&gt;workflows&lt;/li&gt;
&lt;li&gt;collaboration patterns&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;will likely remain an essential part of open source.&lt;/p&gt;

&lt;p&gt;And perhaps we should also remember that contribution doesn't have to start big. &lt;strong&gt;Small, focused contributions matter too.&lt;/strong&gt; Fixing a typo, improving documentation, clarifying an example, or addressing a small issue can make a real difference to a project and its community.&lt;/p&gt;

&lt;p&gt;Starting small can also be a great way to understand a project's codebase, learn its workflows, and gradually become a more confident contributor.&lt;/p&gt;

&lt;p&gt;The tools may change, but meaningful contribution is still about working effectively with both the code and community of developers.&lt;/p&gt;

&lt;p&gt;I am excited to see where open source goes next, and I hope this toolkit can evolve alongside it.&lt;/p&gt;

&lt;p&gt;Now I'm curious—&lt;strong&gt;What do you think open source contribution will look like in the next few years?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;🔗&lt;a href="https://github.com/yuka-with-data/oss-contribution-toolkit" rel="noopener noreferrer"&gt;OSS Contribution Toolkit Repo&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Transparency Note:&lt;/strong&gt; I used AI as an editor—not as the author. For this article, it helped refine the structure and improve the English grammar. The technical content, experiments, opinions, and conclusions are my own and were reviewed by me before publishing.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>github</category>
      <category>ai</category>
      <category>devjournal</category>
    </item>
    <item>
      <title>[MCP &amp; Skill.md] I Rolled Back My MCP Skills Experiment. Here's What I Learned</title>
      <dc:creator>neitherGalax</dc:creator>
      <pubDate>Wed, 08 Jul 2026 19:23:15 +0000</pubDate>
      <link>https://dev.to/neithergalax/i-rolled-back-my-mcp-skills-experiment-heres-what-i-learned-gje</link>
      <guid>https://dev.to/neithergalax/i-rolled-back-my-mcp-skills-experiment-heres-what-i-learned-gje</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;TL;DR&lt;br&gt;
I introduced a SKILL layer while improving fare extraction in a MCP-based transit agent. After that, the agent stopped reliably using the MCP tool and started favoring web search, breaking real-time accuracy. I rolled back to a stable baseline, reintroduced SKILL more carefully, and restored MCP tool usage. &lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a href="https://dev.to/neithergalax/from-prompt-engineering-to-mcp-skills-what-rebuilding-my-tokyo-transit-agent-taught-me-about-ai-2p59"&gt;After the last post&lt;/a&gt;, the system felt stable.&lt;/p&gt;

&lt;p&gt;The MCP-based transit agent was working. Fare retrieval was consistent, routes were predictable, and tool calls behaved the way I expected. It felt like I had finally reached a baseline I could build on.&lt;/p&gt;

&lt;p&gt;Then I started iterating again.&lt;/p&gt;

&lt;p&gt;The goal was still narrow. I was trying to improve fare extraction for more complex routes. Before introducing any new abstraction, I actually modified the MCP tool itself. I adjusted parts of the parsing logic to better handle complex route structures.&lt;/p&gt;

&lt;p&gt;That change alone did not break anything immediately, but it shifted the foundation slightly.&lt;/p&gt;

&lt;p&gt;After that, I introduced a SKILL layer to structure how the agent should use MCP tools. At the time, it felt like a logical next step. The idea was to make tool usage more consistent and less dependent on implicit behavior from the agent. &lt;/p&gt;

&lt;p&gt;Nothing broke immediately. The system still ran, responses still came back, and at a glance everything looked fine.&lt;/p&gt;

&lt;p&gt;But I had effectively changed two layers that depend on each other without fully understanding how they would interact.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Failure Signal (What Broke)
&lt;/h2&gt;

&lt;p&gt;The first sign was not an error.&lt;/p&gt;

&lt;p&gt;It was a shift in where answers were coming from.&lt;/p&gt;

&lt;p&gt;The agent started relying on backup web search instead of the MCP transit tool. This was not limited to fare extraction. Even for basic transit queries, the MCP tool was no longer being used, and the responses were coming from general web-based results instead of real-time transit data.&lt;/p&gt;

&lt;p&gt;I tried to correct it at the SKILL layer.&lt;/p&gt;

&lt;p&gt;I adjusted the instructions, made the tool usage more explicit, and expected the behavior to shift back. But the pattern stayed the same. The agent continued to avoid the MCP tool, even when the intent clearly required real-time transit information.&lt;/p&gt;

&lt;p&gt;That is when it became obvious that the output was no longer grounded in the system I built. It was producing responses, but not based on the real-time transit pipeline anymore.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Point of Uncertainty (And My Frustration)
&lt;/h2&gt;

&lt;p&gt;At this point, I did not know which layer was responsible.&lt;/p&gt;

&lt;p&gt;The MCP tool still worked when called directly. The SKILL layer still looked correct in isolation. Even the parsing changes I had made earlier did not clearly explain the behavior I was seeing.&lt;/p&gt;

&lt;p&gt;But the system behavior told a different story.&lt;/p&gt;

&lt;p&gt;The agent consistently avoided the MCP tool, and even adjustments in the SKILL instructions did not change that. It kept producing answers that were not grounded in real-time transit data.&lt;/p&gt;

&lt;p&gt;It felt less like a single bug and more like a breakdown in coordination between layers that were supposed to work together.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Rollback and What Changed
&lt;/h2&gt;

&lt;p&gt;At this point, I stopped trying to patch it.&lt;/p&gt;

&lt;p&gt;Nothing I changed was bringing the MCP tool back in consistent use anymore. The agent was still bypassing it, and the output was still not grounded in real-time transit data. The SKILL layer had not improved control, and it made the behavior harder to reason about.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;So, I rolled everything back to &lt;code&gt;v0.1.1&lt;/code&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That meant returning to the simpler parsing logic in the MCP tool and removing the expanded SKILL-driven behavior. I wanted a baseline where I already knew the system behaved correctly.&lt;/p&gt;

&lt;p&gt;Then, I reintroduced SKILL, but only in a minimal form, closer to the original intent rather than an orchestration layer that tried to do too much.&lt;/p&gt;

&lt;p&gt;After testing again, the behavior stabilized.&lt;/p&gt;

&lt;p&gt;The agent started using the MCP tool reliably again. Fare retrieval worked. Even some complex routing cases began working better than before.&lt;/p&gt;

&lt;p&gt;It is not fully perfect. There are still edge cases that break. But compared to everything before this point, it is in a much more stable state.&lt;/p&gt;

&lt;p&gt;My working hypothesis is that the regression was not in the MCP server itself, but somewhere in the interaction between the SKILL layer, tool selection, and my parsing changes.&lt;/p&gt;

&lt;p&gt;This is still something I am iterating on.&lt;/p&gt;

&lt;p&gt;What I learned from this round is that SKILL only behaves well when it stays close to orchestration. Once it starts influencing tool selection too strongly, it becomes harder to predict how the agent will actually behave. &lt;/p&gt;

&lt;p&gt;This is the version I ended up tagging.&lt;/p&gt;

&lt;h2&gt;
  
  
  Closing Insight
&lt;/h2&gt;

&lt;p&gt;I think the issue was not the MCP tool itself. It was how additional layers influenced when it got used. SKILL is not a system prompt replacement, but an orchestration layer that can unintentionally affect tool selection. In my case, that interaction changed the agent's routing behavior in subtle ways.&lt;/p&gt;

&lt;p&gt;Rolling back restored a simpler, more predictable decision path, which is why the system stabilized again. &lt;/p&gt;

&lt;h3&gt;
  
  
  For More Info About This Project
&lt;/h3&gt;

&lt;p&gt;🔗&lt;a href="https://dev.to/neithergalax/tokyo-transit-how-mcp-helped-me-fix-a-broken-multi-agent-system-cpe"&gt;GitHub Finish-Up-A-Thon Challenge post&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🔗&lt;a href="https://github.com/yuka-with-data/tokyo-transportation-mcp-server" rel="noopener noreferrer"&gt;GitHub Repo&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Transparency Note: I used AI as an editor, not as the author. For this article, it helped refine the structure and improve the English grammar. The technical content, experiments, opinions, and conclusions are my own and were reviewed by me before publishing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>ai</category>
      <category>devjournal</category>
      <category>agentskills</category>
    </item>
  </channel>
</rss>
