"version": "0.9.4",

# Can you solve the pirate riddle? - Alex Gendler

- **Category:** Video

- **Date:** 2026-01-08

- **Rating:** 5/5

- **Link:** [YouTube - Can you solve the pirate riddle?](https://www.youtube.com/watch?v=Mc6VA7Q1vXQ)

## The Video

<iframe width="560" height="315" src="https://www.youtube.com/embed/Mc6VA7Q1vXQ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

## About

It’s a resting day on the pirate ship. The five pirates: Amaro, Bart, Charlotte, Daniel, and Elizabeth have found a treasure chest with 100 gold coins. They must decide how to partition them.

Pirates are ranked by seniority: Amaro is #1, Bart is #2, Charlotte is #3, Daniel is #4, and Elizabeth is the most junior, #5.

The rules of pirate democracy are as follows: the most senior pirate proposes a distribution. Then, everyone, including the proposer, votes. If at least 50% of the pirates agree, the gold is distributed as proposed. If not, the proposer is thrown overboard, and the process starts again with the next most senior pirate.

Pirates are perfectly rational, but they also have a hierarchy of goals:

1. Stay alive.

2. Maximize their own gold.

3. If all else is equal, they prefer to see others thrown overboard.

Can you figure out what Amaro should propose?

## The Solution

To solve this, we work backward from the most junior pirates:

1. **Two Pirates (Daniel, Elizabeth):** Daniel needs only 50% of the vote. He votes for himself and wins. He takes all 100 coins, and Elizabeth gets 0.

2. **Three Pirates (Charlotte, Daniel, Elizabeth):** Charlotte needs one other vote. She knows Elizabeth will get 0 if it goes to Daniel's turn, so she offers Elizabeth 1 coin. Elizabeth accepts. Distribution: **99, 0, 1**.

3. **Four Pirates (Bart, Charlotte, Daniel, Elizabeth):** Bart needs one other vote. He knows Daniel gets 0 in Charlotte's plan, so he offers Daniel 1 coin. Daniel accepts. Distribution: **99, 0, 1, 0**.

4. **Five Pirates (Amaro, Bart, Charlotte, Daniel, Elizabeth):** Amaro needs two other votes besides his own. He knows Charlotte and Elizabeth both get 0 in Bart's plan. By offering them each 1 coin, they are better off and will vote with him.

**Final Proposal:**

- **Amaro:** 98 coins

- **Bart:** 0 coins

- **Charlotte:** 1 coin

- **Daniel:** 0 coins

- **Elizabeth:** 1 coin

> (item)

(category) Video

(date) 2026-01-08

(link) https://www.youtube.com/watch?v=Mc6VA7Q1vXQ

(rating) 5

(slug) can-you-solve-the-pirate-riddle

(title) Can you solve the pirate riddle? - Alex Gendler

(description) A classic logic riddle from TED-Ed about pirate democracy and rational self-interest.

# Resolving `spawn ENAMETOOLONG` in `gh-pages` Deployment

If you've been using the `gh-pages` package for a while, especially in projects with large build folders or complex structures, you might have encountered the dreaded `spawn ENAMETOOLONG` error when running your deploy script.

## The Problem

When executing the standard deployment command:

```bash

gh-pages -d build -b gh-pages

```

The process fails with a system error indicating that the argument list or the command path itself has exceeded the operating system's limits. This is often related to how the underlying `globby` or `async` dependencies handle file lists in older versions of the package (like `6.3.0`).

The issue is documented and discussed in detail here: [gh-pages Issue #585](https://github.com/tschaub/gh-pages/issues/585).

## The Fix

The specific fix for this issue was highlighted in [this GitHub comment](https://github.com/tschaub/gh-pages/issues/585#issuecomment-2585457896), which explains that the `ENAMETOOLONG` error occurs on Windows when the `rm` command receives an excessively long list of files as arguments.

``` git

diff --git a/lib/git.js b/lib/git.js

index d4c5724272d00bd1f0d76c47dab47d21ccd094d9..d86ac2b0bd7cbc02f34a50dac6980965102ee964 100644

--- a/lib/git.js

+++ b/lib/git.js

@@ -143,7 +143,7 @@ Git.prototype.rm = function (files) {

if (!Array.isArray(files)) {

files = [files];

}

- return this.exec('rm', '--ignore-unmatch', '-r', '-f', '--', ...files);

+ return this.exec('rm', '--ignore-unmatch', '-r', '-f', '--', '.');

};

/**

```

The suggested workarounds included batching the file deletions or simplifying the command to target the current directory (`.`) instead of individual files. Fortunately, these improvements (including a more robust batching logic and a migration to `tinyglobby`) have already been merged into the main branch of the repository via PR #607.

While we wait for a stable release on NPM that fully addresses this in all environments, the most effective way to resolve it is to use the latest development version directly from the source.

By updating your `package.json` to point to the GitHub repository's main branch, you get the latest fixes (including the migration to `tinyglobby` and updated `commander` logic) that bypass these system limits.

### Implementation

Update your `package.json` dependencies:

```json

"devDependencies": {

"gh-pages": "github:tschaub/gh-pages"

}

```

Then, refresh your installations:

```bash

npm install

```

This simple change allowed us to resume our production deployments without hitches, ensuring that our "Brutalist" digital garden stays fresh and accessible.

# Git Cheatsheet: From Basics to Time Travel

A collection of essential Git commands, from daily workflows to digging through the depths of your repository's history.

## 🔍 Searching History

### Find when a file existed (even if deleted)

```bash

git log --all -- [path]

```

### Search for content changes (Pickaxe)

Find commits where a specific string was added or removed:

```bash

git log -S "your_search_string"

```

### Search content with Regex

```bash

git log -G "your_regex"

```

### Find a file in any commit/branch

```bash

git rev-list --all | xargs git grep -l "filename"

```

### See the history of a specific function/method

```bash

git log -L :function_name:file_path

```

---

## 🚀 Daily Workflow

### Stage and Commit

```bash

git add .

git commit -m "feat: descriptive message"

```

### Undo last commit (keep changes)

```bash

git reset --soft HEAD~1

```

### Fix the last commit message

```bash

git commit --amend -m "new message"

```

---

## 🌿 Branching & Merging

### Switch to a new branch

```bash

git checkout -b feature/cool-stuff

# or the newer way:

git switch -c feature/cool-stuff

```

### List all branches (including remote)

```bash

git branch -a

```

### Safely delete a branch

```bash

git branch -d branch_name

```

---

## 🛠️ Cleanup & Maintenance

### Discard all local changes

```bash

git reset --hard HEAD

```

### Clean untracked files

```bash

git clean -fd

```

### Stash changes for later

```bash

git stash save "Work in progress"

git stash list

git stash pop

```

---

## 📤 Remote Operations

### Update local with remote and rebase

```bash

git pull --rebase origin main

```

### Prune old remote tracking branches

```bash

git fetch -p

```

{

"slug": "gh-pages-enametoolong-fix",

"title": "Fixing gh-pages: Resolving spawn ENAMETOOLONG",

"date": "2026-01-08",

"updated": "2026-01-08",

"description": "A quick guide on how to fix the spawn ENAMETOOLONG error in gh-pages by switching to the latest GitHub version.",

"tags": ["gh-pages", "bug", "deployment", "npm", "fix"],

"category": "dev",

"filename": "gh-pages-enametoolong-fix.txt",

"authors": ["fezcode"],

"image": "/images/defaults/sina-salehian-HqmTUJD73mM-unsplash.jpg"

},

{

"slug": "git-cheatsheet-gist",

"title": "Git Cheatsheet: From Basics to Time Travel",

"date": "2026-01-08",

"updated": "2026-01-08",

"description": "A comprehensive Git cheatsheet covering daily workflows, advanced history searching, and repository maintenance.",

"tags": ["git", "gist", "tutorial", "cheatsheet", "dev"],

"category": "gist",

"filename": "git-cheatsheet-gist.txt",

"authors": ["fezcode"],

"image": "/images/defaults/sina-salehian-HqmTUJD73mM-unsplash.jpg"

},