TeachyLeaf aims to make technology easier to understand through clear explanations and examples readers can inspect. This page describes the standards I use when creating and maintaining tutorials and browser-based tools. It is an explanation of the process, not a claim that every possible configuration or use case has been tested.
How topics and sources are chosen
I prioritize topics connected to my experience teaching electronics engineering from 2015 to 2021 and my later work in IT, including web and mobile app development. I aim to explain the level of experience behind a lesson accurately: direct teaching or development experience is different from introductory research or a personal example.
For behavior that depends on a language, framework, database, or browser version, I consult relevant documentation and identify the environment or assumptions when they affect the result. Third-party material is not presented as my original work; when it is used, it should be attributed and used in line with its license.
How examples are checked
Lessons should include enough context to follow an example, such as prerequisites, input data, expected output, and important limitations. I review code and calculations for consistency and, where practical, run examples in the stated environment. A test in one environment does not establish that an example works in every version or production system.
Browser-based tools should explain what they do, what they do not check, and how they handle input. The SQL, JSON, and URL tools on TeachyLeaf process input in the browser. Their results are not a substitute for testing queries against your database, validating data against your application's requirements, or checking a URL's destination and safety.
Corrections and updates
Technical guidance can become outdated as software changes. I review feedback and update a page when a correction, changed behavior, or clearer explanation is warranted. When an article has materially changed, its updated date should be shown alongside its publication date. Minor wording or formatting edits do not necessarily change the updated date.
If you find an error, unclear step, broken example, or outdated detail, please contact me with the page URL and enough detail to reproduce or verify the issue. I will review the report and correct the page when needed.
How readers can use this material
Use lessons as a learning aid, not as a guarantee that code is secure, suitable for production, or correct for an unstated environment. Verify important behavior with the official documentation and in your own context. If something does not match your results, feedback helps me investigate and improve it.
Meet the author on the About page, or browse the tutorial library and developer tools.