Skip to content

Instantly share code, notes, and snippets.

View dmd's full-sized avatar

Daniel M. Drucker, Ph.D. dmd

View GitHub Profile
Know the facts: Protecting our legacy
August 6, 2026
This message is being shared with systemwide physician leaders and people managers. You play an important role in helping your teams understand the changes affecting healthcare and what they mean for Mass General Brigham. We are committed to providing context on the issues facing our industry and how we are adapting to continue advancing our mission.
‌Dear Colleagues,
‌We have heard from many of you that you would like more context about healthcare finances. We will continue sharing information and resources to help explain the forces shaping Mass General Brigham's financial environment and the decisions being made across our system. MGB's mission remains unchanged: improving lives through exceptional patient care, research, education, and service to our communities.
‌What has changed is the environment around us.
**I've Done 7 Repositioning Cruises—Here's What No One Tells You** — Tips For Travellers (Gary Bembridge), 14:50
**TLDR:** Repositioning cruises — one-way voyages when cruise lines move ships between regions in spring and autumn — can cost half the per-night rate of a regular cruise, but they come with catches: heavy sea days, rough shoulder-season weather, one-way flight costs, and a very different onboard vibe.
**What they are**
- One-way trips moving ships between seasons (e.g., Caribbean ↔ Europe/Alaska), sold instead of sailing empty. Most common: transatlantic, Panama Canal/West Coast, and transpacific (he just did Silversea's Silver Nova, Alaska → Japan).
- Only available in two windows (March/April and October/November), run 10–21+ nights, and are sea-day heavy — his Silver Nova trip had eight sea days, six back-to-back.
**Why people love them**
- Fares are often ~half the per-night cost, letting people afford a better cabin or a more premium line (he's booked Crystal and Regent repositionings for
{
"reading_time": "2026-07-16T11:39:57",
"reading_epoch": 1784216397,
"helium_level_ltr": 4504,
"helium_gs_flow_cc_hr": 1040,
"service_inner_shield_temp_3ab_k": 50,
"service_outer_shield_temp_2pt_k": 4,
"service_coldhead_inner_link_temp_5ab_k": 37,
"service_coldhead_outer_link_temp_5pt_k": 40,
"service_top_link_inner_temp_6ab_k": 41,
{
"data": [
{
"id": "1",
"type": "sensor_statuses",
"attributes": {
"assetId": 1,
"inputId": 1,
"lastSensorContact": "2026-07-09T18:11:07.000+00:00",
"minRange": "34.50",
▐▛███▜▌ Claude Code v2.1.204
▝▜█████▛▘ Opus 4.8 · Claude Max
▘▘ ▝▝ /Users/dmd
▎ Extended: Fable 5 is included in your weekly limit
▎ Through July 12, you can use up to 50% of your weekly usage limit on Fable 5. If you hit your limit, you can continue on Fable 5 with usage credits. Fable 5 draws down usage faster than Opus 4.8. Run /model and select Fable to use it. Learn more
❯ use ~/.api_keys/CERTMANAGER_API_KEY to connect to cert-manager and tell me
what ACME accounts I have registered

wehackthemoon.com → Static Site: Conversion Notes

Goal: Produce a 100% static, server-side-free copy of https://wehackthemoon.com/ so it can be hosted without PHP, Drupal, or a database (the current host is discontinuing PHP/Drupal support).

Result: wehackthemoon-static/ — 515 HTML pages and ~9,100 supporting files (~1.4 GB). Upload the folder's contents to any static web host (nginx, Apache, Netlify, Cloudflare Pages, S3, etc.) and the site runs as-is.


What was done (high level)

IDK if you know anyone who can fix this, but...
I found a fun bug in the Google search calculator. The parsec is wrong, but only when you multiply with it.
Every direct conversion is fine: 1 parsec in au, in light years, in meters all return correct values. But put the parsec into a product and the result comes out exactly 180/π ≈ 57.296 times too small.
Cleanest repro:
1 newton * 1 parsec in joules
A newton-metre is just a joule, so this should equal the parsec in meters, 3.0857e16 J. Google returns about 5.39e14 J instead, low by that same 180/π.
# ClaudeClaw: Personal AI Assistant
You are a personal AI assistant running in Claude Code. You operate from this
directory as your workspace.
Your user is Daniel. He lives in Arlington, MA.
## Directory Structure
```
## Writing Rules
These are errors. Violating a hard stop means I send it back.
### Hard stops (never do these)
1. **No em dashes.** Never use — or --. Use commas, semicolons, parentheses, or separate sentences.
2. **No negative parallelism.** No "It's not X, it's Y." No "not because X, but because Y." No "Not X. Not Y. Just Z." State the point directly.
3. **No standalone fragments.** No dramatic one-sentence paragraphs for emphasis. Write real sentences with subordinate clauses.
4. **No magic adverbs.** Cut "quietly", "deeply", "fundamentally", "remarkably", "arguably" when used to inject significance.
# Timelapse project automation
# Show available commands
default:
@just --list
# Classify and rename new photos using AI
classify *args:
./rename-lapse.py {{args}}