thirty-eight grammars, one temper: the machine confesses first, then ships

38 grammars touched 7 daily drivers 1 doctrine 0 fabricated benchmarks ∞ segfaults survived

Real name: classified, and yes, every joke about it has already been made, twice. Working name: Tar0. My code keeps one kernel with many public names; I keep one head with thirty-eight opinions.

Stars, not marketing. Five stars means shipped, paged at 3 a.m., then taught to someone who argued back. Two stars means I can read it, fix it, and complain about it with precision.

• ⭐⭐⭐⭐⭐ — the default hand. Notebooks that grow up into pipelines and win arguments.
• ⭐⭐⭐⭐⭐ — no secrets between me and the memory layout. None.
• ⭐⭐⭐⭐⭐ — macros fixed my posture and my syntax tree.
• ⭐⭐⭐⭐ — primitive-only hot paths; boxing is a tax and I renounced citizenship.
• ⭐⭐⭐⭐ — the browser testifies daily; verdict remains guilty-fun.
• ⭐⭐⭐⭐ — window functions first, apologies never.
• ⭐⭐⭐ — guards that fail loudly, because quiet failure is a liar with good manners.

• TypeScript ⭐⭐⭐⭐ — JavaScript with a seatbelt; mirrors still checked.
• Go ⭐⭐⭐⭐ — boring on purpose, which is the whole point.
• Rust ⭐⭐⭐⭐ — the compiler yells once so production stays silent.
• PHP ⭐⭐⭐ — paid rent with it; dinner-table defense included.
• Ruby ⭐⭐⭐ — reads like cheating, bills like honesty.
• Kotlin ⭐⭐⭐ — Java's sharper sibling, family drama not included.
• Swift ⭐⭐⭐ — optionals taught me respect for absence.
• Dart ⭐⭐⭐ — the Flutter weekend that never officially ended.
• Elixir ⭐⭐⭐ — processes everywhere, panic nowhere.
• PowerShell ⭐⭐⭐ — the Windows side of the garage, automated to submission.

• Lua ⭐⭐⭐ — embedded everywhere, apologizing nowhere.
• R ⭐⭐⭐ — statistics with opinions and excellent plots.
• MATLAB ⭐⭐⭐ — origin story of my control-theory scars.
• Haskell ⭐⭐⭐ — monads stopped being scary the day I stopped naming them.
• C++ ⭐⭐⭐ — modern dialects only; the old one is a crime scene.
• C# ⭐⭐⭐ — LINQ still feels like stolen magic.
• Julia ⭐⭐⭐ — numerics at speed, syntax at peace.
• OCaml ⭐⭐⭐ — types that argue back, correctly.
• Fortran ⭐⭐ — inherited sins, stabilized; the numbers still balance.
• COBOL ⭐⭐ — yes, really; something you use daily still runs on it.
• x86 assembly ⭐⭐ — read fluently, written slowly, respected forever.
• Prolog ⭐⭐ — unification fixed my expectations, then my weekends.

2018 ─ first C segfault; felt strangely alive
2020 ─ Java hot paths; boxing banned inside the house
2021 ─ Python ML pipelines; seeds enforced by law
2023 ─ Racket macros; posture permanently corrected
2024 ─ repositories that rewrite their own READMEs
2026 ─ thirty-eight grammars, one temper, zero fluff

A model without a fixed seed is a horoscope with extra steps. Everything here ships with a seed, a leakage audit before tuning, and an eval gate that has permission to fail the build — a permission it has exercised in public, twice, and I thanked it both times.

One breath stack: pandas scikit-learn PyTorch TensorFlow OpenCV parquet SQL Docker model cards

My repositories redraw their own maps on every push. Add a file anywhere and the README knows before your commit message finishes typing itself. Loop guards, concurrency groups, diff-gated bot commits, history with zero empty noise.

Daily carry: GitHub Actions Docker Make bash git Linux vim

neovim tmux ripgrep fzf gh cli postman grafana prometheus nginx redis-cli psql jq sed awk strace gdb valgrind perf htop wireshark

If it renders, parses, or pages me, I have an opinion and a dotfile for it.

1. Names come from drivers and error messages. Vibes have never compiled.
2. Every bound ships with a witness; hunches wait in the scratch branch.
3. One kernel, many public names. Copy-paste is a confession and I don't confess.
4. Broken visuals get purged the day they are caught. This profile keeps a body count of renderers.
5. The judge owns the milliseconds; I own the work per testcase. We don't argue about it.

Debugging is archaeology where you are also the civilization that buried the bug.

A README is a promise; a CI that rewrites its own README is a promise with a work ethic.

Thirty-eight languages and the humbling constant: the machine only ever understood one.

Benchmarks are fiction unless the input family is named, sized, and reproducible.

Open an issue on any repository. I answer with a runnable witness, not adjectives. If I can't reproduce your bug, I'll say so out loud and we'll hunt it together.

Tar0 · Just Code 👨‍💻.