![]() No matter how sharp you are, humans have limits as to how many things they can juggle in any situation - but the sheer risk of production changes saps even some of that capability away because we are being extra vigilant to ensure everything is done just as planned. The elimination of cognitive load during a stressful activity, such as managing IT changes, is also a huge benefit. Recording Information in Checklists and Cognitive Loading I have removed those plugins and instead run a plugin that simply opens a file type in my operating system’s default application for markdown files and configure Typora to handle markdown extensions in the operating system. Sometimes they conflicted or even prevented editing the markdown by no longer recognizing specific keystrokes. In the past I have had my favorite code editor (VS Code) loaded up with many markdown extensions - each one completed different parts of the puzzle and did it in different ways. HTML and CSS formatting render nicely in Typora, but not in GitLab and GitHub. ![]() Apply HTML or CSS formatting - for instance, colored text background.In the provided CopyQ code there are examples of prompting for both Template Checklist authoring and Tracking Checklist execution. Prompt for information and include it as part of the insertion text.Insert the current date and time as part of “Completion marking.”.Apply Markdown formatting completion mark (such as bold).This allows adding the following additional completion marking capabilities: CopyQ allows the insertion of standardized markdown snippets using hotkeys and Typora can directly receive markdown and immediately renders it. For implementation of more elaborate “completed marking” (for example, adding date-time stamps and/or colors).Ĭombining Typora and CopyQ expands checklist execution and authoring options.For completing visual markdown structures that are not interactive on GitHub and GitLab (such as fill-in fields or tables).For navigation of complex checklists In an outline mode while completing them.There may be times when visual, desktop-based utilities offer advantages over this model, such as: The interactivity of checklists on GitHub and GitLab should generally be used for Tracking Checklists as they facilitate collaboration through immediate, shared updates and do not require Git commits or merges during real-time operational events. “Dual-pain” is not misspelled here - while developers may consider a live rendering window an upgrade to coding in raw markdown, it is very cumbersome for those who do not have a developer role, but need to author Template Checklists or complete Tracking Checklists. Checklist Authoring, Navigation and Completion without Dual-Pain Markdown Editors In this article, we dive into the why and how of using rich desktop editing tools for checklist creation and completion. ![]() Part 2 dug into the rich but often overlooked, support for interactive checklists on GitHub and GitLab. Part 1 justified that human-performed DevOps checklists are essentially source code, and according to GitOps principles, belong in Git just like any other code required for successfully managing a software stack. This article is the third and final of a series. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |