whoami

currently: tinkering

I break my editor
on purpose.
Then I ship the fix.

Explore the work

I'm nohint404. I build developer tooling and web interfaces, with a Linux-minded approach to the everyday details.

Get in touch

~/work

Read the interface. Inspect the source.
❯ ls ~/workPick something apart.

Owned work / nohint404

Scripts for configuring VS Code telemetry, extension behavior and local settings across Linux, macOS and Windows.

Open vs-notrack

~/work/vs-notrack

vs-notrack

A closer look at what your editor leaves switched on.

Scripts for configuring VS Code telemetry, extension behavior and local settings across Linux, macOS and Windows.

  • Bash
  • PowerShell
  • Python
  • GitHub Actions
Inspect the project
vs-notrack / implementation mapSource, not execution

Same editor.
Different decisions.

./vs-notrackmode selectionnormal
❯ inspect settings

Embedded Python merges editor settings into JSON. Timestamp backups precede changes; invalid JSON resets the loaded object, so preservation is not unconditional.

A map of the Linux/macOS script. Neither mode guarantees network privacy. Nothing runs here; read the source before using system-modifying software.

Recording / replay / desktop controls · Contributed work / fraa2a

Monolith

A Windows recording and replay app by fraa2a. I contributed active-game detection, audio controls, desktop UI and initial Stream Deck / local RPC integration.

  • C++
  • Preact
  • TypeScript
  • Tauri
  • SQLite
Read the contributions

This website

Portfolio

This website: static Astro pages with small Svelte islands, a shell-style entrance and case studies drawn from public source.

  • Astro
  • Svelte
  • TypeScript
  • Bun
Read the implementation

~/about

Close to the tool.
Careful with
the interface.

My public work moves between the development environment and the browser.

In vs-notrack, that means working through editor settings, extension state and configuration tests. On this site, it means static Astro pages with small Svelte islands. Different surfaces; concrete implementation details.

Linux is part of how I work. Its shortcuts, paths and direct feedback also shape this site, without getting between you and the work.

I test on my own machine first — if it survives my setup, it ships.

What I actually use

Bash orchestration, Python JSON / SQLite edits, PowerShell and fixture-based checks.

Evidence in vs-notrack ↗

~/contact

Got a weird
tool idea?

Something broken?
Something worth getting right.

Find me on GitHub

Public projects and profile. No direct messaging here.