What in the world?

WORD5 #519 3/6* (Hard Mode) 🟪⬛⬛🟪⬛ 🟪🟪⬛🟪🟪 🟪🟪🟪🟪🟪

WORD5

“Emotions can multiply all your progress by zero” - Clear Thinking

I capitulated. I learned some hard lessons. When bitcoin was at $104k, I took out a loan to pay for taxes and to buy more bitcoin. Bitcoin went up to $126k. I think I made a great decision. The loan I took out had already paid for itself, and then some. Bitcoin falls and closes below the bull market support band ($107k). I see Benjamin Cowen on YouTube confirm that he thinks we've entered the bear market. In the back of my head, I know it's true but I don't want to act on it. Bitcoin falls to $85k and Luke Gromen says he sold at $95k. My pride says he's wrong. Bitcoin crashes further to $72k. Margin call could happen soon, so I load up more collateral. I've been thinking about where to go from here for a while. Benjamin Cowen clearly sees another trend with this bear market rally. Time to make a decision. I'm going to have to pay back this loan in June or refinance. Decided to sell some bitcoin to pay back the loan. Really sucks. Major benefits: don't have to stress about whether to pay back the loan or buy bitcoin at these crazy low prices. Don't have to think about paying the loan and paying taxes together. Overall view: I think @jack mallers's Strike offers an amazing product. I will use it again. I'm going to be smarter about when. An expensive lesson. Benjamin Cowen is almost always right lol.

@Dr. Jeff I think it was in the bear market of last year that you said something like: stacking anywhere below $69k is a great deal. Been thinking about that, especially right now.

The WesternBTC has forked the strfry relay to implement NIP-91 and is working with these changes. You'll now be able to query with AND (&) operators. @Alex Gleason thanks for pointing out this NIP being merged.

WORD5 #515 2/6 🟧🟧🟪⬛🟪 🟪🟪🟪🟪🟪

WORD5

"If LLMs are writing slop in your codebase, that is an engineering problem and not a LLM problem." Great quote from YouTuber Jaymin West.

Let's not gatekeep around here. Share with me your most useful 🦞 prompts. I'll go first. Merlin is my 🦞's name. This full nightly QA job is for creative testing my website each night: --- **Schedule:** Every night at 11:00 PM EST | **Model:** Claude Opus | **Timeout:** 1 hour ### Tooling Rules - `write`/`edit` tools sandboxed to workspace — must use `exec` (shell commands) for all monorepo file operations - Playwright headless Firefox available for UI testing when the plan calls for it - Uses Merlin's real nostr identity for browser testing — no fake profiles unless multi-user testing requires it ### Delivery Sends summary directly via `message` tool to Josh's pubkey on NIP-17 ### Phase 1: Gather Context 1. Pull latest code 2. Read last 24 hours of commits + diffs 3. Check `memory/nightly-testing-log.md` for what's already been covered 4. Run existing test suite, fix any failures first ### Phase 2: Develop Tonight's Testing Plan Stop and think before writing code. Consider: - What changed today (targeted regression tests) - What hasn't been tested recently (existing code needs exercise too) - The full application surface area: - **Public pages:** homepage, parks, discovery, booking flow, signup, cancellation - **Operator management:** dashboard, setup wizard, site classes, pricing, layout, reservations, payments, email, policy, ops, reports, settings - **Account:** profile, nostr identity, wallet, membership - **APIs:** booking/*, webhooks/*, signup/*, email/*, admit/*, membership/*, lnurlp/*, username/*, sign-payload/* - **Services:** reservation, park, cancellation, booking (pricing/bookability/equipment/vehicles/badges), emailer, invoice, paymentIntegration, parkLayout, availabilitySnapshot, legalDoc, quote, and more - **Libraries:** nip98Auth, bookingMiddleware, bookingLock, sharedKeyStore, rateLimit, validators - **Shared packages:** shared-types, shared-utils - **Infrastructure:** NIP-144, NIP-52, NIP-44, nostr event signing Pick 2-3 focus areas mixing today's changes, existing untested code, and optionally something creative. Write out the plan before coding. **Testing approaches:** Unit tests, API endpoint tests, integration flows, security/adversarial, browser/UI (Playwright), code audits, regression tests ### Phase 3: Execute - Write 15-30 quality tests per night - Run full suite after changes - **Bug handling:** - Straightforward bugs (typo, wrong regex, missing null check, obvious off-by-one) → fix it, write a regression test, commit - Complex bugs (tricky logic, architectural decisions, unclear intended behavior) → DO NOT fix. Document clearly: what's broken, where, impact, and ask Josh how to proceed - Commit in logical chunks, push when done ### Phase 4: Log & Report Update `memory/nightly-testing-log.md` with date, commits reviewed, testing plan rationale, tests added, bugs found/reported, coverage gaps, suggestions. Send summary via DM. ### Key Principles - **Plan before you code** — a thoughtful plan beats random test generation - **Rotate coverage** — the WHOLE app needs coverage over time, not just recent changes - **Existing code matters** — most bugs live in code that's been there for weeks - **Think like a user** — what would a park operator actually do? What would a guest mess up? - **Think like an attacker** — what would someone trying to get a free booking do? - **Fix simple bugs, report complex ones** — straightforward fixes are fine, anything involving complex logic or unclear intent needs human judgment - **Keep the log updated** — future you needs to know what you already covered

WORD5 #513 4/6 ⬛🟧⬛🟧🟧 🟪🟪⬛⬛🟧 🟪🟪🟧⬛🟪 🟪🟪🟪🟪🟪

WORD5

Bitcoin hack: buy fat zaps now and give out that amount in a couple years from now. 1500 sats for a dollar? Buy $100 / $200 worth now and zap100 people $10 worth of sats in the future and make their day.

How long until the human language is removed from the AI work?

I think people missed something important about the layoff news at Block and their stock skyrocketing 20%. It sent an unfortunate signal to the whole stock market: cutting workforce = reward