Konstantin

One of the most important features of git in terms of AI is git worktree. It allows you to checkout different branches at the same time in different folders like so:

git worktree add <branch> path

And all worktrees share the common stash list between them. This is crucial for AI use in projects where you might be running a long training job in one worktree, while simultaneously preprocessing data in another, and fixing a bug in code in a third—all without conflicts or context switching.

One of the big drawbacks of git worktree in my opinion was always unintuitive syntax, where I always would have to look up how to do a specific thing.

#My solution: gwt

To fix this, I created gwt, a simple helper that makes git worktree intuitive. Once installed you can simply type:

gwt

To list all available worktrees.

#Before gwt

You would have to git worktree list → copy the path → cd ../../path/to/the-other-feature.

#With gwt

Just run gwt and choose the branch and you’re there.

gwt add <branch> would automatically create a new worktree with checked out branch.

If you already know the branch’s worktree you want to jump into you can simply type gwt <branch>. Gwt supports autocomplete for branch names.

And finally gwt remove interactively prompts you to choose which worktree to delete.

Introducing Old Book: A new theme for Vscode, Vim, and Zed, crafted from the warm, nostalgic colours inspired by the feel of scanned vintage books. The result is a light theme designed to reduce eye strain, making long coding sessions more comfortable.

#Vscode theme

Install from the VS Code Marketplace

#Zed theme

Install from Zed Extensions

#Vim & Neovim

#Install

Simply add it like so in your .vimrc, for vim-plug:

Plug 'gko/oldbook-theme'

packer.nvim:

use 'gko/oldbook-theme'

lazy.nvim:

{ 'gko/oldbook-theme', lazy = false, priority = 1000 }

#Activate

Add this command to your config. For .vimrc:

colorscheme oldbook

For init.lua:

vim.cmd('colorscheme oldbook')

Found a bug or want to contribute? The source code is available on GitHub.

Every project starts with a clean vision: a tool to solve a problem. You see the finished product clearly—that elegant solution to organize your thoughts, manage your tasks, and publish your articles.

But progress is rarely a straight line. You start noticing the small imperfections, becoming invested in polishing user paths and refining feature lists. Suddenly, the platform’s final goal shifts. It begins to accommodate the development of the platform itself.

You find yourself running checklists for new releases inside the app. You start designing a «publish later» feature that doubles as a personal to-do list for your own announcements.

It’s a strange loop to be in—one that is as fascinating and reassuring as it is subtly demotivating.

Deep work has a side effect: clutter. The more focused I am, the more browser tabs, terminal windows, and random apps seem to accumulate on my screen. Recently, I’ve been relying on two shortcuts to instantly clear the decks:

• to focus on a single file in VS Code, I use ⌘⌥t. It closes every other tab, leaving just the one I’m working on. It feels like a reset button.
• to hide all other app windows in macOS, I use ⌘⌥h. It hides everything except my active window.

This is also a good chance to show off the new <kbd> tag design I recently added, which makes sharing shortcuts much cleaner.

Finally back to running after taking time off to finish the very thing you’re reading this on.

Zametka is still a long way from being completed—only about a quarter of the roadmap is implemented. But I needed to get it to a «workable» state so that I could actually start posting here.

This way, I can share updates while I implement the rest of the roadmap (and work on other projects as well). So, double fun!

Les Grands Moulins building

Tours DUO with a cool mirror 🪞/ zoom effect of passing cars.

P.S. It’s actually fun to use this thing on the go.

🙂