Zeev Tapoohi
writes Python.

Computers have held my attention since I was a child. Not the screens — what was behind them. I wanted to know why a machine did what it did, and I have been taking that question apart ever since. It led me to a Software Engineering diploma and to years of writing C, Java, C++ and Android.

Life then took me into a hospital sterile supply department, where I work as a support worker. It is honest work and I hold it in high regard — the department keeps operating rooms safe, and I have given it everything it asks for: precision, patience, and responsibility for equipment other people depend on. I am grateful for what it taught me.

It is simply not my field. My training is in software, my curiosity has always been in software, and staying away from it has never sat right. I would like to bring the same care I give the sterile supply room to the work I actually trained for.

So I am doing this properly. Studying most evenings, writing programs by hand, finishing the certificates, and moving back to the field I have wanted since the beginning. I ask questions, I take feedback well, and I would rather learn something new than defend something I already know.

Alongside Python I work with AI tools every day, and I treat them the way sterile supply taught me to treat any process: very useful, and never trusted without checking. I build automations in n8n, work with Claude Code and MCP (I completed Anthropic's MCP course), wrote a link checker that drives a headless browser with Playwright, and make short videos with generative models like Veo and Kling. What interests me most is not the tool itself but the part where a person decides what to ask — and checks what comes back.

Google IT Automation with Python

Working through the certificate now. PCAP is next.

Written by hand

Every program in the list started as code I typed myself, one topic at a time. Where AI later helped improve one or add tests, the commit history shows exactly what changed.

AI, with a checklist

n8n · Claude Code · MCP · Playwright. I use AI to build faster — but like a load in the sterile supply room, nothing goes out until it has passed a check.

This page is one HTML file. No framework, no build step, no server. The Python in the list runs through Pyodide — CPython compiled to WebAssembly — so it executes on your own device, in this tab. Nothing is sent anywhere.

The programs are not copied into this page. They are fetched from the portfolio repository through the GitHub API when the page loads, so the list here is whatever is in the repository right now. A program that asks for input reads it from the box under the code: type an answer and press Enter, and the program runs again with every answer given so far. A browser cannot pause Python mid-run to wait for a key, so replaying the run is how the console behaves like a terminal.

A Content-Security-Policy restricts what the page may load, the site sets no cookies and collects nothing, and the Hebrew view flips the prose to right-to-left while the code and the console stay left-to-right. I built this site with Claude, and I maintain it myself. I would rather say that plainly than claim every line. What is mine from the start is the Python in the list — every program there began as code I typed myself.

Runs on your device

Pyodide runs CPython in the browser. No server executes the code, so there is nothing to send to one.

Nothing hidden

The whole site is a single file. Open the page source and read every line.

Open to junior Python, automation and QA roles in Israel. Send a message here and it lands in my inbox — or write to zv.tapoohii@gmail.com directly.

I read everything and reply within a day or two.