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.
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.
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.
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.
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.
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
