An algorithm must be seen to be believed, and the best way to learn what an algorithm is all about is to try it. The reader should always take pencil and paper and work through an example of each algorithm immediately upon encountering it in the text. This is a simple and painless way to gain an understanding of a given algorithm, and all other approaches are generally unsuccessful. -- The Art of Computer Programming (1997)

[E]very time that a human being succeeds in making an *effort* of attention with the sole idea of increasing hist grasp of *truth*, he acquires a greater aptitude for grasping it, even if his effort produces no visible fruit. -- Simone Weil

---

---

2026-06-03: re-read Mere Christianity

2026-06-02: built (w/o AI!) github.com/go-monk/awsdash

2026-05-14: shared laziness on https://www.reddit.com/r/perl/comments/1tgjbjv/perl_wisdom_in_the_age_of_llms/

2026-03-06: RR (architect) approved my dashboard Go tool | helped out RS (tester) with Grafana dashboard

2026-02-23: deployed argocd to kind cluster

2026-02-20: added Slovakia/TFS to go.dev/wiki/GoUsers

2026-02-16: SD, udajne najlepsi Go programmer v BA teame, mi dal takyto PR review na: slogger: "Nice idiomatic code. Kudos. Need some final touches."

2025: wrote ghleaks | started gomonk.net

2024: wrote github.com/jreisinger/hostrecon, github.com/jreisinger/smoke and https://github.com/jreisinger/hackbox | wrote https://github.com/jreisinger/mutating-wh with e2e tests | created new version of https://github.com/gokatas | updated https://github.com/jreisinger/docs and did several github.com/jreisinger/pocs | wrote 7 blog posts https://jreisinger.blogspot.com/2024 | read Cloud Native Devops with Kubernetes | read Kubernetes Up & Running | got new $job and successfully onboarded | translated book https://argumentujeme-o-nabozenstve.org

2023: wrote github.com/jreisinger/mathpractice | trying to build cybersecurity program based on NIST CSF 2.0 (notes/sec/nist-csf.md) | reviewing API security (notes/sec/api.md) | embedding vulnerability scanning into CI/CD (.github/workflows/scan-vulns-go.yml) | reviewed Go repojacking (notes/sec/repojacking.md, tools/cmd/gorepojack) | reviewing and improving email security (DKIM, SPF, DMARC) | did and tested Datadog-Pagerduty integration to call us when there's an issue | unified log attributes in Datadog | wrote sectools/scripts/httpver.sh to check HTTP versions of our endpoints | delivered company-wide presentation about data breach and security | obtained AWS Certified Cloud Practitioner certification | review what AWS accounts are integrated with DD and security monitored (sectools/dd-awsinfo) | found and reported leaked git secrets | documented and explained to engineers how to prevent it | found and reported public S3 buckets (sectools/aws-s3pub) | lowered AWS and Datadog costs (sectools/aws-dbinfo) | reviewed Kubernetes clusters security

2022: operated Kubernetes ingress WAF: whitelisting and deploying rules | built kubectl-modsec to extract ModSecurity WAF information from Kubernetes | built (with P's help) a dummy gRPC application demologger-grpc to demonstrate and test logging and tracing | interviewed and evaluated cloud team candidates - mostly developers | set up and documented security monitoring (datadog): logs, detection rules, alerting | delivered company-wide presentation about security monitoring