Skip to content
View QueBallSharken's full-sized avatar
🎯
Living My Best Life
🎯
Living My Best Life
  • Idaho

Block or report QueBallSharken

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
QueBallSharken/README.md

BUILD IT. SAVE IT. BREAK IT. SAVE IT. FIX IT. SAVE IT. RESPECTFULLY. ∞

Evidence over ego. Understanding over hostility. Integrity over appearances. Progress over pretending.

I'm Steven Kyle Hensley, known as Stevil QueBallSharken.

I'm a self-taught developer and independent researcher exploring software engineering, cybersecurity, AI governance, verification, and adversarial testing.

My philosophy is straightforward:

Build deliberately. Preserve the evidence. Challenge assumptions. Preserve the findings. Correct what is demonstrated to be wrong. Preserve the results. Treat people with respect throughout the process.

Progress is not about being right the first time. It's about being willing to discover where you're wrong, understanding why, and applying what you've learned.

My Philosophy

BUILD IT.

Create with purpose.

Define the objective, document assumptions, establish a baseline, and identify meaningful acceptance criteria.

A working implementation is a beginning—not proof that the implementation is correct.

SAVE IT.

Preserve the original.

Record the baseline, source integrity, configuration, assumptions, and initial evidence.

What existed before testing matters just as much as what exists afterward.

BREAK IT.

Challenge the work—not the people.

Test boundaries, question assumptions, explore failure conditions, and search for counterexamples.

Adversarial testing is not an act of hostility. It is a disciplined attempt to discover what ordinary testing may overlook.

There can be no emotional exceptions to the facts.

SAVE IT.

Preserve the failure.

Record the original test, observed behavior, logs, evidence, conditions, and findings.

Never erase an inconvenient failure simply because a later test passes.

A failed test can provide more valuable information than a passing test.

FIX IT.

Follow the evidence.

Investigate the cause, propose a correction, verify the implementation, and test again.

A proposed fix is not a verified fix.

A passing test is not proof of universal correctness.

If a solution introduces another failure, acknowledge it and continue

Pinned Loading

  1. dtpe-canonical-runtime dtpe-canonical-runtime Public

    Python 4

  2. BBIS BBIS Public

    Repo description Boundary-to-Boundary Invariant Survival (BBIS): a governing continuity requirement for systems that claim the same invariant remains live, binding, and refusal-capable across every…

    2