Skip to content

Instantly share code, notes, and snippets.

View thedavidyoungblood's full-sized avatar
😁
Enjoying and Contributing to the: Ne0-Reπ@isS@πce

TheDavidYoungblood thedavidyoungblood

😁
Enjoying and Contributing to the: Ne0-Reπ@isS@πce
View GitHub Profile
@thedavidyoungblood
thedavidyoungblood / Claude-Code_Issue-no.30524_Issue-Comment_and_Local-Patch-Pack.md
Last active April 11, 2026 19:28
Claude-Code_Issue-no.30524_Issue-Comment_and_Local-Patch-Pack.md

Sharing a short write-up in case it is useful:

[!TLDR] explores using PreToolUse hook function(s) as interim mitigation for ISSUE: #3024 (and related).

LINK-TO-GIST

Note

It includes:

  • an expanded issue-commentary
@thedavidyoungblood
thedavidyoungblood / RX(rx)_UV-or-BUN_but-for_RUST_open-research_draft.md
Created April 4, 2026 01:50
RX(rx)_UV-or-BUN_but-for_RUST_open-research_draft.md

[!Note from the researcher]

What's this all about?

I was curious in flow, and just felt like exploring what a more unified, DevEx oriented approach could look like to a UV/BUN like system would be for rust and came across this rx project, so decided to one-shot some opinionated constraints to explore what creating anew, and/or enhancing what is, as borrowed from other well done projects for comparative analysis, and exploration.


What's WINNING look like?

@thedavidyoungblood
thedavidyoungblood / PSA -- RCS General Research - Privacy & Security - some concerns....md
Created February 5, 2026 19:27
PSA -- RCS General Research - Privacy & Security - some concerns....md

RCS General Research - Privacy & Security


[TLDR]: "Do Your Own Due Diligence!"(DYODD)

Ultimately, compared to all of the other available options today, this is one of the most proprietary, restrictive, yet, exposed, and in vulnerable ways, where we trade 'features' and 'functionalities', for our privacy, and data-sovereignty. Find and use something else. Almost anything will do. (Relative to where you're located globally, of course.)

@thedavidyoungblood
thedavidyoungblood / The Complete OSS Contribution Framework.md
Last active January 29, 2026 01:36
The Complete OSS Contribution Framework.md

The Complete OSS Contribution Framework

A decision-ready system for contributing to open source without burning bridges


Status Guide Version Last Updated License Contributions Made for OSS Contributors Anti-Nuisance Framework GitHub Friendly


@thedavidyoungblood
thedavidyoungblood / Resolving python3 errors on Windows 11 -- for Claude Code and other CLI agents.md
Created January 19, 2026 18:39
Resolving python3 errors on Windows 11 -- for Claude Code and other CLI agents.md

Resolving python3 errors on Windows 11 (Claude Code + other CLI agents)

Goal: Make python3 resolve to a real interpreter across PowerShell, cmd, Git Bash, and other shells used by agent tooling on Windows 11, without requiring WSL.

Common symptom: python3 --version → “Python was not found; run without arguments to install from the Microsoft Store…”

Root cause (often): Windows “App execution aliases” stub python3.exe in ...\WindowsApps shadows the real Python.

@thedavidyoungblood
thedavidyoungblood / ADR (Architecture Decision Record) — Documentation Pattern.md
Last active April 22, 2026 09:39
ADR (Architecture Decision Record) — Documentation Pattern.md

ADR (Architecture Decision Record) — Documentation Pattern

ATTRIBUTION: thanks to Martin Cleaver https://github.com/mrjcleaver and the Agentics-Foundation https://agentics.org/ -- I took chat notes, and restructured for future reference below.

A lightweight, durable way to capture why an architectural decision was made (not just what was built), so teams can revisit decisions with context instead of re-litigating from scratch.

Tip

ADR = one decision, one file. Keep it durable, searchable, and easy to supersede.


@thedavidyoungblood
thedavidyoungblood / Unified API Lifecycle Playbook.md
Created December 24, 2025 00:22
Unified API Lifecycle Playbook.md

Unified API Lifecycle Playbook (Vendor- and Platform-Agnostic)

A role-based, actionable guide for executives, platform maintainers, and delivery teams to move from fragmented tooling to a coherent API lifecycle.

Version: 1.1
Date: 2025-12-23
Source inspiration: A vendor whitepaper on unifying the API lifecycle (adapted and generalized).
Note: Quantitative examples are reproduced as illustrative benchmarks and may not generalize.

@thedavidyoungblood
thedavidyoungblood / Some Github Operations For Interdepartmental Collaboration.md
Created December 13, 2025 23:53
Some Github Operations For Interdepartmental Collaboration.md

Protected main workflow (Admin merges, Contributors via PRs)

graph TD

subgraph G0["Repo controls - Maintainer and Admin"]
  G0A["Set roles and permissions<br/>Admin: merge to main<br/>Contributors: no direct push to main"] --> G0B["Protect main branch<br/>Require PRs<br/>Block force-push<br/>Restrict who can push"]
  G0B --> G0C["Require reviews<br/>Minimum reviewers<br/>CODEOWNERS optional"]
  G0C --> G0D["Require CI checks<br/>Tests, lint, build, security optional"]
  G0D --> G0E["Define merge method<br/>Squash or merge-commit or rebase-merge"]
@thedavidyoungblood
thedavidyoungblood / ANTHROPIC-CLAUDE-OPUS-4.5_RELEASE-COMPARISON-TABLE_plus-cost-analysis.md
Created November 24, 2025 23:40
ANTHROPIC-CLAUDE-OPUS-4.5_RELEASE-COMPARISON-TABLE_plus-cost-analysis.md

EXPANDING on OPUS-4.5

Anthropic's Latest Report(s)/Claim(s) with 'cost-considerations'...


![[Pasted image 20251124162614.png]]

their chart as shared on X.