<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-Source on @zhisme :: signal over noise</title><link>https://zhisme.com/tags/open-source/</link><description>Recent content in Open-Source on @zhisme :: signal over noise</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://zhisme.com/tags/open-source/index.xml" rel="self" type="application/rss+xml"/><item><title>Not Best Time For An Open Source Contributions</title><link>https://zhisme.com/articles/not-best-time-for-open-source-contributions/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://zhisme.com/articles/not-best-time-for-open-source-contributions/</guid><description>&lt;p>If intro sounds like an existential crisis to you, then yes – it should!&lt;/p>
&lt;p>In the times before AI, there was a reason. You could add this to your CV and it would be valuable, someone could admire your work, find your PR, and even debate the decisions you made during an interview.&lt;br>
Some other resources, like the old Stack Overflow Jobs, allowed you to add your open-source contributions as widgets visible to anyone, and they had a very prominent place on that HTML page.&lt;/p></description></item><item><title>copy_with_context.nvim v3 Released</title><link>https://zhisme.com/articles/copy-with-context-v3-released/</link><pubDate>Mon, 24 Nov 2025 00:00:00 +0000</pubDate><guid>https://zhisme.com/articles/copy-with-context-v3-released/</guid><description>&lt;p>Previous post on original release is available at &lt;a href="https://zhisme.com/articles/copy-with-context-nvim">copy_with_context.nvim plugin released&lt;/a>.&lt;/p>
&lt;h2 id="whats-new-in-v3">What&amp;rsquo;s New in v3&lt;/h2>
&lt;h3 id="automatic-repository-url-generation">Automatic Repository URL Generation&lt;/h3>
&lt;p>The headline feature: when you copy code, the plugin now automatically includes a direct permalink to the code in your repository. No manual URL construction, no hunting for the right commit SHA—it just works.&lt;/p>
&lt;pre>&lt;code class="language-lua">-- When you copy this code, you get:
function authenticate(user)
 validate_credentials(user)
end

-- Output automatically includes:
-- app/controllers/auth_controller.rb:45-47
-- https://github.com/username/repo/blob/abc1234/app/controllers/auth_controller.rb#L45-L47
&lt;/code>&lt;/pre>
&lt;p>&lt;strong>What it does:&lt;/strong>&lt;/p></description></item><item><title>copy_with_context.nvim plugin released</title><link>https://zhisme.com/articles/copy-with-context-nvim/</link><pubDate>Sun, 13 Apr 2025 00:00:00 +0000</pubDate><guid>https://zhisme.com/articles/copy-with-context-nvim/</guid><description>&lt;p>I&amp;rsquo;m excited to announce the release of my new Neovim plugin, &lt;a href="https://github.com/zhisme/copy_with_context.nvim">copy_with_context.nvim&lt;/a>&lt;/p>
&lt;p>When sharing code snippets, it&amp;rsquo;s often useful to include the file path and line number for context. This plugin makes it easy to copy lines with this metadata. It is easier to understand the context of the code snippet when the file path and line number are included. Otherwise you have to do it manually. Copying snippet, then adding the line number &lt;em>(what if it is long config file? it is boring)&lt;/em>. We can automate it and do not waste our time.&lt;/p></description></item><item><title>lazy_names gem, how much time do you spend in console?</title><link>https://zhisme.com/articles/lazy-names/</link><pubDate>Sun, 12 Jan 2020 00:00:00 +0000</pubDate><guid>https://zhisme.com/articles/lazy-names/</guid><description>&lt;p>I&amp;rsquo;m happy to share the &lt;a href="https://github.com/zhisme/lazy_names?tab=readme-ov-file#lazy_names">lazy_names&lt;/a> gem!&lt;br>
This gem allows you to define a config file that maps long, namespaced constants to something simpler and more intuitive:&lt;/p>
&lt;pre>&lt;code class="language-yml">'Models::Users::CreditCard': 'UserCard'
&lt;/code>&lt;/pre>
&lt;p>I spend a lot of time in the console, which is why I originally wrote this gem. Here’s a quick look at my most frequently run commands from my Zsh history:&lt;/p>
&lt;pre>&lt;code class="language-sh">$: history | awk '{$1=&amp;quot;&amp;quot;; print $0}' | sort | uniq -c | sort -nr
 647 gs
 135 rc # rails console
 135 ls
 134 gd
 ...
&lt;/code>&lt;/pre>
&lt;p>Do you use the Ruby console much while developing? I personally like to check my code directly in the console — calling methods to inspect return values — especially in the early development stage before tests are written. Sometimes, I need to drop records from the database or build some structs on the fly.&lt;/p></description></item></channel></rss>