The reading and research workflow for software engineers: four research tiers that match the different purposes of engineering research (active problem-solving research, weekly technical learning, monthly technology landscape assessment, and project deep research), with the capture and processing disciplines that convert engineering research from background activity into compounding professional knowledge.
AI research for historians: where AI tools provide genuine leverage in historical research and scholarly work (literature orientation, secondary source discovery, writing assistance, administrative tasks), where they introduce serious quality risks for academic history (primary source interpretation, archival fabrication, historiographical claims, citation accuracy), and the professional disciplines that maintain the scholarly integrity that academic history requires.
AI research for screenwriters: where AI tools provide genuine leverage in script development and pitch preparation (world orientation, structural brainstorming, administrative tasks), where they introduce quality risks for professional screenwriting (authentic procedural detail, story judgment, market intelligence), and the professional disciplines that maintain the dramatic and professional quality that the industry requires.
AI research for software engineers: where AI tools provide genuine leverage in engineering work (code generation and explanation, documentation exploration, prototype drafting, debugging assistance), where they introduce quality risks for professional software engineering (security-sensitive code, critical logic, performance optimization, novel problems), and the professional disciplines that maintain code quality and security while leveraging AI productivity gains.
Building a searchable knowledge base for historians: the four knowledge domains that historical research generates (primary sources and archival material, secondary literature and historiography, research arguments and interpretations, and professional and disciplinary knowledge), organized for retrieval across the long timelines of historical research and the specialized audiences of academic publication.
Building a searchable knowledge base for screenwriters: the four knowledge domains that a professional screenwriting career generates (market and industry knowledge, story and character development, craft and technique knowledge, and professional and career knowledge), organized for retrieval at pitch meetings, in writers' rooms, and during the research phases of new projects.
Building a searchable knowledge base for software engineers: the four knowledge domains that a professional engineering career generates (technical solutions and debugging, architecture and design knowledge, codebase and team context, and professional and career knowledge), organized for retrieval during active engineering work, team onboarding, and technical decision-making.
Building a second brain as a historian: the five knowledge components that compound across a historical career (archival and primary source expertise, historiographical knowledge, interpretive and methodological wisdom, professional and disciplinary knowledge, and intellectual identity as a historian), the capture practices that build each component, and how the accumulated knowledge makes each project build on the research investment of all prior work.
Building a second brain as a screenwriter: the five knowledge components that compound across a screenwriting career (story and character intuition, craft and technical expertise, industry and market intelligence, professional relationship wisdom, and personal creative voice), the capture habits that build each component, and how the accumulated knowledge makes each project better than the last.
Building a second brain as a software engineer: the five knowledge components that compound across an engineering career (technical problem-solving patterns, system and architecture knowledge, engineering craft and practices, professional and career wisdom, and intellectual identity as an engineer), the capture habits that build each component, and how the accumulated knowledge makes each project and system engagement more effective than the last.
How historians manage information overload: the six information streams that compete for a historian's attention (secondary literature, archival and primary source discovery, professional discipline updates, peer review and colleague communications, professional community, and administrative work), and the batching and triage strategies that protect the deep reading and thinking time that historical research requires.
How software engineers manage information overload: the six information streams that compete for an engineer's attention (technical documentation and references, team communications, pull requests and code reviews, technical news and learning, incident and operational communications, and administrative work), and the batching and context-switching strategies that protect deep work while maintaining the technical currency and team coordination that engineering work requires.
Note-taking templates for historians: four templates that structure the most important professional note-taking contexts (primary source and archival notes, secondary literature notes, interpretation and argument development notes, and professional and methodological notes), with the specific fields that capture the scholarly intelligence that compounds across a historical career.
Note-taking templates for screenwriters: four templates that structure the most important professional note-taking contexts (story and world research notes, script notes and feedback notes, writers' room notes, and craft and professional development notes), with the specific fields that capture the professional intelligence that compounds across a screenwriting career.
The research-to-output workflow for historians: how primary source research and secondary literature engagement convert into the scholarly outputs of a historical career — monographs, journal articles, conference papers, and public history work — with the disciplines that keep each stage of the research process focused on the argument rather than the accumulation of interesting material.
The research-to-output workflow for screenwriters: how research converts into the professional outputs of a screenwriting career — pitched projects, script drafts, writers' room contributions, and produced episodes — with the disciplines that keep research focused on what scripts actually need and prevent the accumulation of interesting-but-unused material.
The research-to-output workflow for software engineers: how technical research and learning convert into the professional outputs of engineering work — working code, technical documentation, architecture decisions, and knowledge sharing — with the disciplines that keep research focused on solving specific problems rather than accumulating interesting technical knowledge.
The essential software stack for historians: the four professional knowledge problems that historical research generates (source management and archival organization, research and argument development, writing and publication, and professional and career knowledge), and the digital workflow tools that address each — organized around the historian's core challenge of working across time, institutions, and formats with sources that may only be accessed once.
The essential software stack for software engineers: the four professional knowledge problems that software engineering generates (technical knowledge management, architecture and design decision documentation, team and codebase context, and professional and career knowledge), and the tools and workflows that build retrievable engineering knowledge that compounds across projects and teams.
The reading and research workflow for historians: four research tiers that match the different research purposes across a historical career (archival and primary source research, secondary literature engagement, professional and methodological reading, and pre-project deep research), with the capture disciplines that convert research activities into the retrievable scholarly knowledge that makes each project build on all prior work.
The reading and research workflow for screenwriters: four reading tiers that match the different research purposes in a screenwriting career (active project research, weekly craft reading, monthly industry landscape assessment, and pre-production deep research), with the capture and processing disciplines that convert reading from activity into the retrievable professional intelligence that improves both current scripts and long-term career development.
AI research for authors: where AI tools provide genuine leverage in book research and writing (literature orientation, structural drafting, administrative tasks), where they introduce quality risk for books (factual claims, primary source interpretation, historical specificity, argument originality), and the professional disciplines that maintain the intellectual and factual quality that book publishing requires.
AI research for podcasters: where AI tools provide genuine leverage in podcast production (research orientation, show notes drafting, question generation, administrative tasks), where they introduce quality risk (factual claims, guest intelligence, audience intelligence, editorial judgment), and the professional disciplines that maintain content quality when AI is part of the podcaster's workflow.
AI research for translators: where AI tools provide genuine leverage in translation professional work (terminology orientation, background research, editing and proofreading support, administrative tasks), where they introduce risk (terminological accuracy, register and register-specific collocations, subject matter precision, culturally specific expressions), and the professional disciplines that maintain translation quality when AI is part of the workflow.