The Unreasonable Effectiveness Of Plain Text

This video advocates replacing fragile, hype-driven documentation and project-management tools with a durable "Ulysses pact" built on plain text, Git, and GitHub. The speaker argues that writing decisions down in Markdown and standardizing on Git repos makes knowledge permanent, portable, and immune to vendor lock-in, while GitHub’s wiki, issues, milestones, and project boards offer a "minimum viable" alternative to purpose-built apps like Trello or JIRA. A short daily standup centered on blockers keeps teams moving, and GitHub Actions can automate repetitive work at massive scale, while pull requests make sweeping changes safe and reversible. Although the approach is admittedly utopian for many organizations, the speaker encourages adopting even a fraction of it for your own team or solo work as a sane, evidence-based escape from constant tool churn.

• ▶ 1:12 Set up a "Ulysses pact" to guard your team against future bad decisions — create a framework now that prevents your future self from churning through new tools or processes.

• ▶ 2:06 Standardise all tools on plain text as a durable pact: plain text data lives forever and can become more valuable over time, avoiding the constant switching that makes documentation feel disposable.

• ▶ 3:18 Write decisions down in black and white: after conversations, record what was decided and why, then ask for confirmation — this is more reliable than memory and reduces unnecessary meetings.

• ▶ 3:53 Purpose-built documentation apps all "re-invent the wheel" and are ultimately "rubbish," so a better solution is needed.
• ▶ 4:10 Programmers already solve large-scale, distributed, concurrent text collaboration—editing thousands of files daily—and non-programmers can use the same tools.
• ▶ 4:34 Use Git, the dominant version control system, via GitHub; popularity matters for support, integrations, and ecosystem, and these services evolved from Git itself.
• ▶ 6:04 Treat each repo as the foundational unit for one logical project, with wiki and project management tools living alongside the code.
• ▶ 6:22 A wiki is just a folder of linked Markdown files, editable through GitHub's web editor or by cloning it with git — the "minimum viable documentation tool."
• ▶ 6:42 Markdown is the universal standard across GitHub, GitLab, and chat platforms; its plain-text simplicity keeps documentation portable, readable, and focused.
• ▶ 7:52 Issues are a simple, git-host task system for capturing features, bugs, and ideas, and can be enough for solo developers or small teams.
• ▶ 8:15 Milestones group issues under a deadline with just a title, description, and progress bar — minimal project management without complex tools.
• ▶ 8:36 GitHub Project Boards provide a lightweight kanban-style "information radiator" for visual progress, offering a minimum viable alternative to Trello or JIRA.
• ▶ 9:13 The one essential daily meeting is a standup: walk the board backwards, timebox everyone, only speak if you have an issue on the board, and end by asking about blockers.
• ▶ 9:49 The most important part of the standup is asking about blockers; a good standup ensures no one stays blocked or delayed for more than 24 hours.
• ▶ 11:14 GitHub Actions can automate far beyond tests—from rendering images to processing video uploads—running hundreds of times an hour, never making mistakes, and giving a huge competitive advantage.
• ▶ 11:56 Keeping all company assets in Git repos gives offline access and fast, controlled global edits — e.g., renaming a company across 10,000 files is just find-and-replace.
• ▶ 12:50 Git makes large-scale changes safe via pull requests and easy rollbacks, unlike web services where mass edits mean manual, day-long disaster recovery.
• ▶ 13:15 For long-term stability, Git and GitHub are already paid for, dominant, and durable — and plain-text Markdown avoids vendor lock-in and tool churn.
• ▶ 13:51 The speaker acknowledges the video's ideas are utopian and not fully possible in most companies, but encourages doing some of them even just for your immediate team or yourself.
• ▶ 14:02 Asks the audience to share examples of good teams that "buck the hype cycle in favour of sane, evidence-based improvements."
• ▶ 14:08 Thanks viewers and lists support options (Patreon, early/ad-free videos, Discord, mentoring), then closes with source code and corrections info.

• ▶ 0:00 Do Less and Communicate Better (0:00 - 3:53) - - Opens with tech-team pain, the Ulysses pact to do less, and the need for shared documentation and ADRs.
• ▶ 3:53 Introducing Git: From Why Apps Fail to Git Services (3:53 - 5:34) - - Explains why bespoke apps fail and covers Git's origin, recommendation, and trusted code-hosting services.
• ▶ 5:34 Repos, Wikis, and Markdown Documentation (5:34 - 7:49) - - Demo setup leads into repos, wiki docs as linked Markdown, and the portability of plain-text storage.
• ▶ 7:49 Issues, Milestones, and Minimal Project Boards (7:49 - 9:00) - - Covers a lightweight task system with issues, deadlines via milestones, and a simple project progress board.
• ▶ 9:00 Standups, Pull Requests, and Automation (9:00 - 11:56) - - Shows the JIRA effect, daily standups, GitHub organisations, PRs, and Actions running team workflows.
• ▶ 11:56 Offline Git, Plain Text, and Long-Term Stability (11:56 - 13:51) - - Highlights offline repo superpowers, plain-text Markdown benefits, and GitHub's stability over tool churn.
• ▶ 13:51 Realistic Adoption and Closing (13:51 - 14:37) - - Acknowledges real-world adoption limits, asks for examples, and thanks supporters.