About
The people behind STR Coding Club, how each article about first steps in coding, Python practice, club projects and teaching code is put together, and what we will not publish.
What you are looking at is a working blog. Old pieces stay up in the archive rather than quietly disappearing, including the ones that have aged badly.
There was no plan. Imogen Achebe kept being asked the same handful of questions about first steps in coding, Python practice, club projects and teaching code, got tired of writing the same reply, and put the replies somewhere permanent.
There are questions we routinely decline. Anything that depends on facts only you can see, and anything where being wrong would cost you real money on our say so.
Every article carries the name of the person who wrote it, and every name links to a page listing everything else they have written.
Imogen Achebe, Club organiser and mentor. Imogen started a coding club at her school and now trains volunteer mentors. She writes about first steps in coding and projects that work for groups of mixed ability.
Bartholomew Ng, Python instructor. Bartholomew taught maths for years before switching to teaching Python. He writes about the basics of the language and about teaching code without drowning learners in syntax.
Selene Dragomir, Problem solving coach. Selene coaches students for programming contests. She writes about practice problems, debugging and the habits that help beginners get unstuck on their own.
Each piece sits under exactly one heading. Readers arriving from search mostly land in python and practice, first steps and club projects, so those sections get looked after first.
Each article answers one question about first steps in coding, Python practice, club projects and teaching code and then stops. Padding a page to look thorough is the easiest way to waste a reader's afternoon.
We buy what we write about. It is slower, it is more expensive, and it is the only arrangement that lets us say a thing was not worth it.
How claims get checked and how money is disclosed is written down separately, on the editorial policy page.
There is no subscription, no newsletter upsell and no course. If that changes we will announce it on this page before anywhere else.
Point at the sentence. Write to info@strcoding.club or use the contact page. Factual errors are fixed quickly, and when a correction changes the conclusion of a piece we say so at the foot of the page rather than editing quietly.
