Posts

Professional Profile

Executive Summary: A 35-year evolution from technical journalism to strategic content leadership, characterized by a singular ability to translate low-level engineering complexity (embedded systems, assembly language, processor architecture) into clear, user-centric, and business-aligned documentation across diverse, agile, and modern cloud-based platforms. My core competence is bridging the gap between deep technical implementation and effective audience communication. Phase 1: Foundational Technical Depth and Low-Level Systems (1985–1992) Focus: Journalism, Embedded Software, and Hardware Interplay This period established a non-negotiable foundation in low-level technology and detailed technical analysis. Technical Journalism (Electronic Design, 1985-1988): Began as a West Coast Technical Editor, analyzing and communicating complex industry trends in computer hardware, software, and networking to a professional engineering audience. This built my ability to synthesize broad technic...

Resume

 My current resume can be viewed or downloaded from a Web browser View Publication

Multi-Platform App Development & Apple Silicon's Impact

 Trained Generative AI tools (Google Gemini and NotebookLM) to create an overview of app development across multiple operating systems (MacOS, iPadOS, iOS, Windows, & Android). View Publication

Learning Python and Generative AI: A Self-Study Guide

 Trained Large Language Models (Google Gemini and NotebookLM) with prompt design to create a self-study guide for learning Python with a focus on Generative AI. View Publication

Picking Up The Pieces

The article highlights a shift in the approach in product documentation (particularly in smaller startups)  from commercial software like Microsoft Word and Adobe FrameMaker that are industry standards. The trend is now towards open-source alternatives like Apache OpenOffice and LibreOffice. View Publication

Modern Web Applications

Modern web applicatiox (such as Google Docs) implement many coordinated user functions and tasks traditionally associated with desktop software (such as Microsoft Office).. Key topics include: • Open-Source Standards: The use of JavaScript, HTML5, and CSS. • MVC Architecture: Separation of concerns into Model, View, and Controller. • Single-Page Applications (SPA) enhance user experience without full page reloads. • Microapps: Breaking single-page applications into smaller, independent services. • Responsive Web Design: Ensuring web applications work on various devices. • Web Services: Using REST and SOAP for server-side communication. View publication

Planning and Delivering Agile Documents

The impact on documentation is huge when project teams adopt agile practices to plan and deliver products and services. Key Takeaways: Agile Principles and Technical Documentation: Agile development prioritizes working software, collaboration, and adaptability, which significantly impacts technical documentation. Shift from Formal Specifications: In agile, writers must rely on working software, not formal specifications, to create documentation. Dynamic Documentation: Agile emphasizes creating documentation that is relevant, stable, and continuously updated based on feedback. Audience Analysis: Understanding the target audience is crucial for creating effective documentation. User Stories and Tasks: User stories and tasks provide a structured approach to breaking down documentation requirements. Continuous Delivery and Kanban: Agile's focus on continuous delivery and the use of kanban boards help ensure that documentation aligns with the evolving product. The article also inc...