The promise behind the site
Everything published on strcoding.club takes the same route from idea to page. This document explains that route so you can judge our work fairly.
Standards
Sourcing, checking, bylines, dates and commercial links, set out so you can judge what you read on STR Coding Club.
Everything published on strcoding.club takes the same route from idea to page. This document explains that route so you can judge our work fairly.
Nothing is published anonymously. A name on a page means somebody can be asked about it later, and that is the only accountability a small site has.
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.
The writer starts by getting everything down, then goes back and marks anything they could not defend if pushed. Those marks are resolved one by one, against a source or from experience, and whatever cannot be resolved is deleted rather than softened. A second reader then goes looking only for false certainty.
Topics come from three places: reader mail, our own notes, and gaps we notice while reading what else is published. Nothing gets written because a keyword tool suggested it.
We treat dates as facts, not decoration. Refreshing a page to look current without changing its substance is a small lie we would rather not tell, so we do not touch the date unless the content genuinely moved.
Some links on this site are commercial. They never buy a rewrite of the surrounding paragraph.
A request to pull a criticism gets a flat no and a place in our records. Sometimes that request is more revealing than the thing complained about, and it says so in a later piece.
Write to info@strcoding.club with the page address and what is wrong. Factual errors are fixed quickly. If the correction changes the conclusion of a piece, we add a short note at the foot of the page rather than quietly editing it.