Peter Akkies  🔗 **Source:** [Peter Akkies](https://www.reddit.com/r/thingsapp/comments/1wqcxjr/peter_akkies/?share_id=XpVwxC9DYSlrZeQxIuMc0&utm_content=1&utm_medium=ios_app&utm_name=iossmf&utm_source=share&utm_term=2) > [!note]+ Document Notes > tags: [things-3, task-management, productivity-apps, notebooklm, online-courses] > author: Ok-Comfortable2546 and r/thingsapp commenters > source: reddit.com r/thingsapp > reference: https://www.reddit.com/r/thingsapp/comments/1wqcxjr/peter_akkies/ > date created: 2026-10-01 17:28 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: Peter Akkies > <!-- deep-read:sections start --> ## 🧭 Table of contents - [📝 Summary](#-summary) - [📖 Main content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning styles assessment](#-learning-styles-assessment) - [📊 Accessibility assessment](#-accessibility-assessment) - [🌍 DEIB assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🛡️ DARVO analysis](#️-darvo-analysis) - [🎯 Conclusion](#-conclusion) - [🔄 Refactor appendix](#-refactor-appendix--peter-akkies) This is a single anonymous forum thread on Reddit. Everything in it is one set of users' opinions and reports. Nothing in it is verified, and the capture has no sourcing beyond the thread itself and the profile links listed in References. Paragraph labels like ¶4 are the pipeline's extraction labels, not part of the original. Reader shows the author as the Reddit username Ok-Comfortable2546 and the date as 2026-09-28. No real name is given or guessed here. ## 📝 Summary - **What happened.** A thread titled "Peter Akkies" sits in r/thingsapp (¶1), posted by the user Ok-Comfortable2546 (¶2). The captured text has no post body. It holds six short comments by six other users (kuzcoduck, gianni1986, vyega, Flashy-Bandicoot889, mat_rhein, dont12) about videos and courses by someone called Peter. One comment says the video explains "the new feature" (¶12), but no comment names the feature or the video. - **The claim.** There are three positions. One says Things is easy enough that reading Cultured Code's docs once covers it, so tutorial videos add little (¶4). One says a particular video is mostly an ad for his Things 3 course (¶10), and a reply says 95% of it explains the feature with examples and settings (¶12). A third says the personal setup of areas and projects is what the courses teach, because everyone ends up tailoring it (¶14). One user also describes a NotebookLM project built from the public docs (¶8). - **Why it matters.** The thread is a small, live example of the docs-versus-tutorials split for a product with good documentation. It also records one concrete workflow for turning public docs into audio. - **Key stakeholders.** The commenters, the app's maker (named in the thread as Cultured Code, ¶4, ¶8), and Peter, who the thread treats as a creator of Things videos and a seller of courses (¶10, ¶14). Peter's own view isn't in the capture. - **Risks and tradeoffs.** One data point per claim. The "95%" figure (¶12) is a commenter's impression, not a measurement. The advertising charge (¶10) is also an impression. The NotebookLM workflow (¶8) is a self-report with no results shown. Commenter attribution depends on how the capture orders usernames and text (see Main content). - **Bottom line.** Keep the NotebookLM-from-docs workflow as a thing to try and the docs-explain-features, courses-explain-setup split as a hypothesis. Treat every factual statement about Peter, his video, or his course as unverified. ## 📖 Main content **What the capture looks like.** The text file has 14 labeled paragraphs and about 190 words. The labels alternate: a subreddit (¶1), a username (¶2), then pairs of a username and a block of text. Paragraphs ¶3, ¶5, ¶7, ¶9, ¶11 and ¶13 are bare usernames. Paragraphs ¶4, ¶6, ¶8, ¶10, ¶12 and ¶14 are comment text. The capture doesn't mark which username owns which text. **How comments are attributed here.** This note reads each username as the label for the text that follows it, so kuzcoduck wrote ¶4, gianni1986 wrote ¶6, vyega wrote ¶8, Flashy-Bandicoot889 wrote ¶10, mat_rhein wrote ¶12, and dont12 wrote ¶14. That reading is an inference from conversation order. It fits the content: ¶8 ("Then you should listen") answers ¶6 ("I don't think people read anything nowadays"), and ¶12 answers ¶10 (the advertisement charge). Under the opposite reading, where each username closes the text before it, ¶8 would become gianni1986's and the poster's name would head ¶4. The capture can't settle this. The Reddit thread would. **The thread's three positions, as the commenters state them.** | Position | Comment | What it rests on | |---|---|---| | Docs suffice | ¶4 (kuzcoduck) | Things "is made to be easy to understand." Reading the Cultured Code docs once covers everything. No data. | | Video is an ad | ¶10 (Flashy-Bandicoot889) | Calls the video "an advertisement" for "his little Things 3 course." No timestamps or examples. | | Video is substantive | ¶12 (mat_rhein) | Says 95% of the video explains the new feature with examples and all the involved settings. No timestamps. | | Courses teach setup | ¶14 (dont12) | Says they like Peter's videos, bought the courses, and that the areas-and-projects setup is something everyone tailors. | **The NotebookLM workflow (¶8).** The commenter says they gave NotebookLM every open docs URL from the Cultured Code site, then asked it for a global podcast and a mini series that goes feature by feature. NotebookLM is Google's tool that answers questions and generates audio overviews from sources you add. That description is background, not something the thread states. The thread doesn't say how many URLs, how long the episodes run, or whether the audio was accurate. **Terms.** - **Things 3.** A task manager app. The thread assumes the reader knows it. It names the maker only as "Cultured Code" (¶4) and "CulturedCode" (¶8). - **Areas and projects.** Things' two top-level containers for tasks. The thread uses the terms without defining them (¶14). - **Peter / Peter Akkies.** The title and ¶14 give a first name only. The thread treats him as a video maker with courses. That is the thread's framing, not something checked here. **Uncertain or contested.** Whether the video is mostly feature explanation or mostly promotion is contested between ¶10 and ¶12, and neither side cites a time or passage. Whether the docs alone suffice (¶4) is contested implicitly by ¶14, which says setup is personal. The capture doesn't include the video, the course, or the docs, so none of these claims can be checked from it. ## 🗒️ Notes #### 📄 ¶1-¶3 Subreddit, poster, first commenter - ¶1 is the subreddit label, r/thingsapp. The thread's reference URL names the same subreddit. - ¶2 is the poster, Ok-Comfortable2546. No post text follows it in the capture, so the thread title ("Peter Akkies") is the whole post as captured. - ¶3 is the username kuzcoduck, which heads the first comment. #### 📄 ¶4-¶6 "Read the docs once" and the reply - ¶4: kuzcoduck calls Peter a "cool guy" and says videos about Things have a basic problem, because the app is made to be easy to understand. - ¶4: claims that reading Cultured Code's docs once covers literally everything about the app. That is an opinion, with no measure of what "everything" includes. - ¶5 is the username gianni1986. ¶6: "I don't think people read anything nowadays." It reads as an aside about audience habits, with no data. #### 📄 ¶7-¶8 Docs into NotebookLM - ¶7 is the username vyega. ¶8 replies to the "people don't read" remark with "Then you should listen" and a headphones emoji. - ¶8: vyega built a NotebookLM project and gave it all open docs URLs from the Cultured Code site. - ¶8: asked for one global podcast first, then a mini series that covers features one at a time. #### 📄 ¶9-¶10 The advertisement charge - ¶9 is the username Flashy-Bandicoot889. - ¶10: calls the video "basically an advertisement" for Peter's Things 3 course and ends with a shrug emoji. It names no passage. #### 📄 ¶11-¶12 The rebuttal - ¶11 is the username mat_rhein. - ¶12: calls the summary unfair and says 95% of the video is a detailed, easy-to-grasp explanation of the new feature with examples and all related settings. - ¶12: closes with a personal line, that a viewer who sees only an ad has "no interest in Things but complaint." That is a charge about the other commenter's motive, not about the video. #### 📄 ¶13-¶14 A customer's view - ¶13 is the username dont12. - ¶14: likes Peter's videos and bought his courses. - ¶14: says the "setup behind the scenes" with specific areas and projects is something everyone ends up tailoring for themselves. ## 📚 References The captured link list has seven entries, all Reddit pages: the subreddit and six commenter profiles. It has no link to the video, the course, the Cultured Code docs, or NotebookLM. - [r/thingsapp](https://www.reddit.com/r/thingsapp/): the subreddit where the thread sits (¶1). - [Thread: Peter Akkies](https://www.reddit.com/r/thingsapp/comments/1wqcxjr/peter_akkies/): the source analyzed here, the reference URL in the metadata. - [Ok-Comfortable2546](https://www.reddit.com/user/Ok-Comfortable2546/): the poster's profile (¶2). - [kuzcoduck](https://www.reddit.com/user/kuzcoduck/): profile (¶3). - [gianni1986](https://www.reddit.com/user/gianni1986/): profile (¶5). - [vyega](https://www.reddit.com/user/vyega/): profile (¶7). - [Flashy-Bandicoot889](https://www.reddit.com/user/Flashy-Bandicoot889/): profile (¶9). - [mat_rhein](https://www.reddit.com/user/mat_rhein/): profile (¶11). - [dont12](https://www.reddit.com/user/dont12/): profile (¶13). - Claims with no link in the captured markup: that Cultured Code's docs cover everything (¶4); that the video is an advertisement (¶10) or is 95% feature explanation (¶12); that the courses teach setup (¶14); that the NotebookLM project works as described (¶8). The docs the thread points to live on the maker's site, which ¶4 and ¶8 name but don't link. A reader would need the video and the docs themselves to check any of these. ## 🗣️ Paraphrase One user says the app is built to be simple, so reading the maker's documentation once teaches everything and videos add little. A second remarks that people don't read anymore. A third answers by saying they loaded all the public documentation pages into NotebookLM and asked it for a general podcast plus episodes on each feature. A fourth user calls the video in question mostly a pitch for a paid course. A fifth says most of the video is a thorough walkthrough of a new feature with examples and every setting involved, and suggests the critic only wants to complain. A sixth says they like the videos and bought the courses, because the way a person arranges areas and projects ends up being personal. ## 📰 Newsletter **Docs or tutorials? A Things 3 thread has both sides, plus a handy NotebookLM trick.** A short thread in r/thingsapp argues about whether a Things 3 video creator adds anything beyond the official docs. One commenter says one read of the docs is enough. Another says the video in question is mostly a course ad. A third pushes back: most of it, they say, explains a new feature in detail. A fourth, who bought the courses, says the personal setup of areas and projects is what you can't get from docs. The part worth stealing is the workflow in the middle: feed every public docs URL for a tool into NotebookLM, then ask for a general overview podcast and a feature-by-feature series. It's one user's report, with no results shown, so try it on a small doc set first and check the audio against the docs. WordPress folks can run the same experiment on a handbook section. Link: [the thread on r/thingsapp](https://www.reddit.com/r/thingsapp/comments/1wqcxjr/peter_akkies/). ## ✅ Action items One user's forum thread, unverified. Each line ties to the thread's text or says plainly that no action follows. #### DevRel - Developer advocacy: no direct action. If you cite this thread in a talk, call it one anonymous exchange, not evidence about tutorial creators. - Education: the thread's split (docs explain features, courses explain structure, ¶14) is a testable framing for a workshop. Try a docs page and a "how I set this up" walkthrough side by side. - Developer experience: the "read the docs once" claim (¶4) is a prompt to audit whether your own docs cover setup and structure or only features. - Developer marketing: the advertising charge (¶10) shows a commenter reading a tutorial as an ad. A tutorial that states its commercial link up front would avoid that reading. - Community management: the thread stays civil but ¶12 attributes a motive ("no interest in Things but complaint") to another user. Moderators can note that pattern. - Internal/external/cross-project: none from this source. #### OSPO - Policy and governance: no direct action. The thread concerns a proprietary app. - License compliance: none. Feeding vendor docs into a third-party tool (¶8) raises a terms-of-use question, but the thread doesn't discuss it, so this is an inference, not a finding. - Security management: none. - Software inventory: none. - Developer support: none directly. Nearest relevance: a docs-to-audio workflow (¶8) could serve contributors who learn by listening. - Community engagement: none from this source. - Strategic alignment: none. #### Community - Maintainers: no direct action. Nearest relevance: maintainers can ask whether their docs cover setup choices as well as features (¶14). - Contributors: none. - Sponsors: none. The thread mentions paid courses (¶10, ¶14), not sponsorship. - Ecosystem: none from this source. #### WordPress - Core: none. - Core Performance: none. - Core AI: none directly. The NotebookLM workflow (¶8) is an AI use of public docs, and it carries no evaluation data. - **Core Program Team:** none. - Mobile: none. - Playground: none. - Community: none directly. A meetup could run the docs-to-NotebookLM experiment on a handbook page and report back. - Training: the docs-versus-courses split (¶4, ¶14) maps to Learn WordPress. Reference docs and guided setup lessons serve different needs. - Marketing: none. - Support: none. The thread suggests some users won't read docs (¶6), which support teams already know from ticket data. - Design: none. - Documentation: the "read the docs once" claim (¶4) invites a check on whether DevHub and HelpHub pages explain structure and decision-making as well as features. - Photos: none. - TV: none directly. Nearest relevance: the thread is about video tutorials, and ¶12 praises one for examples and full settings. - Polyglots: none. - Accessibility: none from this source. - Meta: none. - CLI: none. - Hosting: none. - Tide: none. - Openverse: none. - Themes: none. - Plugins: none. #### The WPOCC - Programs: none directly. - Projects: none. - Funding experiments: none from this source. ### FAIR - Technical independence: none. The thread says nothing about signing or provenance. - Policies and covenants: none from this source. - Productized governance artifacts: none from this source. ## 🧪 Hypotheses 1. Learners who read a product's docs once recall fewer setup decisions than learners who watch a setup walkthrough of the same product (supports ¶14 over ¶4). 2. Audio generated from a tool's public docs (¶8) gives listeners the same feature coverage as reading those docs, within a measurable accuracy rate. 3. Commenters judge a tutorial as "an advertisement" (¶10) more often when it ends in a course pitch than when it carries no pitch. 4. Documentation for apps marketed as easy (¶4) gets read once and then skipped, so later feature changes reach fewer users through docs than through video or social posts. 5. Users who buy a course (¶14) differ from users who don't in how much they customize areas and projects. 6. A commenter's estimate of how much of a video is feature explanation (¶12) differs from a timed segment count of that video. ## 📊 Methodology - **H1.** Recruit new Things users, split them into a docs-only group and a video-walkthrough group, and test 7 days later. Measure how many setup decisions each person can describe and defend. Use a validated recall scale and pre-register the scoring. - **H2.** Generate audio from a docs set with NotebookLM. Have two reviewers check each episode against the source pages. Count factual errors, omissions and invented details per 10 minutes of audio. - **H3.** Take a set of tutorial videos with and without a pitch, show them to raters, and count "ad" labels. Control for video length and topic. - **H4.** Compare page-view and read-depth data for a help center before and after a feature release with and without a companion video. Needs a vendor's analytics, which the thread doesn't supply. - **H5.** Survey a Things user group with a question on course purchase and one on how many areas and projects they use. Treat results as correlation only. - **H6.** Time-stamp one video into explanation, setup, and promotion segments, then compare the shares with the 95% claim. - **Controls throughout.** Sample sizes stated in advance, no use of the thread's usernames beyond what the thread shows, and no claim about any person's motive. ## ❓ Questions - Which video is the thread about, and which "new feature" does it cover (¶12)? - What does the poster say, given that the capture shows no post body? - Who wrote each comment, given that the capture doesn't mark ownership of the text (see Main content)? - What share of the video actually explains the feature, and what share promotes the course (¶10 versus ¶12)? - Does the NotebookLM project from ¶8 stay accurate across the whole docs set? - Do Cultured Code's docs cover areas-and-projects setup choices, or only what each control does (¶4 versus ¶14)? - How many Things users read the docs at all, given ¶6's remark? - Does Peter state a commercial link in the video, and where? ## 🔮 Future research - **Read the full thread.** The capture holds six comments. The live thread may have a post body, more replies, and Peter's own response. - **Watch the video.** Time-stamp the explanation and promotion segments to test the 95% claim (¶12). - **Test the docs-to-audio workflow.** Run it on a small doc set and audit the audio against the pages (¶8). - **Docs coverage of setup.** Compare what the official docs say about structuring areas and projects with what the course teaches (¶14). This needs access to both. - **Docs-versus-tutorial usage.** Find public data on how users of other well-documented apps split between docs and third-party tutorials. ## 💡 Implications - **Practice.** A tutorial creator with a paid course will get read as promotion by some viewers (¶10) and as value by others (¶12, ¶14). Disclosing the course up front lowers the chance of the first reading. That's inference from the thread, not a measured effect. - **Policy.** Feeding a vendor's public docs into a third-party AI tool (¶8) is common enough that a docs owner may want a stated position on it. The thread doesn't raise this. - **Security.** None from the thread's text. The workflow sends public docs only, so no private data is at stake. - **Education.** The ¶4 and ¶14 pair suggests docs answer "what does this do" and courses answer "how should I arrange this." A learning path can use both. - **Funding.** The thread mentions paid courses (¶10, ¶14) but no prices or revenue. It offers no basis for a funding claim. ## 🧠 Learning styles assessment - **Reading level estimate.** Flesch-Kincaid Grade Level of about 6 to 7, estimated from the six comment texts. Sentences are short and informal, and punctuation is loose, so the sentence count is unreliable. This is a rough estimate, not a clean computed score. #### 👀 Visual learners - Present: no images or diagrams in the captured text. Three emojis appear (¶8, ¶10). - Improve: a screenshot of a Things areas-and-projects setup would show the tailoring that ¶14 describes. #### 🔊 Aural learners - Present: ¶8 describes a podcast generated from docs. No audio is attached to the thread. - Improve: a 2 to 5 minute audio summary of the thread's three positions. #### 🗣️ Verbal learners - Present: plain comments with a few reasons. Terms such as "areas" and "projects" are used without definitions. - Improve: define Things terms on first use and add a one-line summary of each position. #### 🧩 Kinesthetic learners - Present: ¶8 is a repeatable experiment: add docs URLs to NotebookLM and generate audio. - Improve: a step list for the NotebookLM workflow, including how to pick the URLs and check the output. #### 🧠 Logical learners - Present: a three-way disagreement with simple claims. Percentages appear once (¶12). - Improve: a table of claim, who made it, and what would verify it (as in Main content). #### 🧑‍🤝‍🧑 Social learners - Present: the thread is a conversation with agreement and pushback. - Improve: a discussion prompt: "What would you want a Things course to teach that the docs don't?" #### 🧘‍♀️ Solitary learners - Present: short comments that can be read alone in under 2 minutes. - Improve: a self-check: "Which of the three positions matches how I learned my task manager?" #### 🌿 Naturalistic learners - Present: nothing relevant. - Improve: none needed for this topic. ## 📊 Accessibility assessment Judged as captured. The capture is a text view of a Reddit thread, so the live page's markup, colors, and behavior aren't visible. #### Screen reader semantics - Present: comment text reads in order, and usernames appear as separate lines. - Improve: the capture separates each username from its comment, so a screen reader user can't tell whose text is whose without the live page's structure (WCAG 1.3.1, Info and Relationships). Headings, landmarks and alt text can't be seen in the capture. Two emojis (¶8, ¶10) would be read aloud by name, which a screen reader handles but can make a sentence verbose. #### Keyboard navigation - Present: not assessable from the captured text. - Improve: the live page's focus order, skip links and collapse controls can't be judged here. #### Contrast and readability - Present: unknowable from text. Page styling isn't captured. - Improve: check the live thread against the 4.5:1 text contrast minimum (WCAG 1.4.3). #### Text resizing and reflow - Present: the capture reflows as plain text. - Improve: reflow at 200% zoom and 320 CSS pixels (WCAG 1.4.4, 1.4.10) can't be verified from the capture. #### Media and captions - No media referenced in the captured text. The video the thread discusses isn't embedded or linked, so its captions can't be assessed. #### Forms and interactions - Present: none in the capture. A comment box and vote buttons exist on the live site but aren't captured. - Improve: target size and labels on those controls can't be judged here (WCAG 2.5.8). #### Standards reference - Candidate gaps against WCAG 2.2 AA, each unverified: **1.3.1** (usernames separated from comment text in the capture), **1.3.2** (Meaningful Sequence, since ownership of a comment depends on order), **1.4.3** (contrast), **1.4.10** (reflow). The capture carries no images. ## 🌍 DEIB assessment #### Cultural breadth - Present: English only. At least one commenter's English reads as a second language (¶8: "docs url available through CulturedCode web site"). That is an observation about phrasing, not an assumption about the person. - Improve: no multilingual options appear in the capture. A short glossary would help readers outside the Things community. #### Inclusive language - Present: no slurs or group-targeting language. ¶10 calls the course "little" and uses a shrug emoji, which reads as dismissive of the creator, not of a group. - Improve: define "areas," "projects," and "NotebookLM" on first use for readers new to either tool. #### Neurodiversity support - Present: short comments, one idea each, easy to chunk. - Improve: the capture drops the reply structure, so a reader has to infer who answers whom. A reply-tree view would help. #### Representation - Present: seven usernames, no stated names, genders or other identity details. Peter is referred to by first name only. - Improve: none. The thread gives no basis for assumptions about anyone, and this note makes none. #### Psychological safety - Present: the thread is mostly civil. ¶12 says a critic has "no interest in Things but complaint," which is a motive charge against another user. - Improve: moderators can nudge users toward describing the video's content instead of the other commenter's motives. ## ✅ Logical validity Source type: an anonymous forum thread of opinion. It has no data, no citations, and no named expertise. Treat every claim as one user's view. #### Strong reasoning - **Concrete method, ¶8.** The NotebookLM comment states steps (docs URLs, global podcast, per-feature series) that another person could repeat and judge. That makes it testable, though no result is reported. - **Complementary framing, ¶14.** The point that setup choices get tailored per person is consistent with the docs describing features and the courses describing arrangement. The commenter doesn't say this outright, but it reconciles ¶4 and ¶12. - **Direct response, ¶12.** The rebuttal names a measurable thing (share of the video that explains the feature, with examples and settings) that a viewer could check, even though it gives no times. #### Fallacies - **Overgeneralization, ¶4: "you will know literally anything there is to know about the app."** One read of the docs is claimed to cover everything. Weak because "everything" would include structure and workflow choices, which ¶14 says are personal. Fix: say the docs cover what each feature does. - **Hasty generalization, ¶6: "I don't think people read anything nowadays."** A claim about everyone from impression. Fix: cite reading data or say "many of the people I know." - **Unsupported assertion, ¶10: "basically an advertisement."** No passage or timestamp is cited. Fix: name where the promotion starts and how long it runs. - **Unsupported figure, ¶12: "95%."** A precise number with no measurement behind it. Fix: time-stamp the segments. - **Ad hominem (motive attack), ¶12: "you have no interest in Things but complaint."** It addresses the critic's motive, not the critic's claim. Fix: restate the evidence about the video's content. #### Tone of voice - Casual, conversational, and short. Examples: "Cool guy but the problem..." (¶4), "Then you should listen" with a headphones emoji (¶8), "basically an advertisement" with a shrug emoji (¶10). ¶12 turns sharper. ¶14 is warm and personal ("I like Peter’s videos. Bought his courses too."). ## 🛡️ DARVO analysis Not applicable to this source. DARVO describes a response to an accusation of wrongdoing, and this thread is a disagreement about whether a video adds value. **Deny:** no one denies a charge of misconduct. ¶12 disputes the "advertisement" description, which is a disagreement, not a denial of harm. **Attack:** ¶12 attacks the other commenter's motive ("no interest in Things but complaint"). That is a minor credibility move inside a mild argument. **Reverse victim/offender:** no one recasts themselves as a victim. The emotional cues are an eye-roll style shrug (¶10) and the defensive turn in ¶12. ## 🎯 Conclusion The capture holds one thread title, no post body, and six short comments from six users. Each is one person's opinion, with no verification and no sourcing beyond the thread and the profile links in References. Three views appear: the docs suffice (¶4), the video is mostly an ad (¶10) versus mostly feature explanation (¶12), and the courses teach a personal setup (¶14). One user reports a NotebookLM workflow built from Cultured Code's public docs (¶8). What the capture can't tell you matters as much as what it says. It doesn't hold the video, the feature, the docs, the course, or Peter's own words. Comment ownership rests on an ordering inference. **Next steps for readers:** open the live thread to confirm who wrote what and to see any post body, watch the video before taking either side on the advertisement question, and try the NotebookLM workflow on a small doc set while checking its audio against the pages. ## 🔄 Refactor Appendix — Peter Akkies > Density: 2–5 Literature atoms (H1 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 3 Literature, 1 Permanent. Resonance filter applied: username lines, the shrug and > headphone emojis, and the advertisement exchange (¶10 to ¶12) were dropped because they carry > no claim beyond an unmeasured impression. > > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Split Pad #### [H1] Public docs can feed a NotebookLM audio series > [!quote] [¶8] > I’ve provided all open docs url available through CulturedCode web site. **Context & use**: - ¶8, vyega, in reply to the "people don't read" remark. The next sentence in ¶8 says the follow-up request was a global podcast and a feature-by-feature mini series. - A repeatable way to learn a tool's feature set by listening. One user's report, with no results shown. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> #### [H2] One commenter says the docs cover everything > [!quote] [¶4] > If you read through the docs from Cultured Code ONCE you will know literally anything there is to know about the app. **Context & use**: - ¶4, kuzcoduck, by the attribution reading in Main content. An opinion with no data. - Pairs with [H3] as the other side of the docs-versus-courses split. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H3] Personal setup is what courses can teach > [!quote] [¶14] > The setup behind the scenes with specific areas and projects is something everyone will end up tailoring for themselves. **Context & use**: - ¶14, dont12, who also says they bought the courses. A customer's view, which may carry bias toward their own purchase. - Stated by a commenter, not established. Docs that cover structure would test it. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> ### 🧠 Atomic Split Pad #### [P1] Docs describe features while courses describe arrangement **Claim** (one sentence, Courtney's voice): Documentation explains what each control does, and a course earns its price by teaching how to arrange the controls for one person's work. **Evidence pointer**: [[#H2]] · [[#H3]] **Scope & conditions**: Holds for configurable tools where structure is personal, such as a task manager. Breaks when the docs already include setup guidance or when a course only restates features. The only evidence here is two forum comments, so treat it as a hypothesis to test. **Links**: - [[Docs versus tutorials]] — because extends - [[Learning to use a task manager]] — because applies-in - [[Tutorial creators and commercial interest]] — because contrasts on whether a tutorial is value or promotion <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Open the live r/thingsapp thread and check the post body, comment ownership, and any reply from Peter #fleeting #inbox - [F2] Open question: do Cultured Code's docs cover areas-and-projects setup choices? (¶4 versus ¶14) #fleeting #inbox - [F3] Idea: run the NotebookLM docs workflow on a WordPress handbook section and audit the audio #fleeting #inbox #articleseed ### → Things 3 (max 2 actions) - [ ] Try a NotebookLM notebook built from Cultured Code's public Things docs and spot-check the audio against the pages, r/thingsapp thread, one user's report #things - [ ] Open the live thread and confirm who wrote each comment and whether the post has a body, r/thingsapp "Peter Akkies" #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Peter Akkies.md|Peter Akkies by Ok-Comfortable2546]] ## Highlights - Then you should listen 🎧 I’ve created a NotebookLM project to handle all “Things” things: 1st thing first I’ve provided all open docs url available through CulturedCode web site. Then asked to generate a podcast starting by a global one then mini series focusing on feature by feature. ([View Highlight](https://read.readwise.io/read/01m3kzanvhm3gt521wyd20k97g)) - Note: [H1] Public docs can become a NotebookLM podcast series - Tags: atom/literature/h1