Ofri Peretz

01Section 1:Impact

The numbers behind the work

Cumulative totals across code, writing, and community — refreshed daily, every number traceable to its source.

02Section 2:The agenda

Code is changing authors

Most production code will soon be written by machines. The trust layer — review, analysis, policy — has to change authors with it: findings a coding agent can act on, standards that survive the handoff from human judgment to automated repair.

Evidence over confidence

The industry runs on unverifiable claims. Public numbers should carry their methodology, benchmarks should publish their weights, and a marketing claim should expire unless it re-earns its place. I hold my own work to that bar first.

Leadership in the open

Trust doesn't scale through authority; it scales through work anyone can audit. Transparent methods, documented decisions, code in public — the same discipline whether the room is an engineering org or an open ecosystem.

This agenda is behind the Interlace ESLint Ecosystem — 30 plugins, 477 rules, covering OWASP Top 10, LLM security, and database hardening — behind the writing below, and behind how I run distributed engineering teams at Snappy.

04Section 4:Also building

Interlace Serverless

3 plugins live

TypeScript-first plugins for the Serverless Framework

defineConfig and typed plugin helpers, per-function IAM roles with strict validation, and API Gateway caching with flush and cleanup hooks — for Serverless Framework v4+, each plugin independently versioned on top of a shared devkit.

Read the docsView on npm

Interlace Design System

146 items

The components this site is built from

Not an npm dependency — a shadcn-style registry of 146 items you install FROM, so the component lands in your tree and stays yours to edit. This blog consumes it that way (@interlace → ds.interlace.tools), which is why every page here is also a working example of it.

See the systemBrowse Storybook

burgee

Coming soon

An agent-native CLI framework

Drop-in compatible with commander and yargs, so an existing CLI keeps working. Declare a command once and help, --json, --schema, --mcp and shell completions are all projected from that single declaration — so the CLI a human reads is the same one an agent can call, without a second interface to keep in sync.

★ Star on GitHub

• 

  ESLint Ships in 459 KB, So My Blog Posts Lint Your Code

  ESLint's linter ships in 459 KB with two real security plugins inside it. Here's the esbuild recipe that puts a working linter inside a blog post.

  Sep 2, 2026· 4 min
• 

  Nobody Writes Bad Crypto. They Write Correct Crypto at Four Layers.

  Crypto failures are not one mistake repeated. They are four distinct layers of correctness, and each one looks fine from the layer above it.

  Aug 1, 2026· 6 min
• 

  142,076 Weekly Downloads. Zero Releases Since 2021. Is the Niche Defended?

  A Serverless plugin with 142k weekly downloads last shipped a release in 2021. Downloads said taken; the registry said abandoned; the platform's roadmap said something else entirely. The incumbent map — weekly downloads × years since last publish × open-issue decay — is how I decide what to build next, including the pick I shipped against two months before the fact-check caught up with me.

  Jul 20, 2026· 6 min
• 

  We Were Wrong About sls remove

  Our loudest serverless claim — 'ghost billing after sls remove' — failed our own E2E run. The trap is real, but it lives on a different path entirely. The full story of re-scoping a claim in public, and why the narrower version came out stronger.

  Jul 20, 2026· 7 min
• 

  25% of My Benchmark Verdict Is an Opinion. Here's the Anatomy.

  My serverless benchmark prints 0.88 vs 0.3025 — real measurements running on editorial weights. Every index has a committee; the only real question is whether it publishes its votes. Mine are here: seven dimensions, the null policy, and a ±50% attack on the weights.

  Jul 20, 2026· 6 min
• 

  Marketing Pages Rot Silently. Mine Print an Expiry Date on Every Claim.

  The claims registry: one file where every public claim has a row, every row points at a versioned result file, and a 90-day staleness rule decides when a claim must re-earn its place. The contract, the lifecycle, and how any product adopts it in an afternoon.

  Jul 20, 2026· 6 min

06Section 6:Career

Work experience

1. 2024 — Present·U.S. Site Engineering ManageratSnappy (Austin, TX)
   • · Built first U.S. engineering team
   • · Leading largest distributed team (US/EU)
2. 2025 — Present·Open Source Creatoratofriperetz.dev
   • · 30 ESLint plugins, 477 rules
   • · Deep dives on JS/TS, testing & platform engineering
3. 2022 — 2024·DevEx Team Lead + API LeadatSnappy (Tel Aviv)
   • · First monetized API platform
   • · 25+ shared packages, mono-repo
4. 2021 — 2022·Full Stack EngineeratSnappy
   • · Scaled APIs 100x
   • · 1,000+ tests, TypeScript migration
5. 2015 — 2021·Previous RolesatVarious
   • · 6 years of platform engineering across startups and scale-ups