Chen Ben-Haroosh

I've spent 5+ years in IC verification: writing testbenches, closing coverage, debugging simulation mismatches. I know where the pain is.

A few years ago I started actually using AI in verification work: LLMs for reading hardware specs, ML models for predicting coverage holes, agents that can run the closure loop without someone babysitting them.

This site is where I write up what I try: the experiments that worked and the ones that didn't.

Outside of work

I run a Proxmox/Unraid home server with a NAS and more containers than I'll admit to. The usual suspects: Plex, Immich, Pi-hole, Home Assistant, Paperless for documents, Gitea for git. The more interesting part is the custom stuff running alongside them: TREK (a travel planner I use every day) and a handful of MCP servers that let me query and control the homelab through Claude. It's partly useful infrastructure and partly an excuse to keep experimenting outside the verification world.

The point is to own my data and not rely on a tech company or a subscription to keep it safe when something breaks. I manage the ops side with AI now: backups, updates, logs. But it also started as a way to learn things I'd always wanted to and never had the time or the right tools for. Now that AI can fill any knowledge gap on demand, I'm building things I wouldn't have dreamt of attempting a few years ago.