Learn

In-depth guides on software-delivery practice

Each guide is a topical cluster of sub-articles covering one discipline end-to-end. Written for senior engineers and engineering managers, not as marketing veneer.

About Stride Learn

What is Stride Learn?
A library of in-depth guides on software-delivery practice. Each hub covers one discipline (sprint planning, code review, test management, AI coding agents) end to end in five or more sub-articles, written for senior engineers and engineering managers rather than as marketing.
How are the guides structured?
Hub-and-spoke: each topic gets one overview page plus five to eight deep sub-articles. The overview frames the discipline; the sub-articles unpack specific practices (for code review: checklists, async patterns, mob review, SLOs and AI-assisted review). Every sub-article cross-links to related ones and to the relevant glossary terms.
Are the guides written by AI?
They are drafted with AI and published by the Stride team. We build Stride with coding agents, and we write these guides the same way: the practices come from how our own repository works, facts about other tools are checked against each vendor's official documentation, and a person approves every guide before it goes live.
How often are the guides updated?
Material updates bump each sub-article's updated date, shown under its title, so crawlers re-index. Minor edits such as typo fixes and broken-link repairs don't bump the date. Each hub gets a quarterly editorial pass to refresh examples and add new sub-articles as practice evolves.
Can I suggest a new topic or correction?
Yes. Email info@newlightai.com with the topic or the correction. We triage suggestions quarterly. The current roadmap includes hubs on AI prompt engineering for software teams, observability practice and distributed-team coordination.