@Algorixx Me too, I've observed most of the shows starting in the late 2000's till the early 2010's have immaculate writing, House MD, Breaking Bad, Sherlock, GOT, Mentalist, Fringe etc
@PrachiPreyasi@matiks_play Wait, I think you misread the caption.
I ordered the cake last year fresh and it came the same day, there wasn't any issue.
I just meant I'm redeeming the 50 days gift after the 100 days gift, that's all.
I wasn't complaining or anything of that sort 😭
Coding agents like Claude Code and others love Git worktrees. So, if you are using one or trying to build one, knowing about them is important, and here is what they are all about.
A Git worktree lets you check out multiple branches of the same repository at the same time, each in its own directory. Not multiple clones. So essentially, one repo, many working directories, all sharing the same Git history and objects on disk.
The problem they solve is context switching. Normally, if you are midway through work on one branch and need to jump to another, you stash, switch, do the work, switch back, and pop the stash. That context gets destroyed. With worktrees, you just open the other directory. Both branches stay live simultaneously.
For coding agents, this is a 'godsend' :) It is how they run tasks in parallel without interfering with each other. An agent can be running tests on one branch in one worktree while writing new code in another. No waiting required, and things can move in parallel.
Also, each worktree gets its own working tree and index, but they share the object store. So you are not actually duplicating gigabytes of history every time you spin one up. It is fast to create and cheap to maintain.
You create one with `git worktree add ../feature-branch feature-branch`. That is it. The directory is ready, the branch is checked out, and your original workspace is untouched.
Coding agents also get isolation guarantees. If one task crashes or corrupts its working tree, the others are unaffected. This makes Git worktrees a pretty natural fit for any system that needs to run concurrent, independent operations on the same codebase - aka coding agents :)
Hope this helps.