Tools on @zhisme :: signal over noise

Give Your LLM Brevity

Thu, 23 Apr 2026 00:00:00 +0000

Brevity is the Sister of Talent

A.P. Chekhov

Why?!

I don’t want to read invented machinery poems from an LLM about why it chose BigDecimal(0.5) instead of a literal 0.5 and writes 3 paragraphs defending a choice I didn’t ask about.
I don’t want to read invented nonsense that I have no time for.
If I don’t like something, I’ll ask to reimplement/refactor, or in rare cases request elaboration.
Then I will cover it with the needed tests until it satisfies me.
If you’re like me, you don’t want to spend time on that.

Multiple Git Configs Per Directory

Mon, 30 Mar 2026 00:00:00 +0000

The Problem

You have a personal GitHub and a work GitLab (or multiple work accounts). Your global ~/.gitconfig has your personal email. You clone a work repo, make a commit, push — and now your personal email is in the company git history. haha-haha classic..

You could run git config user.email in every new repo you clone. But you’ll forget. You always forget. But this is a boring routine, why do this?

Practical Useful Commands for Claude

Tue, 17 Mar 2026 00:00:00 +0000

These are commands I use often and see a lot of value from. I advise you at least to consider using them in case you haven’t tried them yet.

Commands

claude --worktree or claude -w

In case you want multiple agents to run simultaneously, this option was designed for it. Each Claude agent gets its own version of the repo so they won’t interfere with each other. Where can you use it? Let’s say you’re migrating something to a new architecture and there are multiple services that need changes, but they’re located in a monorepo. With this option, each agent will be moving its own service or “folder” if you want, without getting conflicts with others.

copy_with_context.nvim v3 Released

Mon, 24 Nov 2025 00:00:00 +0000

Previous post on original release is available at copy_with_context.nvim plugin released.

What’s New in v3

Automatic Repository URL Generation

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.

-- 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

What it does:

copy_with_context.nvim plugin released

Sun, 13 Apr 2025 00:00:00 +0000

I’m excited to announce the release of my new Neovim plugin, copy_with_context.nvim

When sharing code snippets, it’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 (what if it is long config file? it is boring). We can automate it and do not waste our time.

lazy_names gem, how much time do you spend in console?

Sun, 12 Jan 2020 00:00:00 +0000

I’m happy to share the lazy_names gem!
This gem allows you to define a config file that maps long, namespaced constants to something simpler and more intuitive:

'Models::Users::CreditCard': 'UserCard'

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:

$: history | awk '{$1=""; print $0}' | sort | uniq -c | sort -nr
 647 gs
 135 rc # rails console
 135 ls
 134 gd
 ...

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.