Jerusalem, Israel Sterile supply → Python

Zeev Tapoohi
writes Python.

Software Engineering diploma, with a background in C, Java, C++, Android and Assembly. I have been drawn to computers since childhood, and I am now returning to the field deliberately — through Python, automation, and tools I build myself. Everything below runs right here in your browser.

python3  /  in-browser Cycle: idle
Programs--
View on GitHubבגיטהאב press Run to start Python
Output appears here.

Programs load live from the portfolio repository — add one there, it appears here.

Start with these three

sterile_department.py

Models the department's sterilizers with two classes behind a small menu: start a cycle, finish it, count what is running. A machine that is already running cannot be started again.

Open in the console
zeev_hospital.py

Checks whether a department is on the right floor of the hospital. A dictionary instead of a chain of ifs, safe handling of bad input, and 14 automated tests that run on every push.

Open in the console
zeev_sterilizer_check.py

Asks how many machines there are, reads each one's temperature, and counts how many are inside the 121–134°C sterilization window and how many are not.

Open in the console

How I got here

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

First course, Crash Course on Python, completed in October 2026. Working through the rest of 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.

How this site is built

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 counts visits only anonymously, through Cloudflare Web Analytics, 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.

Quick answers

Who is Zeev Tapoohi?

Zeev Tapoohi (זאב תפוחי) is a Practical Engineer in Software from Jerusalem, Israel, with a background in C, Java, C++, Android and Assembly. After 14 years in a hospital sterile supply department, he is moving back into software, focusing on Python, QA automation and DevOps.

What role is he looking for?

Junior roles in Python, QA automation or DevOps in Israel. He is based in Jerusalem.

What can I see on this site?

More than 40 Python programs he wrote himself, running live in your browser through Pyodide. Pick one, press Run, and answer its questions in the input box. The floor-checker program is covered by 14 automated tests that run on GitHub on every push.

Did he use AI to build this?

Yes, for the website itself: he built it with Claude and maintains it himself. The Python programs began as code he typed by hand; where AI later helped improve one or add tests, the commit history shows it.

Get in touch

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.