Skip to content

Improve the sqlite3 tutorial #95271

Description

@erlend-aasland

Improve the tutorial using Diataxis as a guideline: https://diataxis.fr/tutorials/

The current tutorial is quite good, but it could make use of some improvements. The first that comes to mind, is:

Suggesting to split this up into multiple PRs, for the reviewers convenience.

Activity

  1. added
    docsDocumentation in the Doc dir
    triagedThe issue has been accepted as valid by a triager.
    on Jul 26, 2022
  2. moved this from TODO: Docs to In Progress in sqlite3 issueson Jul 26, 2022
  3. moved this from In Progress to TODO: Docs in sqlite3 issueson Jul 26, 2022
  4. erlend-aasland commented on Jul 27, 2022

    @erlend-aasland
    ContributorAuthor

    cc. @CAM-Gerlach & @ezio-melotti #diataxis

  5. erlend-aasland commented on Jul 27, 2022

    @erlend-aasland
    ContributorAuthor

    Currently, the tutorial uses two different database examples (one stock exchange example, and a more recent programming language info example). We should aim to use just a single example database for the tutorial. That example database could also be used in other examples, sprinkled across the reference and in how-to's1.

    So, I'm not particularly fond of the stock exchange example; it works well, but it is ... maybe a little bit dull2? Would it be more fun for the aspiring Python SQLite database programmer if we expand on the programming languages example? Or perhaps something else?

    Quoting Diátaxis, I think this touches upon the first item in this list; the example must be meaningful for the tutorial to be meaningful:

    At the same time, the exercise you put your pupils through must be:

    meaningful - the pupil needs to have a sense of achievement
    successful - the pupil needs to be able to complete it
    logical - the path that the pupil takes through it needs to make sense
    usefully complete - the pupil must have an encounter with all of the actions, concepts and tools they need to become familiar with

    Footnotes

    1. It will probably not make sense to just use one grand example database for the whole sqlite3 docs; e.g., the type detection and the user-defined functions work best with stand-alone examples. ↩

    2. No offence meant to the original author; it's just my personal opinion. ↩

  6. CAM-Gerlach commented on Jul 28, 2022

    @CAM-Gerlach
    Member

    So, I'm not particularly fond of the stock exchange example; it works well, but it is ... maybe a little bit dull2?

    Maybe spice it up with some cryptocurrency? That's bound to be...exciting...these days... /s

    As to the example, I'm really not sure. While being a relative subject matter n00b has been helpful in reviewing the docs from a more beginner perspective, I don't really have the required background to suggest something in this specific question, sorry.

  7. added a commit that references this issue on Aug 1, 2022
  8. moved this from TODO: Docs to In Progress in sqlite3 issueson Aug 1, 2022
  9. added 5 commits that reference this issue on Aug 4, 2022
  10. added a commit that references this issue on Aug 6, 2022
  11. added a commit that references this issue on Aug 11, 2022
  12. Repository owner moved this from In Progress to Done in sqlite3 issueson Aug 18, 2022
  13. added a commit that references this issue on Aug 18, 2022
  14. added 4 commits that reference this issue on Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

3.10 (EOL)end of life3.11only security fixes3.12only security fixesdocsDocumentation in the Doc dirtriagedThe issue has been accepted as valid by a triager.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions