Skip to content
View KeilerHirsch's full-sized avatar
🏠
Working from home
🏠
Working from home

Block or report KeilerHirsch

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. Markdown is supported. 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
KeilerHirsch/README.md

KeilerHirsch — High-assurance inside. KISS outside.

Simple products. Uncomfortably serious engineering underneath.

High-assurance software · security research · deterministic systems · reproducible evidence

MyRank · MAYHEM Club · Ko-fi

Activity

The workshop moves; this panel follows it automatically — repositories, languages and public activity included.

GitHub activity

How I build

  • Evidence before claims. Tests, provenance and reproducible artifacts should support what a README says.
  • Over State of the Art by default. “Good enough” is a release decision, not an engineering philosophy.
  • Deterministic where it matters. Core decisions should come from explicit rules and traceable facts whenever possible.
  • KISS outside. Assurance inside. Complexity belongs behind the user-facing surface; critical boundaries get stronger assurance when the architecture benefits from it.

If the UI looks simple, someone probably suffered in the architecture first.

Engineering DNA

Ada/SPARK is my primary engineering language. I use it where correctness matters enough to justify stronger guarantees — not because every component needs SPARK, and not because language byte counts define architectural importance.

I would rather prove an invariant than explain later why “that should never happen” happened.

I still use C#, Python, JavaScript and whatever else fits the job. Critical correctness is simply not where I like to negotiate.

I came to software from the physical world: precision mechanics, industrial electronics, aircraft-technology studies, military service and a suspicious amount of self-teaching. That background shaped how I approach software: tolerances, measurements, failure modes, maintainability and systems first — syntax second.

  • Precision Mechanic (Feinwerkmechaniker) — completed German vocational qualification.
  • Electronics Technician for Industrial Engineering (Elektroniker für Betriebstechnik) — completed German IHK vocational qualification.
  • State-Certified Technician program in Mechanical Engineering — Aircraft Technology specialization (Technikerlehrgang Maschinenbau, Schwerpunkt Luftfahrzeugtechnik) — Technische Fachschule Heinze, Hamburg; 13 of 24 full-time months completed; no qualification awarded.
  • 23 months of voluntary military service in the German Armed Forces (Bundeswehr).
  • Autodidact by habit — largely self-taught in software engineering, security research, digital forensics, OSINT and systems work.
  • Languages: Polish (native) · German (fluent / native-level) · English (very good).

Formal education helped. So did a suspicious amount of self-teaching — and, apparently, 9th-grade Realschule Technik-AG.

GitHub is where the workshop became software — and the measurements stayed.

Security & forensics

I approach systems with the same mindset I use to build them: preserve evidence, bind claims to sources, separate observation from inference, and make important state reproducible.

Focus: AI systems · agent tooling · digital forensics · OSINT · provenance

MAYHEM Club

I am the Founder & Mod of r/MAYHEMClub, a creator-first workshop for indie devs, modders, open-source builders and people shipping wonderfully weird things.

Build cool shit. Share it. Get real feedback.


Simple outside. Technically unpleasant to copy inside. 😎

Pinned Loading

  1. WOLPERTINGER WOLPERTINGER Public

    Wide-Area Operations & Logistics Platform for Exploration, Routing, Telemetry, Intelligence, Navigation, Guidance, Engineering, and Reconnaissance.

    C# 1

  2. PLLDN-Programming-Language-Licensing-Decision-Navigator PLLDN-Programming-Language-Licensing-Decision-Navigator Public

    PLLDN - Programming Language & Licensing Decision Navigator

    JavaScript

  3. Critical-FAR-Disclosure Critical-FAR-Disclosure Public

    Forensic-grade evidence of critical security failures, vendor response or non-response, and preserved remediation history.

  4. SCUM-SENF SCUM-SENF Public

    Open-source monitoring, events, alerts and operational tooling for SCUM servers. Built for server owners who prefer telemetry over guessing.