open source, technical writing

Well begun (in Git) is half done

Well begun is half done. ~ Aristotle Inspired by James Clear’s book, Atomic Habits, I’ve started starting tasks before it’s time to do them. For example, I prepare the Keurig coffee machine before bed each night. I fill the reusable filter with fresh coffee grounds and top up the reservoir with water. As a sign […]

Read more
open source, technical writing

Developer-contributed content in upstream docs

“No software spec survives first contact with the compiler.” One of the interesting bits in the project type #1: Team=Both, Code=Up>Down, Docs=Down>Up scenario is when developers write up their feature plans in the upstream repo. Often, these show up in the /doc subdirectory. Often, before coding, a developer writes up a description of the new feature […]

Read more
technical writing

Writing and publishing on GitHub

I hope to create an open community around documenting open-source software and practice what I preach: To eat my dog food, as they say. What better way than to create a repo and invite the contributions of other writers? To be honest, its a bit tough to do this. I believe in “open source.” I […]

Read more