Spyke

Replies

news

Comment on

Kevin McCarthy is ousted as House speaker in a historic vote pushed by conservatives

Reply in thread

The rules of the 118th Congress state that "in the case of a vacancy in the office of speaker, the next member" named on a list submitted by McCarthy to the clerk of the House in January will become speaker pro tempore until a speaker is elected. A House reading clerk announced immediately after the vote that Rep. Patrick McHenry of North Carolina was the first name on McCarthy's list and therefore was appointed speaker pro tempore.

"Pending such election, the member acting as speaker pro tempore may exercise such authorities of the Office of Speaker as may be necessary and appropriate to that end," the rules state. The requirement of a list appears to have originated with the 108th Congress that convened in January 2003.

After the speaker pro tempore takes over, "presumably, the next order of business would be to choose a speaker," Green said. He pointed out that "it's unlikely the House would continue to operate as usual without a new speaker being selected."

https://www.cbsnews.com/news/kevin-mccarthy-removed-house-speaker-what-happens-next/

science

Comment on

*Permanently Deleted*

Reply in thread

Ok. Let’s pretend that’s what happens. Many people would gladly make that trade if they kept / recovered brain function. Of course, it would depend on many things like how pain and timeline of the cancer vs dementia.

Comment on

I just tried vibe coding with Claude

Reply in thread

My preferred way of using LLM coders is:

  • plan only
  • read the spec file I just wrote
  • optionally ask me questions in ‘qa.md’, I’ll reply inline Repeat until it stops asking me questions, then switch to a different model and ask again. I usually use both gpt5.3-codex AND Claude Sonnet

Then I have it update the spec. I start a new session to have it implement. Finally review the code. If I don’t like it, undo and revisit the spec. Usually it’s because I’m trying to do too much at once. And I need to break it down into multiple specs.

Comment on

Upcoming breaking changes for npm v12

Finally!!!

allowScripts defaults to off: npm install will no longer execute preinstall, install, or postinstall scripts from dependencies unless they are explicitly allowed in your project. This includes native node-gyp builds (i.e., a package with a binding.gyp and no explicit install script still gets blocked, because npm runs an implicit node-gyp rebuild for it). prepare scripts from git, file, and link dependencies are blocked the same way. To see what would be blocked, run npm approve-scripts --allow-scripts-pending. Then allow the packages you trust with npm approve-scripts and block the rest with npm deny-scripts. The resulting allowlist is written to package.json and should be committed. If your install routine runs scripts, you can observe warnings in npm 11.16.0+.

Comment on

Looking for advice/experience on spec driven development for a big application while also maintaining an overarching application spec

Superpowers has brainstorming

Note that the current version injects a lot into the system prompt, and it’s always on. If you using Claude Code, install it in a second profile, so that you choose when to use it. I exploring its features now.

https://github.com/obra/superpowers

The Basic Workflow

  1. brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.

  2. using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.

  3. writing-plans - Activates with approved design. Breaks work into bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps.

  4. subagent-driven-development or executing-plans - Activates with plan. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality), or executes in batches with human checkpoints.

  5. test-driven-development - Activates during implementation. Enforces RED-GREEN-REFACTOR: write failing test, watch it fail, write minimal code, watch it pass, commit. Deletes code written before tests.

  6. requesting-code-review - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.

  7. finishing-a-development-branch - Activates when tasks complete. Verifies tests, presents options (merge/PR/keep/discard), cleans up worktree.

The agent checks for relevant skills before any task. Mandatory workflows, not suggestions.

Comment on

Would the Re-Walk exoskeleton work for patients without full balance? They are able to stand and walk, albeit very slowly. ( cerebellar stroke patient )

Reply in thread

They demo'ed that it should catch you falling forward, and the seatbelt will hold you. I'm not sure about sideways. Obviously, we haven't tested either as scenario.

It's biggest limitations are hills and off-road. It can go any place a normal unpowered wheelchair can go. My wife has used the Zeen on grass... possible but exhausting!