Bilingual

Search Less, Browse More
20 days ago
- Emphasizes browsing documentation over solely searching for quick answers to discover more features.
- Uses learning Excel as an example, where browsing uncovered powerful features unknown to long-time users.
- Contrasts searching (focused on problem-solving) with browsing (focused on discovery and learning).
- Illustrates with Python's pathlib module, found through browsing, which is a superior solution for file paths.
- Highlights that browsing can reveal broadly useful tools that searching might miss due to specificity.
- Proposes a potential workshop on Excel for programmers or analysts based on interest in advanced features.
When docs become performance art, everybody loses (2025)
19 days ago
- Documentation theater refers to creating docs for the sake of compliance rather than addressing user needs, which is worse than having no docs at all.
- Performative content, like fake skill percentages on resumes or unnecessary website sections, is dysfunctional and fails to solve actual problems.
- Tech writers should focus on user needs, not templates or frameworks, by asking who the audience is and how the content helps them, upholding clarity and comprehension.
Markdown Now Has a UTI in Apple's Version 27 OSes
18 days ago
- John Gruber highlights Day One, a journaling app with a 4.8 rating.
- Apple's developer beta introduces a new UTI for Markdown: net.daringfireball.markdown, conforming to public.utf8-plain-text.
- Gruber updates his recommendation to public.utf8-plain-text, reflecting the now-universal UTF-8 support.
Redis Patterns for Coding Agents
18 days ago
- Optimized website for developers and AI agents with Redis patterns, practices, and commands.
- Human-friendly browsing with clickable sections and machine-readable index (llms.txt).
- AI agents start by fetching llms.txt, then individual .md files with Markdown and Redis commands.
- Local mirror of official Redis documentation including command index and detailed docs.
- Core architectural patterns, community-developed use cases, and real-world scale examples available.
Otary – Image and Geometry Python Library Now Has Tutorials
17 days ago
- Provides examples of using Otary for understanding its functionality.
- Covers topics like image cropping, linear entities, scoring, area computation, geometric intersections, and OCR.
- Aims to inspire exploration and practical application rather than serve as a complete reference.
EvilCharts: Charts That Don't Suck
12 days ago
- Fetch the complete documentation index at /llms.txt to discover all available pages.
- Introduces four types of bar charts: Monospace Bar Chart, Hover Trace Bar Chart, Grid Bar Chart, and Isometric Bar Chart.
- Provides installation commands for each bar chart using npx shadcn@latest add @evilcharts/ with respective chart names.
Accretive Editing
15 days ago
- Accretive editing is a failure mode in AI tools where they add addendums instead of correcting text when updating.
- An example involves changing support from Amazon Bedrock to LiteLLM, where AI added an addendum rather than replacing the obsolete information.
- This issue cannot be fixed by simply telling the model to write less or adjust style, as it stems from how LLMs predict text based on multiple inputs.
- The cause may be that LLMs lack human perspective on document updates, focusing on predicting likely text rather than making it true for readers.
- To address accretive editing, focus on instructing AI to replace obsolete text with accurate text, aiming for a document that reads as if written correctly from the start.
Design Systems as Knowledge Graphs
11 days ago
- The traditional design system documentation resembles linear product docs but could be more effective as small, addressable chunks.
- Design systems are hyperobjects akin to knowledge graphs, capturing decisions, patterns, and history, rather than just products or libraries.
- Knowledge graphs interlink entity descriptions with semantic metadata, enabling data integration and sharing, as seen in tools like Roam Research and Obsidian.
- Transclusion allows embedding minimal content chunks (e.g., tokens, components) across contexts, ensuring updates propagate and revealing system relationships.
- Bidirectional links make dependencies (e.g., between Button and Icon) visible from both sides, aiding navigation and visualization, similar to features in knowledge graph apps.
- Fragments (like Wikipedia's red links) represent undefined future elements in design systems, encouraging contribution by highlighting gaps.
- Queries enable users to ask questions of the design system (e.g., via GraphQL APIs) for immediate answers, moving beyond browsing to interactive exploration.
- Applying knowledge graph concepts can transform design system docs into collaborative, remixable tools that scale knowledge across large teams.
Three workers digging in a field outside the data center
8 days ago
- Performance documentation by Dinnis van Dijken on May 15th near Google's data center in Westpoort, Groningen.
- Three workers dig in a field with shovels and a spade, ignoring cameras, while a security guard intervenes.
- The performance explores themes of labor, land, and art, with interactions involving police and corporate security.
- The event concludes with payments and symbolic cookies given to the workers at a nearby Aldi distribution center.

documentation

Search Less, Browse More

When docs become performance art, everybody loses (2025)

Markdown Now Has a UTI in Apple's Version 27 OSes

Redis Patterns for Coding Agents

Otary – Image and Geometry Python Library Now Has Tutorials

EvilCharts: Charts That Don't Suck

Accretive Editing

Design Systems as Knowledge Graphs

Three workers digging in a field outside the data center