Automation is your workforce

What this site is

A reference for people who want to use AI and automation in real work, written and maintained by one person rather than a content team. The emphasis throughout is on what can be put to work now — what a thing is for, when it is the wrong choice, what it costs, and what breaks once real users arrive.

It is written in Hebrew first and mirrored into English. That ordering is worth knowing: the Hebrew side is where material appears first and goes deepest, and a few of the newest pages exist there only. Everything is free, with no account and nothing gated — see about for who writes it and how it is funded.

Where to start

Depends on which of three people you are, and the wrong entry point is the usual reason someone bounces off this subject entirely.

• You want to use AI better in daily work. Start with a guide to one assistant and use it for a month on tasks you already do. Skip comparisons and pricing until you know what you actually run.
• You want to automate something repetitive. Start with the most boring recurring task rather than the most annoying one — boring tasks are regular and rule-shaped, which is exactly what automates well. The annoying ones are annoying because they need judgement.
• You are building on top of models. Prompting, context and structured output first; retrieval, agents and evaluation once you have something running and can name what it gets wrong.

What you will not find here

No "best AI tool" rankings and no benchmark tables lifted from press releases. Scores shift with every release, are measured on tasks the publisher selected, and say less than you would hope about whether something works for you. No claims that AI replaces anyone, either — the pattern in work that actually survives is narrower and duller than that: the machine takes the repetitive middle, and a person still opens the thing that matters.

There is also a body of security material here — prompt injection, jailbreaks, agent security — which can look out of place on an automation site. It is here because it is the author's own field, and it is strictly defensive: enough of how an attack works to explain the defence, and nothing usable against anyone else's systems.

On accuracy

Model names, prices and capabilities date quickly, and a guide that has gone stale is worse than no guide. Pages carry a last-updated date, code in the guides was run rather than copied out of documentation, and figures that cannot be checked against an official source do not go in.

That process is not perfect and errors do get through. A report of something wrong — a stale price, code that has stopped working, a broken link — is handled ahead of anything else, and is genuinely the most useful message anyone sends.