Most of the content for this site is presented in categories, e.g., Repositories, Blogs, ...
That is fine for looking up things about which you already know something.
But there is no inherent sequencing.
-
Where to start?
-
What is a good order for stepping through content?
-
Did I find everything the site contains relating to some topic?
That's where stories are useful. A story is:
- An ordered collection of content relevant to a specific theme, e.g., getting started with C++.
- A mechanism for stepping through that collection in order.
- Each item in the collection should be a relatively complete presentation of an idea or code example.
Here is a list of stories provided by or planned for this site
(see Stories dropdown in top menu):
-
C++ Story
- gentle introduction/refresher for the C++ programming language.
-
Rust Story
- gentle introduction/refresher for the Rust programming language.
-
Rust bite by byte
- intended to be a "getting started for beginners" (about 60% complete).
-
Idioms and Patterns
- a sequence of code fragments that compare C#, C++, and Rust. Just starting.
-
∞ Data Library
- Means to capture scientific research data, guest story by Alexey Zaitsev
-
MLiPS
- Machine Learning integrated with PowerShell, guest story by Mike Corley
-
SiteStory - describes motivation and status for this website.
-
StoryTeller Design - planned description of the design ideas used in the StoryTeller page.
-
Widgets Design - planned description of the design of several widgets used in this site.
-
Design Examples: basic > intermediate > advanced
-
Building complex software systems.
-
Asynchronous message-passing communication channels.