Teaching code has a peculiarity: half of the first session goes into installing things. The wrong Python version, a corporate firewall in the way, one Windows laptop and three Macs, and a whole room waiting. EduTools was built so that half-day stops existing — and so that the rest of the course, from the exercise to the certificate, fits in one tool.
Ask any programming trainer what costs them the most time: it is almost never the teaching. It is the environment.
None of these is fixed by better course material. They are fixed by changing where the code is written.
EduTools' code editor runs in the browser. The trainer types, the room follows live, and with one click each learner gets their own copy to work on without touching anyone else's.
Four languages actually run, in the browser of whoever wrote the code:
And five languages are for writing, not running: PHP, Java, C, C++ and C#. A browser does not compile Java — saying so plainly beats letting people find out mid-session. The editor gives them syntax highlighting, completion and each learner's file; running happens elsewhere.
The editor also does what a modern editor is expected to do: brackets and quotes close themselves with the cursor in between, completion offers the variables the learner has just written — in every language — and, in SQL, the table and column names of the sample database.
Two articles cover the implementation in detail: having learners write code with nothing to install and teaching SQL with queries played out in the room.
It is the move you make twenty times in a day of training: "here is the correct version, take it". The starting point of the exercise, the fix found together, the line everyone needs. And that is where it goes wrong.
Through a chat, code arrives flattened: indentation disappears, line breaks run together. In Python that is not a cosmetic detail — the code no longer runs. By email, you have to leave the session. Dictated, it costs ten minutes.
The collaborative wall solves it. You post the snippet on a note, it stays on the wall for the whole session, and each learner takes it with one button — indentation intact, ready to paste into their editor. Nobody retypes, nobody gets a space wrong.
And because the wall keeps everything, it becomes the thread of the day: snippets pile up in the order they were seen. The learner who drops out for twenty minutes finds what they missed without asking you.
It also works the other way round, and that is often where it earns its keep: ask everyone to post their solution. You end up with five ways of solving the same exercise, side by side, on display. Comparing three correct approaches teaches more than a single correction on the board — and the learners wrote them.
Programming trainers spend a great deal of time writing questionnaires. EduTools ships thirty-six already written, across twelve technical subjects and three moments of a course.
The twelve subjects: first steps in programming, Python, VBA, Excel (basics), Excel (advanced formulas and pivot tables), SQL, HTML/CSS, WordPress, Word, PowerPoint, the internet and digital literacy, artificial intelligence.
And for each, three moments:
Each quiz has ten questions and exists in six languages. Each carries a facilitation sheet saying what to look at in the results — not the average, but the question everyone got wrong, which says more about the session than about the group.
They can be played live game-show style, on their own by link or QR code, or replayed as an arcade game. And they can be edited: they are templates, not fixed content.
Preparation for a technical course gets lost in folders fast. Two tools hold it in place.
The exercise bank keeps your exercises with their answers. In the room, you send one out, and the answer only becomes visible when you open it — not before. What you prepare once, you run forever.
The session plan is your day, step by step, with timings. It serves you during the session and serves the paperwork afterwards. A dedicated article covers it: preparing your day with a session plan.
And the question bank pools what you have already written: a question asked in a Python quiz goes into another one without retyping it.
This is the difficulty specific to technical training: the gap inside one group. Three tools absorb it without splitting the room in two.
The guided course alternates explanation and checking question. The learner moves at their own pace, the server marks, and you see who got stuck where. The fast one does not wait for you; the struggling one blocks nobody.
The branching scenario puts the learner in front of a situation — a production bug, a customer reporting a fault — and makes them choose. Every choice leads to a consequence. It is a case study, not a multiple-choice question.
And flashcards solve the problem of technical vocabulary, which is learned by repetition rather than by explanation.
An independent trainer or a training centre does not live on teaching alone. Two obligations come back with every session.
Electronic attendance: half-day sheets, an individual link or QR code, a signature by finger or mouse, and a compliant PDF at the end. On site and remotely.
The satisfaction survey: straight after the session, or three months later. By name with reminders, or collective and anonymous for large groups.
Both produce the documents an audit asks for. The article proving attendance and participation details which ones.
There is no required order, and above all: creating a room is not compulsory. A quiz, a code editor or an exercise runs on its own, by link or QR code, with nobody having to create an account.
If you teach code, the shortest path is this one:
The free account covers the first three, with no card and no time limit.
No. The code editor runs in the browser: Python, JavaScript, HTML/CSS and SQL execute on the client side, with no interpreter installed and no administrator rights. An up-to-date browser is enough, including on a locked-down corporate machine.
Running: Python, JavaScript, HTML/CSS (as a preview) and SQL (on a sample SQLite database). Writing only: PHP, Java, C, C++ and C#. A browser does not compile those; the editor gives highlighting, completion and file retrieval, but running happens in another environment.
Only if you allow it. By default a learner sees your code but can neither select nor download it — enough to have them listen before copying. You open it with one button when the moment comes, and you can close it again. Each learner can always retrieve their own file.
Yes. They are templates: you create a copy in your own space and change the wording, the answers, the order and the settings. You can keep only a few questions, or mix them with your own from the question bank.
Installing an environment on twenty machines eats the start of every session. Here is how to write and run code in the browser, what it genuinely allows, and where the limits are.
PedagogySQL is learned by querying, not by listening. Here is how to put a real database in a group's hands without installing a server, and in what order to unfold the concepts.
Getting startedAn exercise written once should serve ten times. Here is how to build a bank you can actually find things in, without spending more time than you save.
Create your first interactive room in under 5 minutes. Free plan, no credit card.
Get started for free