GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — qjerome - Overview

@qjerome qjerome Follow
More
  • Overview
  • Repositories
  • Projects
  • Packages
  • Stars
@qjerome
qjerome
Follow
View qjerome's full-sized avatar

Quentin JEROME qjerome

Follow
Enjoy working at the intersection of cybersecurity and programming
101 followers · 2 following
  • @CIRCL & @0xrawsec
  • Luxembourg City, Luxembourg
  • @[email protected]
  • in/quentin-jerome-00a8a074

Achievements

Achievement: YOLOAchievement: Pull Sharkx3Achievement: Starstruckx3Achievement: QuickdrawAchievement: Arctic Code Vault Contributor

Achievements

Achievement: YOLOAchievement: Pull Sharkx3Achievement: Starstruckx3Achievement: QuickdrawAchievement: Arctic Code Vault Contributor

Organizations

@kunai-project
More
  • Overview
  • Repositories
  • Projects
  • Packages
  • Stars
qjerome/README.md

About

My name is Quentin JÉRÔME, and I currently work as a Rust developer. With significant experience in incident response and threat detection, I develop open-source security tools and libraries to solve practical problems.

Proficient in: Rust, Python, Go

Familiar with: C/C++

My Usage of AI

I believe transparency about AI usage is important as it provides context for evaluating work quality. Here's my approach:

  • Documentation: As a non-native English speaker, I use AI to create clear, consistent documentation while ensuring technical accuracy. I always use it to document already trusted/reviewed content.

  • Simple Algorithms: For repetitive, straightforward code that offers no technical challenge, AI can save time but I always review the output thoroughly.

  • Writing Review: AI helps proofread my English writing to enhance quality, but I never rely on fully AI-generated content. Rather, I write the full content and then use AI to proofread. I believe this process reduces hallucination effect and thus minimizes my review time.

  • Search Engine: AI efficiently finds information (though not always accurately).

Key Principle: I maintain near-zero trust in AI output. Every generated code undergoes functional and performance review. For writing activities (media/blog posts), I author the core content myself and use AI only for refinement - except for code documentation where the code itself is the primary content.

Pinned Loading

  1. 0xrawsec/whids 0xrawsec/whids Public

    Open Source EDR for Windows

    Go 1.3k 154

  2. 0xrawsec/golang-evtx 0xrawsec/golang-evtx Public

    Go 171 28

  3. 0xrawsec/gene 0xrawsec/gene Public

    Signature engine for all your logs

    Go 172 18

  4. 0xrawsec/gene-rules 0xrawsec/gene-rules Public

    Python 42 7

  5. 0xrawsec/0xrawsec.github.io 0xrawsec/0xrawsec.github.io Public

    HTML

Something went wrong, please refresh the page to try again.
If the problem persists, check the GitHub status page or contact support.

Uh oh!

There was an error while loading. Please reload this page.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.