Writing in Git Part

[singularityhacker]

Follow up to "Github for Writing"

https://about.gitlab.com/blog/2018/03/05/gitlab-for-agile-software-development/

Replaces:

• ToDo lists
• Trello
• Jira
• Confluence
• Slack

Maybe all project management should be managed through version control. The Org will be swallowed by code and in doing so, it will be swallowed by source control.

See for mapping traditional agile concepts to git entities:

• https://codetree.com/guides/sprint-planning-github-issues
• https://about.gitlab.com/blog/2018/03/05/gitlab-for-agile-software-development/

[singularityhacker]

• Getting Grammarly to work with MD is a big problem
• posting MD directly to Medium: https://pqsec.org/2020/05/25/import-markdown-into-medium.html

The issues above are separate.

1. One is the issue of replacing many traditional auxiliary agile tools with a version control system like git.
2. A second, and totally separate, issue is using git for writing.
3. One might argue that content generation should fall within the scrum framework but that's another issue as well.

[singularityhacker]

https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues

[singularityhacker]

"Our Course Steward Model Each Scrum.org course is assigned 2 stewards. The stewards are ultimately responsible for collecting input on the course materials, both those that exist and potentially additions to be made, review that input with the community along with Ken Schwaber and provide updates as required.

Each course is stored in GitHub, allowing version control, feedback mechanisms, distribution and much more, not unlike the code that Scrum Teams deliver for their products. Through GitHub capabilities, a PST can submit feedback on a course materials, its delivery content, speaker notes, exercises and much more. With PSTs around the world teaching the materials, that provides a fantastic number of people to provide excellent feedback to improve the content and quality of the courseware. Learn more about the PSM II class from one of our course stewards Barry Overeem and fellow Professional Scrum Trainer Joshua Partogi." - https://www.scrum.org/courses/professional-scrum-master-ii-training

[singularityhacker]

If writing in git is largely about getting to the source of things then it makes sense to get to the source of things in tooling as well. This has been a rocky patch since taking on this experiment. A few things to take into mind:

• I thought I needed a markdown app to conveniently edit MD files in such a way that the rendered MD would appear next to my typed text. I even almost paid for this as a service.
• After trying several MD MacOS apps, I was disappointed that Grammarly did not work while using them so I looking at MD editor web solution because Grammarly works in the browser context. This proved to be not ideal because I had to grant the web app access to my github account and atomic commits were weird as the web apps I tried were not clear in when they would since to my repo.

So I'v settled into using VS Code for my writing tool.

• No third-party access to my repo.
• Unambiguous git interaction.
• MD extension that permits side by side rendering of MD content.
• A Grammarly extension.
• Proximity to the source and experience of things. This includes an ide interface, extension ecosystem, and two birds with one stone in learning a single way to write content and code.
• Building a second brain with Foam

[singularityhacker]

Content/code is a continuum, not binary. Code should be self-documenting and content should be precise enough to be formally modeled to some extent.

[singularityhacker]

• watched basic tutorials on VSCode
• Learned how to install extensions
• Learned how to push to github
• And who to edit/preview MD (cmd+k V)

[singularityhacker]

• [x] Add grammarly
• [x] Connect foam package
• [ ] Setup github pages
• [ ] Connect to netlify
• [ ] Move Agile Automata to Netlify

[singularityhacker]

Grammarly removed from the market place. Use the package directly: https://github.com/znck/grammarly/releases/tag/v0.12.2

[singularityhacker]

VS Code crash course:

• command pallet: cmd + shift + P

[singularityhacker]

On the idea that code/content as a continuum:

• https://meta.wikimedia.org/wiki/Abstract_Wikipedia/July_2020_announcement
• https://www.inklestudios.com/ink/
• https://en.wikipedia.org/wiki/AI_Dungeon_2

[singularityhacker]

• Written communication is remote work super power
• Why writing matters in remote work
• :point_up_2: The above post got amplified right on up to Chris Coyier

[singularityhacker]

• https://beta.openai.com/

[singularityhacker]

See the triangle: diagram/content/code

Not suggesting a curry-Howard correspondence but a meaningful continuum.

We are made for image recognition. The memory master leverage cognitive cathedrals to retain large amounts of information. Even some programming languages are introducing this correspondence: https://ballerina.io/

Content as "wet code" and code as "dry code": http://unenumerated.blogspot.com/2006/11/wet-code-and-dry.html

[singularityhacker]

Some notes on recent pattern changes and advances:

• Images: imgur image uploader
• Less is more: Writing through the browser isn't bad
• Volume: link to word count plugin
• Top-level project board
• Private journaling
• Github actions (entry point of executable content)
• Github as social network: https://i.imgur.com/X7mhZ1E.jpg
• Easier MD writing with chrome extension
• The github writer extension above makes Grammarly work!! Woooohooooo!

[singularityhacker]

Chrome extension to market with this next blog post series:

• [ ] Markdown file editor word count display
• [ ] Words written profile graph (dynamically updated in new profile readme)

[singularityhacker]

Aligning ideas:

• Safe has moved away from software centered thinking and applied software org practices to all business endeavors
• This means that instantiating safe in the form of a Dao suddenly has relevance for all cooperative activities and not just software-based ones
• This highlights the need for business activities to happen in a content center version control system so that it can be known by the DAO via oracle mechanisms

[singularityhacker]

Commits vs work count. Measure the right thing. https://github.com/marketplace/actions/word-count

[singularityhacker]

• A review of the vision: natural language to format language is a spectrum, not binary.
• Version control as the single resource of truth. GitOps
• From don't break the chain to quantified daily contribution with Github actions
• Don't break the chain on my watch: https://apps.apple.com/us/app/contributions-for-github/id1153432612
• A big circle from larger complexity to the simplest setup. (In browser editing with the markdown plugin + Grammarly)
• HackMD.io as a presentation and sharing mechanism
• How I'm handling images (Imgur + https://github.com/mileswd/mac2imgur)

[singularityhacker]

Questions I said I would address in my previous post:

• The details of my new writing setup (The circle)
• Steps to migrate existing Google docs projects to GitHub (https://www.buymeacoffee.com/docstomarkdown)
• A status report on how things are going (Felt advantages: visibility. Facts confront feelings.)

[singularityhacker]

Read the tutorial for anything I may have missed: https://www.scrygroup.com/tutorial/2020-01-07/guide-to-git-github-for-writers/

My last post for reference: https://medium.com/@justiceconder/writing-on-github-c35ddd12bfd8

[singularityhacker]

Tips:

• Use issues for quick notes and prolonged ideation
• Migrate issue to document when you're ready to start on the document
• Use a project board with milestones to maintain a cadence
• Create your projects at the topmost level of your GitHub so you can use a single cross-cutting kanban board and link issues to any of your repositories.